You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Sample payload and review of workerJourney replacing allocateChecklist REST API

in Journeys

As communicated via release notes we know support will be discontinued in 25C for current REST API allocateChecklist endpoints and we need to use workerJourney endpoints instead.

We are currently using the below endpoints:

  • Get Checklist by PersonNumber - hcmRestApi/resources/11.13.18.05/allocatedChecklists?orderBy=AllocatedChecklistId&q=(PersonNumber = 'XXXXX')
  • Get Tasks assigned by ChecklistId and Performer (PersonNumber) - hcmRestApi/resources/11.13.18.05/allocatedChecklists/999999999/child/allocatedTasks?limit=50&fields=ActionType,AllocatedChecklistId,AllocatedTaskId,TaskName,Status,PerformerOrigSystem,&offset=0&q=(PerformerOrigSystem= 'XXXXXX')
  • Updated Task Status by ChecklistId and TaskId- hcmRestApi/resources/11.13.18.05/allocatedChecklists/999999999/child/allocatedTasks/999999999

Below are the endpoints I think replace those above:

  • Get a Journey by PersonNumber - /hcmRestApi/resources/11.13.18.05/workerJourneys
Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!