Symptom
- How the Candidate Profile's ID is defined?
- Sometimes I can see gaps between the numbers. Is this expected?
Environment
SAP SuccessFactors Recruiting Management
Resolution
As soon as the candidate creates the new profile, the system uses a cache with 20 IDs and attribute each ID to a new profile, in an ascending order. This cache however, will have a time session and if no profile is created within this session, the system will disconsider all the remaining IDs that were not used. After this time session runs out, a new cache, with new 20 IDs, is created whenever a candidate creates a new profile.
Here is an example to illustrate the behavior:
- Last ID used by the system was "100";
- A new candidate created a profile;
- The system will generate a cache with 20 IDs;
- 10 candidates submitted a profile after that first candidate;
- Candidate IDs will then be from "101" until "111";
- None candidate applied during the current time session and it runs out;
- IDs from "112" to "120" will be disconsidered;
- A new candidate submitted a profile;
- The system will generate a cache with 20 IDs;
- These IDs will now be from "121" to "140";
Please notice that this is an expected behavior. These gaps are not considered as an issue.
Keywords
IDs, ID, design, work, gaps, gap, candidate, profile, how, it, works, work , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , How To