We send a value that we catch from our HRIS system to another source’s attribute. A new value has been added to the HRIS system but is still not accepted by the app. We’d like to catch the account creation event, and change the attribute value to something else that’s supported by the app.
Example:
Values from Workday: val1, val2, val3
Values accepted by the app: val1, val2
Desired config: when val3 is captured from the HRIS, ISC should change it to val1 and send it to the app
In my oppinion, this can be done only by a BeforeProvisioningRule. Is there any other easy way to solve this problem?
Hi @khalilgahbiche ,
I believe you can try to build a Value Mapping Transform which would check the incoming value and map it to an acceptable value before sending it to the target system.
If you don’t need the val3 ever, you could apply this transform to the attribute in the identity profile. If you need val3 for some apps, you could create a new identity attribute with the modified list.
