How does the version history of a policy work?
Every time you modify an overtime policy, the system automatically generates a new version with its date and time, keeping previous versions saved.
Therefore, the version history is a complete chronological record where you can check what changed, when it happened, and who made each modification.
What changes generate a new version? The system creates a new version of the policy when you modify settings that affect the calculation of hours:
- How accumulated time is managed (pay, time off, or hybrid).
- The basis against which hours worked are compared (schedule/shift or contract).
- On which days overtime is generated or how it is distributed.
- Changes to the approval chain or flow.
- Adjustments to management periods, expiry rules, or annual limits.
Other adjustments, such as changing the name, description, or visibility and notification options, are saved in the history but do not generate a new version.
Versions are displayed from most recent to oldest. By clicking on any previous version, you can:
- View how the calculation, visibility, or notification parameters were configured on a specific date.
- Restore an old version using the "Create new version from this one" option to take that base configuration without altering the current version.
In addition to the list of versions, each individual action is signed with the user's name and the exact date to give you full traceability.
If you are going to modify a policy that has employees assigned, check which version is active and since when. Changes to the calculation may affect balances already generated.
