1 of 16

Workbench UI

Figma screens for the UI are available here. Refer to them to understand the Workbench UI.

Configurations

MDMS Configurations

DevOps Configuration

Overview

This page provides details about the Workbench UI configuration required to enable it in any environment.

DevOps Configuration

In the DevOps repository of your organization, locate the following "deploy-as-code/helm/environments/unified-dev.yaml". Inside the environment YAML file used to deploy the Core platform, please add the following block of code:


workbench-ui:
  custom-js-injection: |
    sub_filter.conf: "
      sub_filter  '<head>' '<head>
      <script src={{INSERT_YOUR_AWS_BUCKET_NAME}}/globalConfigs.js type=text/javascript></script>';"

A dev environment sample file is linked here. Note that you will have to modify this for your deployment.

Global Configuration

This section contains a config that applies globally to all UI modules. These need to be configured before configuring the service-specific UI.

Steps to create a globalconfig.js file:

Create a config file (globalconfigs.js) with the below-mentioned configurations (refer code below).
Configure all the images/logos required in the S3 and add links as footerBWLogoURL, footerLogoURL.
Mention the state tenant ID as stateTenantId.
If any user roles have to be made invalid add as invalidEmployeeRoles.
Then push this global config file into your S3 bucket as globalconfigs.js.
Mention the globalConfigs file URL in your Environment config .

var globalConfigs = (function () {
  var stateTenantId = 'pg' // statetenantId
   var gmaps_api_key = '<<INSERT_GMAP_GENERATED_TOKEN>>';
   var contextPath = 'workbench-ui'; 
   var configModuleName = 'commonMuktaUiConfig'; 
   var centralInstanceEnabled = false;
   var footerBWLogoURL = '{{INSERT_YOUR_AWS_BUCKET_NAME}}/digit-footer-bw.png';
   var footerLogoURL = '{{INSERT_YOUR_AWS_BUCKET_NAME}}/digit-footer.png';
   var digitHomeURL = 'https://www.digit.org/';
   var xstateWebchatServices = 'wss://dev.digit.org/xstate-webchat/';
   var assetS3Bucket = '{{INSERT_YOUR_AWS_BUCKET_NAME}}';
   var invalidEmployeeRoles = ["CBO_ADMIN","STADMIN","ORG_ADMIN","ORG_STAFF","SYSTEM"] 

 
   var getConfig = function (key) {
     if (key === 'STATE_LEVEL_TENANT_ID') {
       return stateTenantId;
     }
     else if (key === 'GMAPS_API_KEY') {
       return gmaps_api_key;
     }
     else if (key === 'ENABLE_SINGLEINSTANCE') {
       return centralInstanceEnabled;
     } else if (key === 'DIGIT_FOOTER_BW') {
       return footerBWLogoURL;
     } else if (key === 'DIGIT_FOOTER') {
       return footerLogoURL;
     } else if (key === 'DIGIT_HOME_URL') {
       return digitHomeURL;
     } else if (key === 'xstate-webchat-services') {
       return xstateWebchatServices;
     } else if (key === 'S3BUCKET') {
       return assetS3Bucket;
     } else if (key === 'CONTEXT_PATH'){
	return contextPath;
     } else if (key === 'UICONFIG_MODULENAME'){
	return configModuleName;
     } else if (key === 'INVALIDROLES'){
	return invalidEmployeeRoles;
     }
   };
 
 
   return {
     getConfig
   };
 }());

Localisation Configuration

All strings localised per module are provided in this sheet linked here. To translate the UI into other languages, please follow this sheet and provide appropriate translations in your language.

Reference Links

Figma screens for the UI are here. Refer to them to understand the Workbench UI.

FAQ :: On Localisation Screens

How to Add a New Language

To add a new localisation entry, follow these steps:

Go to the Localisation Add Screen:
- Navigate to the screen designated for adding localisation entries.
Input Language and Module Name:
- In the appropriate fields, enter the desired language and module name.
Enter Keycode and Message:
- Provide the keycode and message value in their respective fields. For example:
  - Keycode: TEST
  - Message: TEST

See the Image Below:

Save the Data:

Once you have entered the keycode and message, click on the "Save" button to save the data.

Verify the Entry:

Navigate to the Localization Search screen to verify the entry you just added. You should see the keycode TEST with the message TEST.
See the Image given below:

By following these steps, you can successfully add and verify new localization entries in the system.

How to Add a New Module

Adding a New Module

To add a new module, follow these steps:

Navigate to Manage Master Data:
- Go to the "Manage Master Data" section of the application.
Provide Module and Master Name:
- Enter the module name and master name. For example, you might use:
  - Module Name: Common Masters
  - Master Name: State Info
View the Master Data:
- View the master data as shown in the image provided below.

Add Localization Modules:
- Choose "Add Localization Modules" from the options.
- Enter the label and value for the localization. For example:
Update the Master Data:
- Click on "Update" to save the changes.

By following these steps, you can successfully add a new module and update its localization details.

Manage Master Data

Overview

The Manage Master Data screen allows users to manage master data. Navigate to the Manage Master Data from the home screen card.

Manage Master Data - User Role

MDMS_ADMIN

For the provided role, it is necessary to include all role action mappings associated with master data in MDMS.

Search Master Data

How to search master data

Overview

Search Master Data Flow

Users can click on the specific master name from the dropdown on the Manage Master Data screen to select the master data.
Users are redirected to the Search Master Data screen (of the selected master) screen as soon as a master is selected.
By default, the data present in that master is shown in the Results table.
Users can search master data using the following input parameters -
1. Field
2. Value
3. is Active

Note -> Search with field and value is considered as one parameter. Make sure to enter both in order to search master data.

'isActive' is a Boolean parameter which results in either active or inactive master data. All master data contain this field by default.
For the time being, master data search is allowed with string fields and the isActive flag.
Search results are filtered by string type and isActive before getting rendered in the table.

Search Schemas API

The master and module dropdowns on the manage master screen are populated on the basis of the responses from the schema search. Refer to the below curl for details:

Use the below parameters to search for the schemas -

tenantId
limit
offset
codes -> list of schema codes

curl --location 'http://localhost:8094/mdms-v2/schema/v1/_search' \
--header 'Content-Type: application/json' \
--data '{
    "RequestInfo": {
        "apiId": "asset-services",
        "ver": null,
        "ts": null,
        "action": null,
        "did": null,
        "key": null,
        "msgId": "search with from and to values",
        "authToken": "dfcca143-b5a6-4726-b5cd-c2c949cb0f2b",
        "correlationId": null,
        "userInfo": {
            "id": "1",
            "userName": null,
            "name": null,
            "type": null,
            "mobileNumber": null,
            "emailId": null,
            "roles": null
        }
    },
    "SchemaDefCriteria": {
        "tenantId": "pb",
        "codes": [
            "Trade.Fields"
        ],
        "limit":50
    }
}'

Search Master Data For Specific Schema API

Users are redirected to the search master data screen once a specific master is selected from the manage master data screen.

Refer to the below API curl to search for the master data -

curl --location 'http://localhost:8094/mdms-v2/v2/_create/common-masters.Sample' \
--header 'Content-Type: application/json' \
--data '{
  "RequestInfo": {
    "apiId": "asset-services",
    "ver": null,
    "ts": null,
    "action": null,
    "did": null,
    "key": null,
    "msgId": "search with from and to values",
    "authToken": "dfcca143-b5a6-4726-b5cd-c2c949cb0f2b",
    "correlationId": null,
    "userInfo": {
      "id": "1",
      "userName": null,
      "name": null,
      "type": null,
      "mobileNumber": null,
      "emailId": null,
      "roles": null
    }
  },
  "Mdms": {
    "tenantId": "pg",
    "schemaCode": "common-masters.Sample",
    "uniqueIdentifier": "aa4d8d08-658b-45c1-af4d-d57428fa5e52",
    "data": {
                "id": "sdfljksd",
                "code": "testtcode",
                "name": "nameeee",
                "description": "descccc"
            },
    "isActive": true
  }
}'

The parameters here are used to search for the master data. Refer to the request body object below.

 {
    "tenantId": "pg",
    "schemaCode": "common-masters.Sample",
    "uniqueIdentifier": "aa4d8d08-658b-45c1-af4d-d57428fa5e52",
    "data": {
                "id": "sdfljksd",
                "code": "testtcode",
                "name": "nameeee",
                "description": "descccc"
            },
    "isActive": true
  }

The "data" object holds the field-value pairs used to search for master data within a specific master. The "uniqueIdentifier" is a backend-generated ID for each master data.

Add Master Data

Flow for adding master data from UI

Overview

Add Master Data Flow

An action button is available on the search master data screen to add master data.
Clicking on the action button redirects users to the add master data screen.
The Add Master Data screen renders a form through which the user can enter master data.
Once the form is submitted, the validations are run as specified in the schema. If the validations are passed, the Create API is called and the respective toast message is shown as relevant to the response received from the Create API.

Role Action Mapping To Access Create API

As of now, role actions have to be defined for every schema. Let us take an example of a schema code "Trade.Details"
The Create API URL for the above schema will look like this "/mdms-v2/v2/_create/Trade.Details"
Hence for this URL, the role action mapping has to be added to the MDMS_ADMIN role.
Similarly, for other masters, add role action mapping to the same role "MDMS_ADMIN".

Create Master Data API

Refer to the curl below:

curl 'http://localhost:3000/mdms-v2/v2/_create/Trade.Validations' \
  -H 'Accept: application/json, text/plain, */*' \
  -H 'Accept-Language: en-US,en;q=0.9' \
  -H 'Connection: keep-alive' \
  -H 'Content-Type: application/json;charset=UTF-8' \
  -H 'Origin: http://localhost:3000' \
  -H 'Referer: http://localhost:3000/workbench-ui/employee/workbench/mdms-add-v2?moduleName=Trade&masterName=Validations' \
  -H 'Sec-Fetch-Dest: empty' \
  -H 'Sec-Fetch-Mode: cors' \
  -H 'Sec-Fetch-Site: same-origin' \
  -H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36' \
  -H 'sec-ch-ua: "Chromium";v="116", "Not)A;Brand";v="24", "Google Chrome";v="116"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "Windows"' \
  --data-raw '{"Mdms":{"tenantId":"pb","schemaCode":"Trade.Validations","uniqueIdentifier":null,"data":{"name":"sfd","dropdownField":"90-100"},"isActive":true},"RequestInfo":{"apiId":"Rainmaker","authToken":"5bbfa93c-adc2-42b2-992e-a708a83cb2cf","userInfo":{"id":80234,"uuid":"aeb85b37-c996-4218-bdca-1b00cc268f2f","userName":"WBQA","name":"LOC","mobileNumber":"9999991942","emailId":null,"locale":null,"type":"EMPLOYEE","roles":[{"name":"MDMS ADMIN","code":"MDMS_ADMIN","tenantId":"pb"},{"name":"Super User","code":"SUPERUSER","tenantId":"pb"},{"name":"Localisation admin","code":"LOC_ADMIN","tenantId":"pb"},{"name":"Employee","code":"EMPLOYEE","tenantId":"pb"}],"active":true,"tenantId":"pb","permanentCity":null},"msgId":"1694161641687|en_IN","plainAccessRequest":{}}}' \
  --compressed

Sample request body:

{
    "Mdms": {
        "tenantId": "pb",
        "schemaCode": "Trade.Validations",
        "uniqueIdentifier": null,
        "data": {
            "name": "sfd",
            "dropdownField": "90-100"
        },
        "isActive": true
    },
    "RequestInfo": {
        "apiId": "Rainmaker",
        "authToken": "5bbfa93c-adc2-42b2-992e-a708a83cb2cf",
        "userInfo": {
            "id": 80234,
            "uuid": "aeb85b37-c996-4218-bdca-1b00cc268f2f",
            "userName": "WBQA",
            "name": "LOC",
            "mobileNumber": "9999991942",
            "emailId": null,
            "locale": null,
            "type": "EMPLOYEE",
            "roles": [
                {
                    "name": "MDMS ADMIN",
                    "code": "MDMS_ADMIN",
                    "tenantId": "pb"
                },
                {
                    "name": "Super User",
                    "code": "SUPERUSER",
                    "tenantId": "pb"
                },
                {
                    "name": "Localisation admin",
                    "code": "LOC_ADMIN",
                    "tenantId": "pb"
                },
                {
                    "name": "Employee",
                    "code": "EMPLOYEE",
                    "tenantId": "pb"
                }
            ],
            "active": true,
            "tenantId": "pb",
            "permanentCity": null
        },
        "msgId": "1694161641687|en_IN",
        "plainAccessRequest": {}
    }
}

View Master Data

Flow for viewing master data

Overview

From the search master data screen users can click on any of the rows in the results table, this will redirect the UI to the View master data screen.

Rendering View Master Data Screen Logic

Before loading the View screen, we fetch the schema and the data using the schema code and unique Identifier respectively. Curls for search schema and search data can be referred from the Add Master Data page.
Schema response is used to render the form, similar to add form, and the data response is used to prefill the values in the form. The only difference here is that all the fields are disabled, unlike the add screen.
The same role action mapping rules apply here as defined in the Add Master Data page.
In the View screen, we have an action button with two options
1. Edit Master Data
2. Disable Master Data
The above actions are covered in the Update Master Data page.

Update Master Data

Flow for updating master data from UI

The users have two options on the View Master Data screen -

Disable/Enable Master Data
Edit Master Data

Disable/Enable Master Data

This option is dynamic, if the master data is currently disabled(computed through the "isActive" flag present in every master data) Enable option is shown and vice-versa.
Update Master data API is called with the updated value of "isActive" flag and a respective toast message is shown to the user
As soon as the API responds, this option is updated according to the new value of "isActive" flag.
Pls refer to the end of this page for updated API details

Edit Master Data

When the user clicks on this option, the screen redirects to the Edit master data screen.
This screen is similar to the add master data screen, but all the fields are pre-populated with previous data.
Users can make changes to the master data.
Once the user clicks on the Submit button, validations are run in UI (specified in schema). If the validations are passed update master data API is called and a toast message is shown. After 5 seconds the user is automatically redirected to the view screen, where the updated data is reflected.
If the validations fail, the respective error message is shown below the target field for which validations failed.
The same role action mapping rules apply here as mentioned in the Add Master data page.

Update Master Data API

Refer to the curl below to update the master data API. It is very similar to the Create Master Data. (Notice the URL is unique to the schema for which the master data belongs, similar to add).

curl 'http://localhost:3000/mdms-v2/v2/_update/Trade.Validations' \
  -H 'Accept: application/json, text/plain, */*' \
  -H 'Accept-Language: en-US,en;q=0.9' \
  -H 'Connection: keep-alive' \
  -H 'Content-Type: application/json;charset=UTF-8' \
  -H 'Origin: http://localhost:3000' \
  -H 'Referer: http://localhost:3000/workbench-ui/employee/workbench/mdms-edit?moduleName=Trade&masterName=Validations&uniqueIdentifier=sfd' \
  -H 'Sec-Fetch-Dest: empty' \
  -H 'Sec-Fetch-Mode: cors' \
  -H 'Sec-Fetch-Site: same-origin' \
  -H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36' \
  -H 'sec-ch-ua: "Chromium";v="116", "Not)A;Brand";v="24", "Google Chrome";v="116"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "Windows"' \
  --data-raw '{"Mdms":{"id":"661b4560-a0ec-4930-a8c2-c84d643b361f","tenantId":"pb","schemaCode":"Trade.Validations","uniqueIdentifier":"sfd","data":{"name":"sfd","dropdownField":"70-90"},"isActive":true,"auditDetails":{"createdBy":"aeb85b37-c996-4218-bdca-1b00cc268f2f","lastModifiedBy":"aeb85b37-c996-4218-bdca-1b00cc268f2f","createdTime":1694161642579,"lastModifiedTime":1694161642579}},"RequestInfo":{"apiId":"Rainmaker","authToken":"5bbfa93c-adc2-42b2-992e-a708a83cb2cf","userInfo":{"id":80234,"uuid":"aeb85b37-c996-4218-bdca-1b00cc268f2f","userName":"WBQA","name":"LOC","mobileNumber":"9999991942","emailId":null,"locale":null,"type":"EMPLOYEE","roles":[{"name":"MDMS ADMIN","code":"MDMS_ADMIN","tenantId":"pb"},{"name":"Super User","code":"SUPERUSER","tenantId":"pb"},{"name":"Localisation admin","code":"LOC_ADMIN","tenantId":"pb"},{"name":"Employee","code":"EMPLOYEE","tenantId":"pb"}],"active":true,"tenantId":"pb","permanentCity":null},"msgId":"1694163335209|en_IN","plainAccessRequest":{}}}' \
  --compressed

Sample request body for update:

{
    "Mdms": {
        "id": "661b4560-a0ec-4930-a8c2-c84d643b361f",
        "tenantId": "pb",
        "schemaCode": "Trade.Validations",
        "uniqueIdentifier": "sfd",
        "data": {
            "name": "sfd",
            "dropdownField": "70-90"
        },
        "isActive": true,
        "auditDetails": {
            "createdBy": "aeb85b37-c996-4218-bdca-1b00cc268f2f",
            "lastModifiedBy": "aeb85b37-c996-4218-bdca-1b00cc268f2f",
            "createdTime": 1694161642579,
            "lastModifiedTime": 1694161642579
        }
    },
    "RequestInfo": {
        "apiId": "Rainmaker",
        "authToken": "5bbfa93c-adc2-42b2-992e-a708a83cb2cf",
        "userInfo": {
            "id": 80234,
            "uuid": "aeb85b37-c996-4218-bdca-1b00cc268f2f",
            "userName": "WBQA",
            "name": "LOC",
            "mobileNumber": "9999991942",
            "emailId": null,
            "locale": null,
            "type": "EMPLOYEE",
            "roles": [
                {
                    "name": "MDMS ADMIN",
                    "code": "MDMS_ADMIN",
                    "tenantId": "pb"
                },
                {
                    "name": "Super User",
                    "code": "SUPERUSER",
                    "tenantId": "pb"
                },
                {
                    "name": "Localisation admin",
                    "code": "LOC_ADMIN",
                    "tenantId": "pb"
                },
                {
                    "name": "Employee",
                    "code": "EMPLOYEE",
                    "tenantId": "pb"
                }
            ],
            "active": true,
            "tenantId": "pb",
            "permanentCity": null
        },
        "msgId": "1694163335209|en_IN",
        "plainAccessRequest": {}
    }
}

Manage Localisation Data

We have the following flows in Manage Localization Data

Search Localizations
Edit Localizations
Add and Bulk upload

Role required to manage localizations

"LOC_ADMIN"

Sample JSON:

{
   "name": "Localisation admin",
   "code": "LOC_ADMIN",
   "tenantId": "pb"
}

Search Localisation Data

Overview

This page provides the steps to search localisation data.

Steps

Navigate to the Manage Localisation screen from the home screen card. This opens the search localisation screen.

The following parameters are available for searching localizations

locale -> this field is mandatory. This dropdown is populated based on this mdms https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-UAT/data/pg/common-masters/StateInfo.json
module -> list of modules present in this mdms https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-DEV/data/pg/common-masters/StateInfo.json
keycode -> code of a specific message. It is a string-type parameter

Search Results

We have the following columns for localisation search results:

Module name
Key code
Default value -> message stored in default locale
Text -> message stored
Action -> Edit action to update message in that particular localisation

A note on the default value in the results

While adding localisations, by default all the messages will be updated in the locale mentioned by the user as well as in the "default" locale. The message updated in this locale is considered the default message. While updating the message default locale message remains unchanged.

Search API For Localisations

Localisation search API is an open API. Refer to the curl given below:

curl --location 'https://qa.digit.org/localization/messages/v1/_search?locale=en_IN&tenantId=pb' \
--header 'Content-Type: application/json' \
--data '{
     "RequestInfo": {
       "apiId" : "emp",
       "ver" : "1.0",
       "ts" : "10-03-2017 00:00:00",
       "action" : "create",
       "did" : "1",
       "key" : "abcdkey",
       "msgId" : "20170310130900",
       "requesterId" : "rajesh",
       "authToken" : "{{authToken}}",
       "userInfo" : {
         "id" : 1
       }
   }
}'

Search for the desired language and module using the provided search functionality. The language and module are derived from MDMSv2.
For example, if you are searching for the language ‘English’ and the module ‘rainmaker-common’, Once you perform the search, all relevant results will be displayed below.

Refer to the screenshot below:

Adding a new Localisation Message

To add a new language, provide a locale name and a keycode, then click ‘Add’ to include it in the system.

Add Localisation Data

Add localization flow

Adding Localizations

From the search screen user can navigate to add localization screen by clicking the action button
In this screen user can specify the locale(language) and module in which messages have to be upserted
Once the language and module is selected a table is rendered in which user can add the keycode and the respective message. In one go, we can upsert upto 50 messages in this table.
These messages will be upserted into the default locale as well.
After adding the messages user can click on the "Save" action button. Upon success, a relevant toast message is shown and the table is cleared.
In case of failure, an error toast message is shown listing the list of errors due to which the messages could not be upserted.

API for adding localizations

Same API is utilized for edit and bulk upload as well.

Refer the below curl:

Tenant Module Localization

State level users can upsert localizations to all modules
City level users can only upsert to module specific to the tenantId (eg -> pg.citya)
Some examples of city module localizations

Edit Localization Messages

Editing localizations

From the Search screen itself user can update localization messages
Only message text can be edited, we are not allowed to change locale, module and code of the message.
There is a fixed action column in the results table.
Upon clicking the edit icon a modal is opened from where user can add the updated message
User can click on the submit button, a respective toast is shown and the search results are refetched and rendered with the updated message.
API used here is same as add localization.

Select the edit icon in the action column, update the text as needed, and then click submit to save your changes.

FAQ :: Add localisation if screens are not localised.

Bulk Upload

If you are visiting the screen and it is not localized, the screen will appear as in the screenshot below.

You can localize it with these simple steps:
We have an option to upload Excel sheets (XLSX, XLS) and upsert bulk messages.
From the "Add Localization" screen, there is an option to Bulk upload. See the image below.

Upon clicking the bulk upload option, the user can select an Excel file from the file system.
Copy all the locale code and give the corresponding message to display, module, and locale.
Paste this data into an Excel spreadsheet and save it as an XLSX file.
See the screenshot provided for reference for excel file.

Conditions for valid excel file

Excel file can contain multiple sheets, every sheet must have these four columns:

code
message
locale
module

Upload this XLSX file to the project UI.
After uploading, log out and log back in to see the UI localized.

Now see the UI, it will be as given below:

Create New Master

Steps to follow to create a new Master -

Create a schema using Postman (API) - Schema( JSON draft-07 ) can be constructed by inputting the required JSON Object here Below is the sample cURL to create a schema.

curl --location --request POST 'https://qa.digit.org/mdms-v2/schema/v1/_create' \
--header 'Content-Type: application/json' \
--data-raw '{
    "RequestInfo": {
        "apiId": "asset-services",
        "ver": null,
        "ts": null,
        "action": null,
        "did": null,
        "key": null,
        "msgId": "search with from and to values",
        "authToken": "b2250d2c-3c25-40c9-960d-c4dda7443d44",
        "correlationId": null,
        "userInfo": {
            "id": "1",
            "userName": null,
            "name": null,
            "type": null,
            "mobileNumber": null,
            "emailId": null,
            "roles": null
        }
    },
    "SchemaDefinition": {
        "id": "b55f449c-61bb-4c56-b8cd-99cbdb00ee7f",
        "tenantId": "pb",  // update the state tenant id as per environment
        "code": "ACCESSCONTROL-ROLEACTIONS.roleactions",
        "description": "roleactions",
        "definition": {
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "isActive": true,
            "properties": {
                "rolecode": {
                    "type": "string"
                },
                "actionid": {
                    "type": "string"
                },
                "actioncode": {
                    "type": "string"
                },
                "tenantId": {
                    "type": "string"
                }
            },
            "required": [
                "rolecode",
                "actionid"
            ],
            "x-unique": [
                "rolecode",
                "actionid"
            ],
            "x-ref-schema": [
                {
                    "fieldPath": "rolecode",
                    "schemaCode": "ACCESSCONTROL-ROLES.roles"
                },
                {
                    "fieldPath": "actionid",
                    "schemaCode": "ACCESSCONTROL-ACTIONS-TEST.actions-test"
                }
            ]
        },
        "isActive": true,
        "auditDetails": {
            "createdBy": "902fcdad-8742-4e13-b9f0-12605a6180bb",
            "lastModifiedBy": "902fcdad-8742-4e13-b9f0-12605a6180bb",
            "createdTime": 1693284323630,
            "lastModifiedTime": 1693284323630
        }
    }
}'

Add actions-test and roleactions for search, create, and update. Below is the sample code for the actions-test for the schema mentioned above::

{
      "id": 2486,
      "name": "MDMS",
      "url": "url",
      "displayName": "Roleactions",
      "orderNumber": 1,
      "parentModule": "",
      "enabled": true,
      "serviceCode": "MDMS",
      "code": "null",
      "navigationURL": "/workbench-ui/employee/workbench/mdms-search-v2?moduleName=ACCESSCONTROL-ROLEACTIONS&masterName=roleactions",
      "path": "9MDMS.ACCESSCONTROL-ROLEACTIONSroleactions",
      "leftIcon": "dynamic:ContractIcon"
    },
    {
      "id": 2487,
      "name": "MDMS",
      "url":"/mdms-v2/v2/_create/ACCESSCONTROL-ROLEACTIONS.roleactions",
      "displayName": "Create ACCESSCONTROL-ROLEACTIONS roleactions",
      "orderNumber": 1,
      "parentModule": "",
      "enabled": true,
      "serviceCode": "MDMS",
      "code": "null",
      "path": ""
    },{
      "id": 2488,
      "name": "MDMS",
      "url":"/mdms-v2/v2/_update/ACCESSCONTROL-ROLEACTIONS.roleactions",
      "displayName": "Update ACCESSCONTROL-ROLEACTIONS roleactions",
      "orderNumber": 1,
      "parentModule": "",
      "enabled": true,
      "serviceCode": "MDMS",
      "code": "null",
      "path": ""
    }

Here is the sample code for the roleactions::

{
      "rolecode": "MDMS_ADMIN",
      "actionid": 2486,
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "MDMS_ADMIN",
      "actionid": 2487,
      "actioncode": "",
      "tenantId": "pb"
    },
    {
      "rolecode": "MDMS_ADMIN",
      "actionid": 2488,
      "actioncode": "",
      "tenantId": "pb"
    }

Push the localization messages using the rainmaker-schema module to the schema's name(on the Add Master Data page and sidebar), tooltips, and all the fields on the UI. Example::

{
   "code": "SCHEMA_ACCESSCONTROL_ROLEACTIONS_ROLEACTIONS",
   "message": "Role Action",
   "module": "rainmaker-schema",
   "locale": "en_IN"
},
{
   "code": "ACCESSCONTROL_ROLEACTIONS_ROLEACTIONS_TENANTID",
   "message": "Tenant Id",
   "module": "rainmaker-schema",
   "locale": "en_IN"
},
{
   "code": "TIP_ACCESSCONTROL_ROLEACTIONS_ROLEACTIONS_TENANTID",
   "message": "Tenant Id",
   "module": "rainmaker-schema",
   "locale": "en_IN"
}