Symptom
Onboarding operates out of multiple datacenters, which themselves operate on separate release cycle schedules. For example, Arizona datacenter (DC4) operates on a different release schedule than Virginia (DC8). Determining what version of Onboarding you are running can be a helpful addon to your Support case, and can be very easily found.
Resolution
How To
In the URL for the Onboarding environment you are in, remove everything after the domain adress and the partner directory. As an example, we'll use this for partners operating out of a Zerolag environment, as well as a SuccessFactors Datacenter 4 Arizona environment.
You should be left with this information in the address bar:
Now, add this information after the new address:
You should be left with these URLs:
Hitting enter should send you to a page that yields this information. Copying and pasting this into your case is an extremely helpful way to specifically pinpoint the issue you may be experiencing.
Release: | 1411.7.20010.49297 |
Revision: | 704637 |
Server: | WWW01 - 6.0 |
Environment
This can be performed in any environment that Onboarding is running in. Here's a quick list of links to various datacenter application versions:
DC4: https://onboarding4.successfactors.com/ + partner name (eRecruit, KMS, Kenexa, etc) + /AppAdmin/Sys/AppVersion.aspx
DC8: https://onboarding8.successfactors.c...ppVersion.aspx
DC10: https://onboarding10.successfactors....ppVersion.aspx
Zerolag: https://xpresshr.online-onboarding.com/ + partner name (eRecruit, KMS, Kenexa, etc) + /AppAdmin/Sys/AppVersion.aspx
.
Keywords
KBA , LOD-SF-OBD-RCM , Onboarding Core , How To