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.
Steps:
In the DevOps repository of your organization, locate the following - "deploy-as-code/helm/environments/works-dev.yaml"
.
Add the code block below to the environment YAML file used to deploy the Works platform.
This section contains the configurations applicable globally to all UI modules. These need to be configured before service-specific UI configurations.
Generate a configuration file named "globalconfigs.js" using the settings provided (refer to the code below).
Set up all the images and logos needed in your S3 storage, and include the links as "footerBWLogoURL" and "footerLogoURL."
Specify the state tenant ID as "stateTenantId."
If any user roles should be marked as invalid, list them under "invalidEmployeeRoles."
Upload this global configuration file to your S3 bucket, naming it "globalconfigs.js."
A dev environment sample file is available . Make sure to modify this for your deployment.
Make sure to include the URL of the "globalConfigs" file in your .
The UI Screen configurations required for MUKTA are present in the folder . Click for the remaining MDMS configurations.
Refer to the table in for role configurations specific to each screen. Keep in mind that certain configurations may already exist in the MDMS for backend service modules. If they are already present, there's no need to duplicate them.
Refer to the which contains all module-specific localized strings for translations. To convert the UI into other languages, follow the information in this sheet and provide the correct translations in your desired language.
Figma screens for the UI are available . Refer to them to understand the MUKTA UI.