3539368 - SF Recruiting Offer Letter Integration With OpenText Sending ownerId=0 After Offer is Signed via DocuSign - Recruiting Management

Summary of SF Recruiting Offer Letter Integration with OpenText:

When a Recruiting User creates an Offer Letter, SF RCM will use an API to send the Offer Letter and some details about it (like ownerId, uploaderId, documentCategory, etc.) to OpenText. If the customer uses DocuSign, SF RCM will call the API again to send another update to OpenText after the Offer Letter is signed by the Candidate. This second update may include a certificate file.

The Issue:

Before the Offer Letter is signed, all the details (such as ownerId) are sent correctly. However, after the Offer is signed, the second API incorrectly sends the ownerId and uploaderId equal "0" and "v4admin" instead of the Candidate ID and the User's ID who uploaded it.

SAP SuccessFactors Recruiting Management

The issue will be fixed as part of the OpenText Workspace enhancements within 2H 2024: 3536200 - Offer Letters Integration Enhancements with OpenText Workspace in 2H 2024.

3536200 - Offer Letters Integration Enhancements with OpenText Workspace in 2H 2024

offer, missing, op, open, text, ownerID, candidate, ID , KBA , LOD-SF-RCM-CAO , Candidate Offers, Offer Letters , LOD-SF-RCM-INT , Integration Center & Intelligent Services , Problem