Skip to content
CA Service Management - 14.1
Documentation powered by DocOps

Manage Events-Rules-Actions

Last update August 13, 2015


As a CA Service Catalog administrator, you can use events, rules, and actions for automating the requests, users, and accounts process in the system as following: 

Events

Events are installed automatically when you install or upgrade CA Service Catalog.

  • Events represent changes that occur within CA Service Catalog. Several standard events typically occur in various components. For example, the User Create event occurs when an administrator adds new user, by using either the user interface or the createUser web service method. You can also add custom events.
  • Events can have rules that are associated with them. Rules can have a set of filter conditions that define when the rule applies. When the filter conditions are satisfied and the rule is enabled, the rule actions are launched.
  • A rule can have one of more actions that are associated with it. When an event occurs and a rule filter is satisfied, the associated rule actions are executed, if the rule is enabled.

Perform one of the following actions when a custom event occurs:

  • Use one of the postEvent web service methods for the event type
  • Use a URL to post the event

To manage rules, select Administration, Events-Rules-Actions. The page displays the event types and provides access to the rules and actions that are associated with each event type. You can perform the following actions:

  • Use Event Parameters
  • Add a Custom Event Type
  • Manage Rules
  • Manage Actions
  • Post an Event

Rules

All rules are initially disabled. A rule must be enabled to be used. In addition, for some of the rules, there are two mutually exclusive actions, one for use with CA Service Desk Manager and one for use without CA Service Desk Manager. By default, the actions which interface with CA Service Desk Manager are disabled.

The rule conditions that are shipped with CA Service Catalog may not completely match your business processes. They are generic and must be examined for applicability to your environment. In addition, some rules overlap in functionality. When activating rules, be careful to understand the full implications of your changes.

A rule can have one of more actions associated. When an event occurs and a rule filter is satisfied, the associated rule actions are executed. A rule action causes some task to be executed. A rule action can perform one of several action types such as run a command line command, send an email, start a CA Process Automation process, or run a Java plug-in.

The When Status is Submitted and Approval Process is Driven by Workflow rule handles the approval process. The rest of the rules handle the fulfillment process.

Actions

Actions are invoked when a condition in a rule is satisfied. Actions include running a command line command, starting a Java process, sending an email, and starting a CA Process Automation process. For more information about actions, see the descriptions of the rules.

Was this helpful?

Please log in to post comments.