Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
URL- digit-ui/employee/hrms/create
Logged Users can Create Employees by providing the necessary Details
If a user enters a mobile number that already exists in the system - Then the application will give an error message.
The Boundary is auto-filled with current TenantId
. The user is able to add Multiple Jurisdictions and Assignments.
Primary Files: https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/pages/createEmployee.js
URL- digit-ui/employee/hrms/edit/{Employee Id}
Logged Users can Edit Employee Details. Employee Id is disabled.
Primary Files: https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/pages/EditEmployee/EditForm.js
Sl.No. | API | Role | Access ID |
---|---|---|---|
API | Role | Access ID |
---|---|---|
1
/egov-hrms/employees/_create
HRMS_ADMIN
1750
2
/egov-hrms/employees/_search
HRMS_ADMIN
1752
/egov-hrms/employees/_update
HRMS_ADMIN
1751
Logged-in users can activate or deactivate employees as required.
If the employee Status is Active - Users can deactivate the employee by clicking on the Take Action button available in the Employee Detail screen.
On the click of Deactivate Employee button, a PopUp appears where users should provide necessary details such as
Mandatory
Reason for Deactivation
Effective Date
Optional
Order No.
Supported Documents (File Upload)
Remarks
On deactivation, users will be re-directed to the Acknowledgement screen
If an employee status is inactive, users can reactivate employees by clicking on the Take Action button placed on the Employee Detail screen.
On the click of Deactivate Employee button, a popup appears where users should provide necessary details such as
Mandatory
Reason for Reactivation
Effective Date
Optional
Order No.
Supported Documents (File Upload)
Remarks
On reactivation, users are routed to the Acknowledgement screen
Primary Files: https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/components/EmployeeAction.js
Secondary Files: https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/components/Modal/index.js
API | Details |
---|---|
/egov-hrms/employees/_update
1 let documents = { 2 referenceType: "ACTIVATION", 3 documentId: uploadedFile, 4 documentName: file.name, 5 }; 6 applicationData.Employees[0]["documents"].push(documents); 7 } 8 9 Employees[0]["reactivationDetails"].push(data); 10 Employees[0].isActive = true;
/egov-hrms/employees/_update
1 let documents = { 2 referenceType: "DEACTIVATION", 3 documentId: uploadedFile, 4 documentName: file.name, 5 }; 6 applicationData.Employees[0]["documents"].push(documents); 7 } 8 Employees[0]["deactivationDetails"].push(data); 9 Employees[0].isActive = false; 10 history.push("/digit-ui/employee/hrms/response", { Employees, key: "UPDATE", action: "DEACTIVATION" });
URL- digit-ui/employee/hrms/details/{Employee Id}
Logged in users should able to see details of employees
Employment Status
Personal Details
Employee Details
Jurisdiction Details
Assignment Details
Supported Documents
If the user has uploaded any documents against Employment Status. Those documents are downloadable in one click.
API details
Primary Files: https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/pages/EmployeeDetails.js
URL - digit-ui/employee/hrms/inbox
Admin can search employees based on multiple filters and Search parameters
Filter By
ULB
Department
Status
Search
Name
Employee ID
Mobile Number
The search screen has a pagination feature.
On Hover of Roles Count
Logged Users can see the detailed assigned roles
On clicking upon Employee Id logged-in users are routed to the Employee Detail screen.
API | Role | Access ID |
---|---|---|
File link -
API URL | Roles | Action ID |
---|
API | Parameters | Role | Access ID |
---|
Primary Files:
Secondary Files:
/egov-hrms/employees/_search
HRMS_ADMIN
1752
| HRMS_ADMIN |
|
|
| HRMS_ADMIN |
|
Refer to the employee inbox technical documentation below before reading the auto-escalation flow details.
The auto-escalation option provides employees with the option to view all escalated applications that have not been acted on.
Route - https://egov-micro-uat.egovernments.org/employee/inbox
Note
The tab ASSIGNED TO ME is inter-changed to ALL vice versa and the Escalated tab is added in the 3rd position.
Nearing Escalation and Escalated: The localisation message of Escalated is changed to SLA Breached.
get all applications in payload.ProcessInstances
using egov-workflow-v2/egov-wf/process/_search
get the escalated applications in escalatedPayload.ProcessInstances
using egov-workflow-v2/egov-wf/escalate/_search
pushing escalated applications into all applications with isEscalatedApplication
flag with true value, for finding the escalated application in all applications.
This works the same as Employee Inbox.
The Escalated tab shows all Escalated applications.
The process instance response fetches all records from which the records are filtered based on the following condition:
The isEscalatedApplication
is the flag added initially for separating the escalated applications to show in the escalated tab.
The functionality works as it is but the only change is showing the symbol to identify the state from which it has escalated.
Note: Inbox functionality works the same as before as outlined in the Employee Inbox document attached here.
Escalated API file path: frontend/actions.js at master · egovernments/frontend. The escalated API is called based on given conditions.
Functionality file path: frontend/index.js at master · egovernments/frontend
API | Roles | Action ID |
---|---|---|
/egov-workflow-v2/egov-wf/escalate/_search
EMPLOYEE
2150