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

S.No.	Data	MDMS Link
1	Relationship	https://github.com/egovernments/works-mdms-data/blob/DEV/data/pg/common-masters/Relationship.json
2	GenderType	https://github.com/egovernments/works-mdms-data/blob/DEV/data/pg/common-masters/GenderType.json
3	SocialCategory	https://github.com/egovernments/works-mdms-data/blob/DEV/data/pg/common-masters/SocialCategory.json
4	WageSeekerSkills	https://github.com/egovernments/works-mdms-data/blob/DEV/data/pg/common-masters/WageSeekerSkills.json
5	TenantBoundary	https://github.com/egovernments/works-mdms-data/blob/8285bc63aac7f056326165897ac18918520c9723/data/pg/citya/egov-location/boundary-data.json

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.	API	Action ID	Roles
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

Sidebar Configuration

S.No.	Screen	Navigation URL	Left Icon Updates	Roles
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.	Screen	Configuration
1	Create/Modify	Modify Individual Config
2	Search	Search Individual Config

Localization Configuration & Modules

TenantID	Module
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.