Entitlement Aggregating for a calculated Workday Attribute failing

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hello,

We are trying to aggregate a custom calculated field from our Workday Source as an Entitlement. We leveraged the integration field override to bring the attribute within the account schema called ‘Timekeeper_Role_Assignment__c’ and we’ve assigned this as an entitlement. However, when we run the entitlement aggregation, we’re unable to pull in any entitlements. We’ve also created an XPATH entry for the calculated field, however we’re still unable to aggregate this.

The XPATH is as follows - ws:Worker_Sync/ws:Worker/ws:Additional_Information/ws:Timekeeper_Role_Assignment

How can we aggregate this attribute as an entitlement? Does the attribute need to be created elsewhere?

2

Hi @nyeung Have you validated the XPath using Postman or similar?

3

Hi Jeremy, our workday team has confirmed that this is the XPath to said attribute

4

Thanks @nyeung But, tbf, that’s not the question i asked :wink:

5

I ask because I don’t recognise that api response “ws:Worker_Sync”. I think your WD team are confused between WD Connectors and the SP Connector. The SP Connector uses the Human_Resources Get_Workers SOAP Web Service to pull information from WD and has a root XML path of wd:Response_Data/wd:Worker (ISC uses the ns1: xml namespace). WD Connectors are used to push information from WD.

6

PS to get it to work try making sure you’ve got the Integration System ID in Aggregation settings and remove the XPath.

OR

Work out the correct XPath, using Postman or equivalent (look under wd:Response_Data/wd:Worker/wd:Worker_Data/wd:Integration_Field_Override_Data) and add the XPath (with ns1: namespace) but don’t include the “__c” suffix in the attribute name.

7

Hi @nyeung when leveraging the Integration Field Override in SailPoint to pull custom attributes from Workday, we generally do not need to specify an XPath. Please ensure the permissions and steps Integration Field Override are configured as defined here

8

Hi @j_place/@prashanthrns, thank you for your response! We are leveraging the Integration Field Override in Sailpoint and you’ are both correct, I did not need to define the XPath to pull in the attribute. We defined the attribute within the account schema & was pulling this via account aggregation, but I was so convinced that an entitlement aggregation was needed to populate the entitlements. Turns out, we didn’t need to and the integration was working all along.