Master Migration Document
2.9 release master migration document
Overview
This page contains the changes related to core and municipal services along with the MDMS, DevOps and configuration setups required to accommodate multi-tenancy. Browse through the details below to learn more about the Central Instance.
Refer to SAAS Guidelines for Central Instance to find additional information.
Migration Steps
Service-request Module - Citizen Feedback Module
The service-request module is required for the surveys to work. Follow the steps given below:
Add the Service-request module
Add the new persister file: service-request-persister
Add the Helm chart
Configure the build
Make the role action-mapping changes in the MDMS
Click on the Job-builder once the above steps are complete.
Restart the following services: egov-accesscontrol, egov-mdms-service, egov-persister
Deploy the service-request module build
For further details on how to use Citizen-feedback APIs refer to the Citizen Feedback service.
Create the Citizen Feedback Service definitions (as mentioned in the above Citizen Feedback Service document) for modules and flows as per requirement before using it on the UI.
Note: Service definition creation is a backend task that requires sending an API request using tools like Postman. This task is typically performed once during the initial setup process.
New KPIs
Refer to KPIs: Pendancy, Citizen Feedback and Pt-SLA changes and make changes as per the document.
Restart dashboard analytics with Cluster-configs.
UI Migration Changes
Central Instance:
Find the details for prepping the UI build for a new instance.
UI build preparation for a new instance
Citizen Consent Form:
This feature allows citizen users to give their consent at the time of logging in.
Add this MDMS file
Documentation: a. Refer to Citizen Consent Form b. Restart MDMS and deploy the latest front-end builds.
Citizen Feedback:
A functionality that allows users to provide the user facility to submit feedback/ratings at the end of the service.
Add the MDMS file available here: https://github.com/egovernments/egov-mdms-data/blob/QA/data/pb/common-masters/RatingAndFeedback.json
In the provided configuration, the parameter headerByRating
is utilized to specify the value for the star condition, along with the corresponding message to be displayed on the UI screen. The enabledScreensList
parameter is used to indicate the specific flows where the Citizen feedback screen will be presented, allowing citizens to provide reviews.
The rating component is utilized for displaying star ratings on the citizen feedback screen. You can locate this component within the micro-ui-internals folder on the following GitHub link: Rating.js.
Documentation
a. Refer to Citizen Feedback Documentation for more details.
b. Restart MDMS and deploy the latest front-end builds.