Outbound Mapping - Evolveum Docs

Quoted on this wiki

Every place a page here uses this source, in the order the words come in it.

1. Workaround “This way, adding accounts to the target resource will not be interrupted during the reconciliation, and the attribute will be added during a subsequent recomputation.” Example condition

   In Account-contact mapping

2. Workaround “Define a condition in the troublesome outbound mapping that makes sure the mapping is ignored, and that adds a trigger for a recomputation at a later point, during which the attribute will be modified.” Example condition

   In Attribution data quality

3. Cause “As a result, when you add a new account in midPoint with attributes that cannot be modified upon creation, such connectors will not be able to both create and set the attributes during a reconciliation, and they will not add the new account in the target resource at all.” Workaround

   In Enrichment APIs and integrations

4. Cause “Attributes that cannot be set upon creation require two steps - first creating, and only then modifying.” Workaround

   In Mailbox provisioning