Case: Create

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

Case: Edit

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

https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/pages/EditEmployee/index.js

MDMS API

 moduleDetails: [
    {
      moduleName: "common-masters",
      masterDetails: [
        { name: "Department", filter: "[?(@.active == true)]" },
        { name: "Designation", filter: "[?(@.active == true)]" },
      ],
    },
    {
      moduleName: "tenant",
      masterDetails: [{ name: "tenants" }],
    },
    {
      moduleName: "ACCESSCONTROL-ROLES",
      masterDetails: [{ name: "roles", filter: "$.[?(@.code!='CITIZEN')]" }],
    },
    { moduleName: "egov-location", masterDetails: [{ name: "TenantBoundary" }] },
  ]

Introduction

The HRMS provides a digital interface for ULB/State admin to create, edit & deactivate employees.

Functional Scope

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

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.

Primary Files: https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/pages/Inbox.js

Secondary Files: https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/components/inbox/DesktopInbox.js

https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/components/inbox/search.js

https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/components/inbox/ApplicationCard.js

https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/components/inbox/ApplicationTable.js

https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/components/inbox/ApplicationLinks.js

Logged-in users can activate or deactivate employees as required.

Deactivate Employee

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

Activation Employee

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

https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/components/Modal/EmployeeActivation.js

https://github.com/egovernments/digit-ui-internals/blob/development/packages/modules/hrms/src/components/Modal/EmployeeAppliaction.js

MDMS Hook

const { isLoading, isError, errors, data, ...rest } = Digit.Hooks.hrms.useHrmsMDMS(tenantId, "egov-hrms", "DeactivationReason");

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

Admin can see the total count of employees in the following format -

• Active Employee Count

• Total Employee Count

API -EndPoint- /egov-hrms/employees/_count

Role Action Mapping

Objective

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

Technical Implementation Details

1. get all applications in payload.ProcessInstances using egov-workflow-v2/egov-wf/process/_search

2. get the escalated applications in escalatedPayload.ProcessInstances using egov-workflow-v2/egov-wf/escalate/_search

3. pushing escalated applications into all applications with isEscalatedApplication flag with true value, for finding the escalated application in all applications.

4. This works the same as Employee Inbox.

Escalated Tab

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:

if (get(item, "isEscalatedApplication", false)) {
      escalatedToMe.push([...dataRows])
  }

The isEscalatedApplication is the flag added initially for separating the escalated applications to show in the escalated tab.

On-Click History

The functionality works as it is but the only change is showing the symbol to identify the state from which it has escalated.

Role Action Mapping