Issue with Workday Integration for Fetching Job Profiles

[Jay]

Hello @Susan Britt, @Ankur Bawiskar , @Uncle Rob , 

I am encountering an issue with our Workday integration when fetching Job Profiles. We are utilizing out-of-the-box (OOB) flows, specifically "Get Job Profiles" and "Get Job Profile Service."

Upon running the "Run Workday Integration" flow today, the following error occurred:

"Flow Designer: Operation(Run Workday Service.If$3.389457f51b92545067817669cc4bcbd5.DYNAMIC_FLOW_BLOCK$3.getFlowOutputs) failed with error: com.snc.process_flow.exception.ProcessAutomationException: Call block 'Get Job Profiles Service.DS_action_wrapper-96da5f22dbeb5010127e3764e2961940.96da5f22dbeb5010127e3764e2961940.Datastream$1.item$1' failed. Detail: Error: Cannot read property 'Job_Level_ID' from undefined, Detail: Cannot read property 'Job_Level_ID' from undefined." please refer attached images for more info.

It's important to note that these OOB flows are read-only and were functioning correctly prior to our upgrade to the Vancouver Patch 10. However, I'm uncertain if the issue is related to the upgrade, as the flows are not yielding errors in production, though they are also not retrieving any data from Workday.

Please provide guidance on how to resolve this issue or suggest any potential steps we should take to investigate further.

Thank you for your assistance.

Best regards!
Jay

[rcard11]

Hey there!  We are having the same issue and SN support has been stumped so far with a resolution.  Did you happen to get this resolved?  Thank you!

[Jay · Accepted solution]

Hi @rcard11,
We raised a ServiceNow ticket for this issue, and ServiceNow informed us that there is a problem with the Workday integration plugin. The fix for this PRB will be included in version 3.1.3. Currently, we are using version 3.1.1. 

[rcard11]

Thank you!  Did they provide a workaround for you?  Not being able to pull in Job Profiles is a bit of a problem for us.  

[Seema Hegde]

That sounds like the response parsing script had an error. Can you see what was returned from the call? I would take the response body and test the script on it separately. Maybe the expected Xpath for the attribute is a bit off or changed?

But definitely reach out to support if the integration was broken by the upgrade.