Wage Seeker

Wage seeker configuration details

Overview

This module helps in creating an individual (Wage Seeker), it is needed in Mukta to assign work, track attendance and process DBTs.

This module has 3 associated screens :

  1. Search

  2. View

  3. Modify

MDMS Configurations

Module Enablement Configuration

  1. Set module code as “Masters” in Module.js for the Masters (Organization) Module. Refer CityModule.json

 {
            "module": "Masters",
            "code": "Masters",
            "active": true,
            "order": 6,
            "tenants": [
                {
                    "code": "pg.cityb"
                },
                {
                    "code": "pg.cityc"
                },
                {
                    "code": "pg.citya"
                }
            ]
     }
  1. Enable Module in App.js. Update the object ‘enabledModules’. Use the code “Masters”. This code should match the code of the cityModule.json, mentioned above.

Role-action Mapping

S.No.APIAction IDRoles

1

/individual/v1/_search

71

MUKTA_ADMIN, ORG_ADMIN

2

/individual/v1/_update

72

MUKTA_ADMIN, ORG_ADMIN

3

/individual/v1/_delete

74

MUKTA_ADMIN, ORG_ADMIN

S.No.ScreenNavigation URLLeft Icon UpdatesRoles

1

Search Individual

/works-ui/employee/masters/search-wageseeker

dynamic:WageseekerIcon

MUKTA_ADMIN

Sample object for a sidebar action defined in MDMS (containing the navigation Url)

{
      "id": 78,
      "name": "WAGESEEKER",
      "url": "url",
      "displayName": "Masters Search Wageseeker",
      "orderNumber": 10,
      "parentModule": "",
      "enabled": true,
      "serviceCode": "WageSeeker",
      "code": "null",
      "navigationURL": "/works-ui/employee/masters/search-wageseeker",
      "path": "8WageSeeker.Search",
      "leftIcon": "dynamic:WageseekerIcon"
    }

Screen Configuration

S.No.ScreenConfiguration

1

Create/Modify

2

Search

Localization Configuration & Modules

TenantIDModule

pg

rainmaker-masters

pg

rainmaker-common-masters

pg

rainmaker-common

pg.citya

rainmaker-pg.citya

Workflow Configuration

NA

Customization

  1. Modify Individual Screen

    • Use the common Utility “PreProcessMDMSConfig”.

    • Pass the associated dependencies for the config.

    • The utility will return a config which will run through FormComposer.

    • Refer to docs for Pre-Process configuration of Component comments.

  2. Search Individual Screen

    • Use the common utility “preProcessMDMSConfigInboxSearch”.

    • Pass the associated dependencies for the config.

    • The utility will return a config which will run through RenderFormFields.

    • Refer to docs for Pre-Process configuration of Component comments.

    • All the Inbox and Search screens throughout the app are rendered using the component Inbox/Search Composer

  3. Validations added

    • Form validations are integrated within the Screen Configurations. To facilitate this, include the appropriate populators for the respective validations. Additionally, make sure to specify the JSON path necessary for the pre-processing to function correctly.

  4. Delete API Usage

    • To modify existing skills, the "deleteIndividual" and "update Individual" APIs are utilized.

    • If skills are already present, they can be updated using the "update" API. If any skills need to be removed, the "delete" API is used. In the case of skill removal, the entire skill object should be sent with the 'isDeleted' flag set to true.

Last updated

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