Omada.OE.Solution.OIM.Assembly.AfterSaveHandlers Namespace

Adds new customer users to the "CIAM end users" user group. Used by the CIAM portal so customer users can logon via impersonation.

Ensures that new non-Ingestion objects are assigned a unique composed business key, e.g. contractor identities

The after save handlers related to derived systems.

Creates a ContextAssignment data object when an identity's org.unit is changed. The ContextAssignment is only valid for the number of days configured in the org unit context type The purpose of it is to ensure that the identity keeps his access in a grace period ///

Handles creation and updates of import profiles

Refreshes the logging configuration when the configuration object is saved. Note there is a risk that the transaction is rolled back after the log API has been re-configured resulting in an "inconsistency". Pushes the log configuration to OPS

Handles creation and updating of shadow data object types for resource types when a resource type or attribute set data object is created, updated or deleted. Handles creation and deleting of eventdefinitions used for sending out initial password emails.

After save handler for Resource assignments

This handler will create an Eventdefinition (timer based) for a SurveySchedule with a single CodeMethodAction, which launches a Survey. The Eventdefinition includes the SurveySchedule Id in its filterexpressions. It will also update event name when survey schedule name is changed

When importing system categories from changeset we have to assign them a new source system id

Writes to the (event) log when certain data objects are changed.

This class handles changing system status to removed. It archives all jobs using provisioning monitor. It cleans data related to the resources from the removed system and it disables provisioning for this system.