Attributes, levels and versions

Seniority date attributes are the individual dates you can calculate and store — several of them, which is the mechanical answer to the four-figures problem. They exist at person, work relationship and assignment level. Level decides what survives, and it matters in exactly one way you need to remember: person-level seniority survives a change of employer within the group; assignment-level does not. So the level is not a technical preference — it is the answer to "does a transfer count". Choose per purpose: group service uses one level, a role-specific seniority uses another. Versions. The feature has evolved through versions with different capabilities, and your environment may be on an older one. Check which, before you design rules against capabilities you may not have. Cumulative versus adjusted service is the other axis — how breaks are treated — and what drives recalculation, and when it runs, matters because the numbers…

In this module: Module 12 · Seniority Dates

1. 1What seniority dates are for
2. 2Attributes, levels and versions
3. 3Configuring seniority rules
4. 4Common rule configurations
5. 5Fast formulas and overrides
6. 6Migration and what breaks
7. 7Lab: three attributes, three entitlements