How do Sailpoint handle the termination of Workday Rescinding Hires

[vsekar7 (Vengatesan Sekar)]

How do Sailpoint handle the termination of Workday Rescinding Hires

I have tried to add new account schemas as mentioned in the below document and getting the below error in account aggregation task:

Rescinded and Corrected User Records

Error!

[ InvalidConfigurationException ]
[ Possible suggestions ] You cannot initiate this action because there are other pending or completed actions for the person that conflict with this one.
[ Error details ] Validation error occurred. Invalid ID value. ‘IS_RESCINDED’ is not a valid ID value for type = ‘Business_Process_Type’

[vsekar7 (Vengatesan Sekar)]

Hi Experts,

Can anyone help me with this

[zachm117 (Zach Mullins)]

Hi @vsekar7 ,

Did you also enable the Aggregate Rescinded Future Hires option in the UI in addition to adding this attribute to the schema?

Thank you,

• Zach

[vsekar7 (Vengatesan Sekar)]

Hi @zachm117 ,

Yes and the Workday account aggregation task is getting failed with below error:

Error!

[ InvalidConfigurationException ]
[ Possible suggestions ] You cannot initiate this action because there are other pending or completed actions for the person that conflict with this one.
[ Error details ] Validation error occurred. Invalid ID value. ‘IS_RESCINDED’ is not a valid ID value for type = ‘Business_Process_Type’

[zachm117 (Zach Mullins)]

Are you trying to aggregate rescinded future hires or rescinded past hires (or both)?

[vsekar7 (Vengatesan Sekar)]

Hi @zachm117 ,

Yes and the Workday account aggregation task is getting failed with below error:

Error!

[ InvalidConfigurationException ]
[ Possible suggestions ] You cannot initiate this action because there are other pending or completed actions for the person that conflict with this one.
[ Error details ] Validation error occurred. Invalid ID value. ‘IS_RESCINDED’ is not a valid ID value for type = ‘Business_Process_Type’

Also I have added the xpath for “IS_RESCINDED” as “ns1:Worker_Data/ns1:Employment_Data/ns1:Worker_Status_Data/ns1:Hire_Rescinded” whereas still getting the same error on account aggregation.

[zachm117 (Zach Mullins)]

If you are using both options:

1. Ensure that your offset days are non-zero and non-null values.
2. Ensure RESCINDED_DATE and RESCINDED_DESCRIPTION are also added to your account schema for rescinded past hire records (in addition to IS_RESCINDED). None of these require an XPath definition on the connector. If you have one defined for any of these 3 attributes, try deleting them.
3. Try adding FUTURE_ACTION, FUTURE_DATE, and LAST_DAY_OF_WORK to your account schema also.
   1. FUTURE_ACTION XPath: ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data/ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type='Business_Process_Type']='Hire Employee']/ns1:ID[@ns1:type='Business_Process_Type'] |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data/ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type='Business_Process_Type']='Contract Contingent Worker']/ns1:ID[@ns1:type='Business_Process_Type'] | ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data/ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type='Business_Process_Type']='Terminate Employee']/ns1:ID[@ns1:type='Business_Process_Type'] |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data/ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type='Business_Process_Type']='Onboarding']/ns1:ID[@ns1:type='Business_Process_Type'] |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data/ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type='Business_Process_Type']='End Contingent Worker Contract']/ns1:ID[@ns1:type='Business_Process_Type']
   2. FUTURE_DATE XPath: ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data[ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type='Business_Process_Type']='Hire Employee']]/ns1:Transaction_Effective_Moment |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data[ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type='Business_Process_Type']='Contract Contingent Worker']]/ns1:Transaction_Effective_Moment |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data[ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type='Business_Process_Type']='Terminate Employee']]/ns1:Transaction_Effective_Moment |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data[ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type='Business_Process_Type']='Onboarding']]/ns1:Transaction_Effective_Moment |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data[ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type='Business_Process_Type']='End Contingent Worker Contract']]/ns1:Transaction_Effective_Moment
   3. LAST_DAY_OF_WORK XPath: ns1:Worker_Data/ns1:Employment_Data/ns1:Worker_Status_Data/ns1:Termination_Last_Day_of_Work
4. Check your source to confirm certain features are enabled
   1. connectorAttributes.pullRescindedHiresPast: true
   2. connectorAttributes.pullRescindedHires: true
5. Try turning off one option, ‘Aggregate Rescinded Future Hires’ for example, and seeing if just the ‘Aggregate Rescinded Past Hires’ option alone works to help narrow down the issue.

[vsekar7 (Vengatesan Sekar)]

Hi @zachm117 ,

Please find the below mappings which is already available below:

1. FUTURE_ACTION XPath:

ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data/ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type=‘Business_Process_Type’]=‘Hire Employee’]/ns1:ID[@ns1:type=‘Business_Process_Type’] |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data/ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type=‘Business_Process_Type’]=‘Contract Contingent Worker’]/ns1:ID[@ns1:type=‘Business_Process_Type’] | ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data/ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type=‘Business_Process_Type’]=‘Terminate Employee’]/ns1:ID[@ns1:type=‘Business_Process_Type’] |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data/ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type=‘Business_Process_Type’]=‘Onboarding’]/ns1:ID[@ns1:type=‘Business_Process_Type’] |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data/ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type=‘Business_Process_Type’]=‘End Contingent Worker Contract’]/ns1:ID[@ns1:type=‘Business_Process_Type’]

2. FUTURE_DATE XPath:

ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data[ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type=‘Business_Process_Type’]=‘Hire Employee’]]/ns1:Transaction_Effective_Moment |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data[ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type=‘Business_Process_Type’]=‘Contract Contingent Worker’]]/ns1:Transaction_Effective_Moment |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data[ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type=‘Business_Process_Type’]=‘Terminate Employee’]]/ns1:Transaction_Effective_Moment |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data[ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type=‘Business_Process_Type’]=‘Onboarding’]]/ns1:Transaction_Effective_Moment |ns1:Worker_Data/ns1:Transaction_Log_Entry_Data/ns1:Transaction_Log_Entry/ns1:Transaction_Log_Data[ns1:Transaction_Log_Type_Reference[ns1:ID[@ns1:type=‘Business_Process_Type’]=‘End Contingent Worker Contract’]]/ns1:Transaction_Effective_Moment

3. LAST_DAY_OF_WORK XPath:

   ns1:Worker_Data/ns1:Employment_Data/ns1:Worker_Status_Data/ns1:Termination_Last_Day_of_Work

4. IS_RESCINDED XPath:
   ns1:Worker_Data/ns1:Employment_Data/ns1:Worker_Status_Data/ns1:Hire_Rescinded

But still getting this error:

[ InvalidConfigurationException ]
[ Possible suggestions ] You cannot initiate this action because there are other pending or completed actions for the person that conflict with this one.
[ Error details ] Validation error occurred. Invalid ID value. ‘IS_RESCINDED’ is not a valid ID value for type = ‘Business_Process_Type’

[zachm117 (Zach Mullins)]

@zachm117

Ensure RESCINDED_DATE and RESCINDED_DESCRIPTION are also added to your account schema for rescinded past hire records (in addition to IS_RESCINDED). None of these require an XPath definition on the connector. If you have one defined for any of these 3 attributes, try deleting them.

Try removing the XPATH mapping for IS_RESCINDED and just leave it in the account schema.

[vsekar7 (Vengatesan Sekar)]

Hi @zachm117 ,

Still the same.

[lampard08 (Chelsea Blue)]

This looks like is happening as a provisioning action not aggregation. do you have attribute sync set for this attribute?