UI Configuration
UI configuration for app
Last updated
Was this helpful?
UI configuration for app
Last updated
Was this helpful?
This page provides details about the MuktaSoft UI configuration required to enable it in any environment.
In the DevOps repository of your organization, locate the following "deploy-as-code/helm/environments/works-dev.yaml"
. Inside the environment YAML file used to deploy the Works platform, please add the following block of code:
A dev environment sample file is linked . Note that you will have to modify this for your deployment.
This section contains a config that is applicable globally to all UI modules. These need to be configured prior to service-specific UI configurations.
Create a config file (globalconfigs.js) with below-mentioned configurations (see 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 .
All the UI Screen configurations required for MUKTA are present in this folder . For other MDMS configurations, please check .
Please refer to the table in for screen-specific role configuration. Note that some of this will overlap with configurations done for the backend service modules. If already present in MDMS, please ignore it.
All strings localized per module are provided in this . To translate the UI into other languages, please follow this sheet and provide appropriate translations in your language.
Figma screens for the UI are . Refer to them to understand the MUKTA UI.