Event and Notification Configuration for CA APM

This article contains the following topics:
casm173
This article contains the following topics:
An
event
represents an activity related to a field (default or extended) for an object. When you define an event, you specify the criteria that must be met before the event occurs. For example, you want to know when the data in a particular field changes. You can define an event that detects the data change. An event works in combination with a
notification
, which the workflow provider (for example, CA Process Automation) creates to alert your team members that an important event has occurred for a specific field or object. By using events and notifications, you alert people about upcoming events and help ensure that the appropriate tasks are performed in the correct order at the right time.
A notification is triggered when an event that you define occurs. For example, you define a date event on the Termination Date field for a legal document to notify the contract manager 15 days before a legal contract expires. The contract manager uses the 15 days to review and possibly negotiate a better contract. When the date arrives (that is, 15 days before the contract expires), the event occurs and the notification process is triggered through the workflow provider. The workflow provider constructs, issues, and manages the notification based on the configuration that you provided in the workflow provider and in CA APM.
The default notification method in CA APM supports email notifications using a workflow provider. You can send an email notification to any user or distribution list that is defined in your internal email system, even if the user is not a CA APM user. In addition, you can send an email to any external email address, if permitted by your email system.
You can also configure the notification process in the workflow provider to trigger any type of process. For example, you can set up the notification process to perform certain actions in another application when an event occurs in CA APM. For information about setting up different notification processes, see your workflow provider documentation.
You can define the following types of events to track and manage important changes to fields or objects:
  • Date events. Monitor a date field for an object and have the workflow provider notify you that an important date is approaching or has passed.
  • Change events. Monitor a field for an object and have the workflow provider notify you that the field value has changed.
  • Watch events. Monitor a field for an object and have the workflow provider notify you about a potential obstruction to completing a task.
How to Configure Events and Notifications
Events work in combination with notifications, which the workflow provider (for example, CA Process Automation) creates, to communicate information to your team members about important events and activity. To configure events and notifications, complete the following steps:
  1. Administrators grant permissions to users to manage events.
  2. Users with the correct permissions open an existing configuration and define date events, change events, and watch events. For more information about defining events, see Events and Notifications for CA APM.
  3. Users, when defining an event, map all workflow provider process parameters to a CA APM object attribute. For more information, see Workflow Provider Process Parameters.
  4. The workflow provider initiates the notification process.
Grant Permissions to Manage Events
You can grant permissions to users so they can configure the user interface and can define an event.
Follow these steps:
  1. Click the tab and optional subtab for the object that you want to configure.
  2. On the left, click CONFIGURE: ON.
    The configuration of the page is enabled.
  3. In the Configuration Information area of the page, select an existing global or local configuration.
    Global configuration changes affect all users, regardless of their role. Local configuration changes only affect users in the roles that are assigned to the selected configuration.
  4. In the Permissions area of the page, move Manage Events to the Granted Permissions list.
  5. (Optional) Select the Inherit Permissions from Parent Object check box to apply any security permissions from a top-level (parent) object to the lower-level (child) object using the same configuration.
    For example, you create a local configuration for an Organization. In the configuration, you deny permissions to change field labels, move fields, make fields required, and hide fields. After you save the configuration, you open Attachments under Organization and select the Inherit Permissions from Parent Object check box. All permissions from the Organization are applied to Attachments. In this example, because permissions to change field labels, move fields, make fields required, and hide fields are applied to the Organization, the permissions are also applied to the Attachment.
  6. Click Save Configuration.
    When you assign a configuration to a role, users in the role have permissions to define an event.