Previous Topic: Fields for Date Range ElementsNext Topic: Creating a Simple Service


Policies and Actions Tab

Note: On the Policies and Actions tab, you can use the link to access CA Process Automation.

By default, CA Service Catalog evaluates all global policies and all events, rules, and actions (global actions only) for every requested service. However, for individual service options, you can replace this default behavior. From the Policies & Actions tab of a service option, you can specify that the Catalog system apply the following specifications to that service option:

You create global policies and global actions for general use with any service. In contrast, you create attached policies and actions for use with one or more specific service options only. You attach these policies and actions to each service option individually. You can create an attached policy or action only from the Policies & Actions tab of that service option. After you create an attached policy or action for that service option, you can optionally attach that policy or action to another service option. However, you cannot change an attached policy or action into a global policy or action. Similarly, you cannot change a global policy or action into an attached policy or action.

As a best practice, use attached actions and policies only if you are using a discrete request life cycle that includes discrete approval of service options. This precaution helps avoid the unintended application of policies and actions at both the service and service option levels.

Important! Applying policies or actions at both the service and service option levels could produce conflicting, unintended, or unpredictable results. If you decide to use attached policies and actions without discrete approval, carefully think through the results for both service options and the service. Review and test the affected services thoroughly in a test system before using them in a production system.