Workday Connector - ON_LEAVE Attribute support for multiple leave events

Identity Security Cloud (ISC) ISC Discussion and Questions
1

The following table lists the account attributes:

The Workday connector provides support to aggregate fields in addition to the fields present in the default account schema. For more information, refer to XPATH to Support Additional Standard Attributes in Schema.

This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/connectors/workday/help/integrating_workday/account_attributes.html
2

I believe the XPath for ON_LEAVE is incorrect, and should be Worker_Data/Employment_Data/Worker_Status_Data/Leave_Status_Data[1]/@On_Leave rather than Worker_Data/Employment_Data/Worker_Status_Data/Leave_Status_Date[1]/@On_Leave

Also note that this is a multi-valued field, and we have found that selecting the first value for a user with multiple leaves will result in pulling a prior leave that has already ended and result in a value of 0 even if the user is currently on leave.

3

Hi Mike! Thank you for your input. We’ve created a Jira issue to track the effort and we’ll update the comment thread when it’s been addressed: CONDOCS-4837

4

Hi Mike. I fixed the issue with the filepath, and the page has been updated.

I spoke with our engineering team regarding your point about it being a multi-valued field, and I was told that this attribute is actually a single-valued field. Since this is more of a technical question, I’ve moved your comment to our ISC Discussions and Questions category for greater help from the community. If you are encountering any issues, you can also reach out to our Support team.

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

7

@Mike_Trachta, the topic has been reopened.

8

Here is an example from our environment (with some redacted data), where the field is multi-valued. You an see the first entry is for a prior leave which is no longer active, and the second entry is for the current active leave. We had to update our XPath to account for this, otherwise the first entry takes precedence and inaccurately reported that this user was not on leave.

Our HR team has also verified that a user could be on multiple active leaves at a given time.

<wd:Leave_Status_Data>
    <wd:Leave_Request_Event_Reference>
        <wd:ID wd:type="WID">REDACTED</wd:ID>
        <wd:ID wd:type="Request_Leave_of_Absence_ID">LEAVE_REQUEST_EVENT-3-350</wd:ID>
    </wd:Leave_Request_Event_Reference>
    <wd:Leave_Request_Description>Absence Request: Redacted Name</wd:Leave_Request_Description>
    <wd:Leave_Return_Event_Reference>
        <wd:ID wd:type="WID">REDACTED</wd:ID>
    </wd:Leave_Return_Event_Reference>
    <wd:On_Leave>0</wd:On_Leave>
    <wd:Leave_Start_Date>2024-02-05</wd:Leave_Start_Date>
    <wd:Estimated_Leave_End_Date>2024-02-06</wd:Estimated_Leave_End_Date>
    <wd:Leave_End_Date>2024-02-06</wd:Leave_End_Date>
    <wd:Leave_Last_Day_of_Work>2024-02-04</wd:Leave_Last_Day_of_Work>
    <wd:Leave_of_Absence_Type_Reference>
        <wd:ID wd:type="WID">REDACTED</wd:ID>
        <wd:ID wd:type="Event_Classification_Subcategory_ID">NLD_Sick_Leave</wd:ID>
        <wd:ID wd:type="Leave_of_Absence_Type_ID">NLD_Sick_Leave</wd:ID>
    </wd:Leave_of_Absence_Type_Reference>
    <wd:Benefits_Effect>0</wd:Benefits_Effect>
    <wd:Payroll_Effect>0</wd:Payroll_Effect>
    <wd:Paid_Time_Off_Accrual_Effect>0</wd:Paid_Time_Off_Accrual_Effect>
    <wd:Continuous_Service_Accrual_Effect>0</wd:Continuous_Service_Accrual_Effect>
    <wd:Stock_Vesting_Effect>0</wd:Stock_Vesting_Effect>
</wd:Leave_Status_Data>
<wd:Leave_Status_Data>
    <wd:Leave_Request_Event_Reference>
        <wd:ID wd:type="WID">REDACTED</wd:ID>
        <wd:ID wd:type="Request_Leave_of_Absence_ID">LEAVE_REQUEST_EVENT-3-735</wd:ID>
    </wd:Leave_Request_Event_Reference>
    <wd:Leave_Request_Description>Absence Request: Redacted Name</wd:Leave_Request_Description>
    <wd:On_Leave>1</wd:On_Leave>
    <wd:Leave_Start_Date>2024-06-05</wd:Leave_Start_Date>
    <wd:Estimated_Leave_End_Date>2024-10-31</wd:Estimated_Leave_End_Date>
    <wd:Leave_Last_Day_of_Work>2024-06-04</wd:Leave_Last_Day_of_Work>
    <wd:Leave_of_Absence_Type_Reference>
        <wd:ID wd:type="WID">REDACTED</wd:ID>
        <wd:ID wd:type="Event_Classification_Subcategory_ID">GBL_Garden_Leave</wd:ID>
        <wd:ID wd:type="Leave_of_Absence_Type_ID">GBL_Garden_Leave</wd:ID>
    </wd:Leave_of_Absence_Type_Reference>
    <wd:Benefits_Effect>0</wd:Benefits_Effect>
    <wd:Payroll_Effect>1</wd:Payroll_Effect>
    <wd:Paid_Time_Off_Accrual_Effect>0</wd:Paid_Time_Off_Accrual_Effect>
    <wd:Continuous_Service_Accrual_Effect>0</wd:Continuous_Service_Accrual_Effect>
    <wd:Stock_Vesting_Effect>0</wd:Stock_Vesting_Effect>
</wd:Leave_Status_Data>
9

Hi Mike, thanks for the code sample. I’ll reach out to engineering to see what they say.