Overview#Event Transformation Policy Set or (ETP) alter the Meta-directory engine's view of the events that happen in the Identity Vault or the connected application. The most common task performed in an Event Transformation policy is custom filtering, such as scope filtering and event-type filtering.
The Event Transformation Policy operates on events reported on a channel input. The Subscriber and Publisher channels usually have different Event Transformation Policies. The purpose of the Event Transformation Policy is to modify the report of what happened (the events) before the events are processed further by Identity Manager.Publisher Flow the Event Transformation Policy Set uses the Policy Set Interval Values of 5 and is applied to events issued by the shim to Identity Manager and is applied after the Input Transformation Policy and Schema Mapping Policy, but before any other policy-based event processing. Subscriber Flow the Event Transformation Policy Set uses the Policy Set Interval Values of 4 and is applied to events received by Identity Manager from Identity Vault and is applied before any other policy-based event processing.
There are many common applications for the Event Transformation Policy, including:
- scope filtering (e.g., only allow events on objects in a particular subtree, or with a particular attribute value)
- custom event filtering (e.g., disallow moves or deletes)
- transforming the event directly into a custom command to be passed to the application
- generating additional events
Scope filtering removes unwanted events based on event location or an attribute value. For example, removing the event if the department attribute is not equal to a specific value or is not a member of a specific group.
Event-type filtering removes unwanted events based on event type. For example, removing all delete events.