IIQ Version - 8.3 Hello Experts, We have an identity attribute called Entity. Whenever this attribute changes, a few dependent attributes of an application also change which need to be provisioned to the target system. Currently we have added 10+ attributes for the same application in target mappi…

There are 15 fields dependent on the ‘Entity’ attribute value change which we need to push to target system with some data transformation. Currently we have defined 15 such data transformation rule attached to the target mapping. However, thinking if this is the best option or should we leverage the…

this sounds like an Lifecycle event base requirement, I would do this in a custom workflow which will handle the logic calculation for the 15 fields for each applications in a provisionPlan. example: Create an event called EntityChanges of type Attribute change. Point the your “entity” attribute …

Try handling this using LCE and you can give trigger condition as attribute based changes where you can put “Entity”. Create a custom wf and call it Inside wf create plan and execute it. if you want request generation then use OOTB LCM and update one of your steps to create plan

Hi @shamal_khokle , as per my understanding you are describing the following situation: You have an identity attribute and numerous target system (schema) attributes which should be updated as soon as the identity attribute changes. Can you please confirm or correct. If my understanding is corre…

15 dependent fields is unusual, but if that is what you need then it should work ok.

Hi @shamal_khokle , This requirement can be achieved by “Value change Rule” also. You can monitor performance and decide which option is suitable.

@shamal_khokle - If you only need to provision the new value, then having 10-15 target mappings is the best solution. If you need to perfom additional steps whenever the value changes, you can create a lifecycle event or have a value change workflow in the identity mappings.

@shamal_khokle You need to understand the tradeoffs. If your Target Mappings are working fine, then you can continue with it. If you face any issues like identity deadlock, refresh taking longer, etc., then you can think of other options like Lifecycle Events, where you refresh task can launch the w…

First things first. You should not create an Identity Attribute that starts with a capital letter. All Identity Attributes should be either all lower case or camelCase. No underbars, no numbers, no repeated caps. No “ID”. That’s why the example is costCenter. You should have called it entity …

Identity Mapping Best Practice

IdentityIQ (IIQ) IIQ Discussion and Questions

msingh900 (Manish Singh) January 17, 2026, 8:46am 6

I would suggest you create a Value Change Workflow and add your logic to change all the other 15 attributes by building a provisioning plan.

Topic		Replies	Views
Best practice for provisioning attributes to end points IIQ Discussion and Questions workflows , rules , identityiq , provisioning	4	88	December 22, 2025
Identity attribute sync to target system: Push only attributes on the on change event (e.g., identity attribute updated) IIQ Discussion and Questions identityiq	10	335	September 23, 2024
Detecting Identity Attribute Changes in SailPoint JDBC Provisioning Rule ISC Discussion and Questions aggregation , identity-security-cloud , provisioning , connectors	3	82	April 23, 2025
Services Standard BeforeProvisioning Rule ISC Discussion and Questions rules , identity-security-cloud , provisioning	5	327	August 16, 2024
Update Provisioning Policy behavior ISC Discussion and Questions identity-security-cloud , provisioning , connectors	4	150	December 26, 2025

Identity Mapping Best Practice

Related topics