DE701803: Onboarding.complete API failed with 400 Bad Request error where information is partially saved for the employee, contractor and company
Impacted APIs
|
Method |
URI |
roleCode Value |
|---|---|---|
| POST | hcm/v2/applicants/{applicantid}/onboarding.complete | Practitioner |
Issue Description
Onboarding.complete API should complete the onboarding process and make an employee active. The API is returning a 400 Bad Request and the practitioner needs to login to the RUN Powered by user interface (UI) to complete the remaining process of onboarding.
Suggested Workaround
The practitioner needs to login to the RUN Powered by ADP UI to complete the remaining process of onboarding.
Issue: Departments Codelist
Impacted APIs
|
Method |
URI |
roleCode Value |
|---|---|---|
| GET | /codelists/hr/v3/worker-management/Departments | Practitioner |
Issue Description
Departments Codelist has an entry 0 with the description as Unassigned (shown below). This code cannot be used.
"listItems": [{
"codeValue": "0",
"shortName": "Unassigned",
"longName": "Unassigned"
},
Suggested Workaround
There are no workarounds available.
Issue: Event notification not supported through API
Impacted APIs
|
Method |
URI |
roleCode Value |
|---|---|---|
| POST | /hcm/v2/applicant.onboard | Practitioner |
| PUT | /hcm/v2/applicants/{applicant-id}/onboarding | Practitioner |
Issue Description
When onboarding an employee using API[POST:/hcm/v2/applicant.onboard] or updating the details of in progress employee using API[PUT:/hcm/v2/applicants/{applicant-id}/onboarding], the event notification is not generated.
Suggested Workaround
There are no workarounds available.
