Considerations and limitations
- If an employee needs to cancel an entire time-off request, they must rely on existing (core) GTOR functionality.
- This extension supports:
- multiple assignments.
- the rerun functionality.
-
This extension respects the Employee Visibility Period. For example, assume that an employee initially requested leave from August 25 – August 30. Further assume that the Request Period within the Employee Visibility Period ends on September 1. If the employee attempts to extend leave from August 30 – September 5, the edit is prevented because the leave extends beyond the allowed visibility period; the system rejects the request and notifies the employee.
- The Edit Approved GTOR business process must be attached to employee process profile assignments.
- When the Request Cancellation option in the Request Subtype configuration is set to Disallow, the workflow permits only leave extensions. Cancellation of any part of the leave is not permitted.
- Employees can edit only approved time-off requests through this workflow.
- If a time off request needs to be approved at multiple levels, this workflow only supports 20 reviewers in a single step for symbolic reviewers.
- If an employee cancels or modifies a leave request, the corresponding days are excluded from the form in a subsequent run.
- When an employee extends leave, the workflow generates a new time-off request. This newly created request includes a comment indicating that it was generated by the workflow. During a subsequent processing cycle, it appears as a new entry in the user form.
- Do not remove the
- indicative paycode that the workflow adds to the employee timecard.
- schedule tag that the workflow adds to the employee schedule.