Building Blocks for External Interactions

CA Identity Governance Programming Guide › Customizing Business Flows › Standard CA Identity Governance Building Blocks › Building Blocks for External Interactions

Building Blocks for External Interactions

This section describes building blocks that communicate with provisioning endpoints, mail servers, and other external platforms.

Send Mail

Use the Send Mail building block to create a node that sends email to a group of users. CA Identity Governance processes the request using its default email target and other settings.

This building block exposes the following parameters:

emailTemplateName

Specifies which template to use for the email. Of the templates defined in the CA Identity Governance server, this building block uses only templates associated with the Customized Process Email event.

Note: This building block sends the same email text to all recipients. Do not include personal data fields in email templates that you use with this building block.

The following default templates, installed with CA Identity Governance, are used for aggregated workflows:

CommitChanges - Concludes a self-service request and implements the review decisions that were submitted.
StartApproval - Initiates the change approvals phase of a certification.

To

Defines a list of users that receive the email. This value is a comma-separated list of email addresses or CA Identity Governance users. You can also specify parameters that contain lists of email addresses or CA Identity Governance users.

emailParams

Defines values for variable data fields in the email template. This value is a comma-separated list of variable=value statements. For example, if the template contains the ${campaignType} and ${flowName} variables, you can assign static values as follows:

campaignType="Annual Privileges Review", flowName="Managers Phase"

Notify Model Change / Notify Aggregate Model Change

Workflows can result in changes to the model configuration of a universe. You can export these changes to provisioning endpoints. CA Identity Governance communicates these changes using the Model Event Notification API.

Workpoint processes query the following CA Identity Governance system parameters to determine the behavior that is enabled on the CA Identity Governance server:

approval.isModelChangeNotificationOn

Indicates whether you enable the model event notification.

modelEvent.producer.fireEvent

Specifies what events trigger change notification. Valid values include:

Atomic: Triggers an event after every approval during a workflow.
Aggregate: Triggers an event when all approvals complete for a workflow.

Use the Notify Model Change building block to create a node that exports changes that result from a single review task. Your process logic activates this node when modeEvent.producer.fireEvent is Atomic.

Use the Notify Aggregated Model Change building block to export all the changes that result from an entire workflow. Your process logic activates this node when modeEvent.producer.fireEvent is Aggregate.

The Notify Model Change building block exposes the following standard parameters:

A set of node parameters that specify the focal entities of the process.
General process parameters that identify the target universe and configuration file.

In addition, this building block exposes the following unique parameters:

Action

Describes the change to the specified link or entities. Valid values include:

Add: Indicates a new entity, attribute value, or link between specified entities.
Delete: Indicates that the entity, attribute, or link specified is removed from the configuration file.

More information:

Model Event Notification API