Rival Workflow integration
To personalize the onboarding experience for the hire, Rival Workflow requires some background information before it can launch the onboarding process. If your ATS does not, or cannot track all of this information, a recruiter can supply the information in Rival Workflow.
Your ATS requests a security token from Rival Workflow to use in subsequent calls. Rival Workflow validates the security token request and makes sure the new hired employee is not a duplicate.
These are the parameters your ATS should post to Rival Workflow.
| Parameter | Description |
|---|---|
| PartnerKey | A key Rival gives to each partner. Points to that partner’s data in a shared database. |
| SharedSecret | A shared secret used, to along with the RETURN_ADDRESS, to authenticate the request. |
| LifesuiteCode | A code to identify the Rival Workflow customer that was entered as part of the customer configuration. Rival Workflow validates that it is pointing to the right customer to make sure there has been no misconfiguration. |
| Class | The class of this service that was entered as part of the configuration. Staging, Prod, Test. Rival Workflow uses this to validate it is pointed to the right class to make sure there had been no misconfiguration. |
| ATSName | Rival Workflow stores this so that it can be placed in the audit notes. |
| RecruiterName | Rival Workflow stores this so that it can be placed in the audit notes. |
| RecruiterID | An ID to identify the recruiter. Reserved for future use. |
| ATSCandidateID | ID that your ATS will use to identify the newly hired employee. This key must be immutable with respect to the newly hired employee for this job. Rival Workflow uses this ID to determine whether the employee has been already imported. If the candidate were subsequently hired into a different job, Rival Workflow would expect a different ATSCandidateID. Rival Workflow:
|