Which IIQ version are you inquiring about?
8.4p3
I have a use case where Workday team wants to delay attribute sync back to Workday XX days prior to start start date.
By default there is no setting in IIQ for this. Any suggestions?
Hi @talbright ,
would you be able to kindly rephrase/refine your requirement.
Basically you want to utilize Attribute Synchronization into a Workday target but not directly after the attribute changes (which is the OOTB behavior) but depending on the start date of the identity.
Can you please confirm or correct.
As per my current understanding you would be able to achieve the goal by introducing a custom Attribute Synchronization workflow which gives you great flexibility:
Either globally or via "Identity Mappings → Attribute → Sync with Workflow
Let us know if this helps.
You may also want to consider other options to achieve the goal: may I ask which attribute values are in scope?
From a performance side it might be better to establish a auxiliary attribute which is populated at the right point in time and stick to the OOTB Attribute Synchronization.
However, to assess the options we would need some more details regarding your requirements.
Best regards,
Daniel
Currently we aggregate Future Hires -14 days from Workday. Which will trigger Joiner workflow which provisions Active Directory. Attribute sync will then sync upn and email back to workday (used for SSO into Workday); those attributes are also synched to other targets using the same Identity Mapping.
What Workday team is asking is for those two attributes not to be synced to Workday before a set amount of days prior to start date on the Identity to allow users to use the default credentials they assign.
Hi @talbright ,
Try to write the Customization Rule and Apply the Logic as per Workday Team wants
You can achieve this using IdentityAttributeTarget rule instead of direct target mapping.
Rule logic has to be long the lines of
If identity start date is >= today + no of days prior then return value else null
eg: start date = 2026-10-26, days prior = 2, then the attribute will be sent to target on tomorrow, today nothing will be pushed to target.
So you want all the provisioning etc happening as part of joiner except attribute sync for these two attributes
Did you try the code the conditional logic in the transformation rule while doing target mapping?
The rule can be used to check your date conditions and only return the value if the condition is met.
If these attributes are rarely changed, you can do independent run rule task to push these values as well as attribute sync will always evaluated during refresh with attribute sync option set
I see the recommendations for using a transformation rule. Anyone have sample code they can share?
@talbright You can also try with Roles. Create a role with assignment rule, where you can check the date duration and return true/false. and attach a provisioning form with the attribute that you sync to workday.