This article explains what are the precautions while doing an instance refresh for Recruiting Marketing customers.
SuccessFactors Recruiting Marketing (RMK) - All Versions
Reproducing the Issue
If after the instance refresh you do not fix the configuration described in the resolution of this article, you may start facing issues for the Recruiter SSO, Candidate SSO and to post jobs in RMK.
Important: Note that the Recruiting Engineering team recommends that customers do not request Operations refresh instances that have Candidate SSO enabled as their processes don’t adequately sever the relationship between the refreshed test instance and the RMK Production site.
In case that you have Recruiting Marketing and will request an instance refresh, the following information should be saved first:
- API Credentials – save the settings in Provisioning > Recruiting Marketing Settings. The Security Key will not be visible there, so this information has to be collected in Command Centre. If you do not have access to Command, and do not have anyone to ask to check this, open a RMK support incident asking this information.
- Data Center URLs – save the URLs presented in Provisioning > Configure Recruiting Marketing Datacenter URL
After the instance refresh, the information above should be added/updated again. You may also ran a full feed in provisioning (job type “sync all external postings”) and check if the owner of the job doesn’t need to be updated as well.
Instance Refresh Recruiter SSO Candidate SSO Jobs not posting Recruiting Marketing RMK , KBA , LOD-SF-RMK , Recruiting Marketing , How To