Programming Guides › Programming Guide for Java › Managed Objects › Access to Event Objects

Access to Event Objects

When a CA Identity Manager task reaches the asynchronous phase (that is, after the user clicks Submit on the task screen and the user-supplied data has been validated), CA Identity Manager breaks down the task into its component events.

These events can be accessed by custom objects that CA Identity Manager calls during the asynchronous phase, and by workflow scripts that call the methods in the Workflow API.

Event objects are accessed through one of the following interfaces. Each interface allows read/write access to a managed object in a CA Identity Manager event. EventContext also allows the generation of secondary events:

EventContext

• Extends IMPersistentContext, which extends IMContext.
• EventContext allows information to be persisted throughout the life of an event.
• Extended by WorkflowContext.

  EventContext is also the ...Context object for the Event Listener API.

EventROContext

• Extends IMContext.
• Extended by ExposedEventContextInformation, NotificationRuleContext, ParticipantResolverContext.

If you modify a managed object in an event, CA Identity Manager commits the modifications to the data store after any approvals required for the execution of the event have been provided and the execution of the event is complete. You do not call modifyObject() to persist the modifications.