Calculation affecting events resolver

The CalculationAffectingEventsResolver extension is responsible for queuing identities for calculation when an event occurs in the Omada Identity as described in the Event-based queuing section.

Configuration and example

You can configure the extension to specify the properties on the involved objects that trigger a calculation for an identity.

If you want to specify additional properties that trigger the calculation when they have been changed, add their system names to the comma-separated list for the data object type.

<add type="Omada.RoPE.Controller.OISX.Extensions.CalculationAffectingEventsResolver, Omada.RoPE.Controller.OISX">
    <settings>
        # We state the properties (per DOT) that are relevant from an engine perspective when a data object is changed.
        <add key="DOT#Identity" value="IDENTITYID,FIRSTNAME,LASTNAME,VALIDFROM,VALIDTO,IDENTITYSTATUS,OUREF,EXPLICITOWNER,ODWBUSIKEY" />
        <add key="DOT#OrgUnit" value="PARENTOU,EXPLICITOWNER,MANUALOWNER" />
        <add key="DOT#System" value="EXPLICITOWNER" />
        <add key="DOT#Resource" value="CHILDROLES,ACCOUNTTYPE,EXPLICITOWNER,MANUALOWNER,ATTRIBVALUES,SKIPPROVISIONING,VALIDFROM,VALIDTO,CLT_TAGS" />
        <add key="DOT#ResourceFolder" value=""EXPLICITOWNER,MANUALOWNER,CLT_TAGS" />
        <add key="DOT#ResourceAssignment" value="VALIDFROM,VALIDTO,ROLEASSNSTATUS,ATTRIBVALUES,ACCOUNTNAME" />
        <add key="SelfManagementExplicitOwners" value="EXPLICITOWNER,MANUALOWNER"/>
    </settings>
</add>

info

The SelfManagementExplicitOwners optional setting expects a comma separated list of settings. If no list is provided, then EXPLICITOWNER is used by default. Properties from this setting must be also set on the DOT setting for new or removed manual owners to be correctly recalculated.