Exit Application – Feature Requirements
Bhavik Dattani
Exit Application – Feature Requirements
We require the following features in the Exit Application module:
- Attachment Upload – Ability to attach documents to the application, either individually or via bulk upload.
- Resignation Date Modification – Option to change the resignation application date, automatically updating the last working date. This should be configurable, allowing only admins to make changes.
- Approval Configuration for RM-Initiated Exit – A configurable option to determine whether an RM-initiated exit application requires approval.
- Approval Configuration for Admin-Initiated Exit – A configurable option to determine whether an admin-initiated exit application requires approval.
- Exit Type & Workflow Configuration –
- Support for voluntary and involuntary exit types.
- Configurable workflows based on the exit type.
- In case of termination, allow triggering of a different workflow.
- Workflow should support back-and-forth movement, and all values should be stored properly in the backend.
- Workflow Retention & Visibility –
- Option to retain the workflow at each level.
- Admins and RM users should be able to track whether the process is in the re-initiation stage.
- Configurable visibility to hide this process from employees if needed.
- Email Configuration – Customizable email settings for each exit type.
- My Team Exit Page can be Given access based on Requirements
- Reason Type should be based on Master Table and System store id and value in backend.
- Guidelines & Documentation –
- Proper guidelines, documentation, examples, and flowcharts should be available.
- The system should be fully configurable without developer dependency.