This article explains how termination dates are determined and automatically set by the system when a user is decommissioned.
Termination Date Logic
When a user is decommissioned, the system evaluates multiple types of activity entries to determine the appropriate termination date. This date reflects the most recent interaction by the user and ensures alignment with system records.
The system checks the following:
- Latest time entry date
- Latest expense entry date
- Latest charge entry date
- Latest product entry date
- Latest committed date (resource booking date)
Date Selection Logic
If all the above dates are prior to today's date, the system sets the termination date to the current date.
If any of the above dates are on or after today's date, the system sets the termination date to the latest date among them.
Example Scenarios
The table below illustrates how the termination date is determined based on time entry data:
Note: In the following examples, the current date is assumed to be 2025-10-10.
| User Name | Task | Latest Entry Date | Expected Termination Date | Explanation |
|---|---|---|---|---|
| UserA | Project Planning Review | 2025-11-18 | 2025-11-18 | Latest time entry date is after the current date |
| UserB | Client Budget Approval | 2025-10-10 | 2025-10-10 | Latest time entry date equals the current date |
| UserC | System Integration Testing | 2025-09-09 | 2025-10-10 | Latest time entry date is before the current date |
Additional Information
Any processed holiday entry is considered a valid time entry and is included in the termination date calculation.
The system only sets the termination date automatically based on the most recent relevant entry.