Problem Statement:
As part of our migration from SailPoint IdentityIQ (IIQ) to Identity Security Cloud (ISC), we are evaluating how to replicate the current identity attribute synchronization process used for Oracle EBS.
In the current IIQ implementation, we leverage a Lifecycle Event to trigger provisioning for specific Oracle EBS person table fields that are not managed by the out-of-the-box EBS connector. This provisioning invokes an EBS stored procedure whenever specific HR-related identity attributes change. Some of these attributes are not even stored in EBS but are used to trigger business-critical downstream processes via custom stored procedures.
In IIQ or ISC, attribute sync typically occurs by reading changes from source and target systems. However, in this case, the sync is triggered proactively based on attribute changes, rather than relying solely on source/target reads.
We are seeking a comparable approach in ISC that allows for similar behavior — triggering attribute sync or downstream processes when identity attributes change, especially when those attributes are not present in the target (EBS) system. The client prefers to retain this functionality as-is due to its critical role in their existing business logic and is resistant to altering the current model.
We planned to use Workflows but we can’t trigger update account provisioning yet with workflow.