Master Migration Document

2.8 release master migration document

Bill Amendment (Billing-service)

W&S Bill Amendment workflow config migration

• Follow the steps mentioned in the W&S Bill Amendment Workflow config migration document.

• Verify once if workflow name is hardcoded except edited parts of UI, Backend - check in indices and report - checked not present except config

• Verify if wf config is there for tenant level or state level only

• An update has to be added as a patch to the first release of the amendment

Water & Sewerage

• Latest persister file - Water

• Latest persister file - Sewerage

Note : Replace the existing persister files with the latest files linked above.

• Water modify connection

  • Workflow config

• Sewerage modify connection

  • Workflow config

• Sewerage Disconnection

  • Workflow config

• Water Disconnection

  • Workflow config

Privacy Feature

By default encryption & privacy is disabled for 2.8

• To disable privacy for Property and W&S make changes in the MDMS- DataSecurity -> SecurityPolicy.json file.

• For models- Property,PropertyDecrypDisabled, WnSConnection, WnSConnectionOwner, WnSConnectionDecrypDisabled, WnSConnectionOwnerDecrypDisabled, WnSConnectionPlumber, WnSConnectionPlumberDecrypDisabled; insert only one attribute in the attributeList as follows:

 {
         "name": "sample",
         "jsonPath": "sample",
         "patternId": null,
         "defaultVisibility": "PLAIN"
    }

• Insert the name and jsonPath which are not actually expected to be present in the RequestBody/ResponseBody

• Files to be updated

  1. Security policy complete file

  2. Masking patterns - needed only if enc is enabled and carried our for old data.

• References for reading

  1. PT,W&S decryption policy

  2. Decryption Disabled config for PT,W&S

  3. W&S Plumber enc/dec

  4. Inbox decryption config

  5. Reindexing enc/dec config

• Once the above changes are done deploy the following builds:

  1. Ws-services

  2. Property-services

  3. Sw-services

  4. Inbox

  5. Restart egov-user service

• Impact of privacy framework

  1. The privacy implementation masks the PII information based on the MDMS config (Security Policy)

  2. The masking/unmasking of data is entirely dependent on the roles of the users in the system, adding or removing these roles from the config will enable masking for each role.

  3. There is no module-level control here, so if a W&S role is added to an employee of TL then data will be masked so cross-using of roles should be avoided.

  4. The agreement with Manish is that the privacy be disabled until redesign with the module filter - Done

  5. The policy should be defined for adding or removing fields from the encryption process.

  
• W&S privacy (Skip over if encryption is not carried out)

  1. Deploy the latest builds provided for the 2.8 release {builds}

  2. Add privacy configs to MDMS (SecurityPolicy.json)

  3. Restart the MDMS service followed by the encryption service

  4. Add the temporary index config update index with encrypted data

     • This file will fetch data from the Encryption of old data and upload it to the existing index so that the index will be encrypted or masked as per config.

  5. Trigger the encryption of old data through the provided APIs

  6. Validating the encryption of old data {Doc Link}

  7. Disable & enable decryption.privacy

     • water.decryption.abac.enabled=true

     • sewerage.decryption.abac.enabled=true

• PT privacy (Skip over if encryption is not carried out)

  1. Deploy the latest builds provided for the 2.8 release

  2. Add privacy configs to MDMS (SecurityPolicy.json)

  3. Restart the MDMS service followed by the encryption service

  4. Add the temporary index config update index with encrypted data

  5. Add the new index config for the fuzzy search index

  6. Trigger the encryption of old data through the provided APIs

  7. Validating the encryption of old data {Doc Link}

  8. Disable & enable decryptionprivacy

     • property-decryption-abac-enabled: "true"

• Bill genie

  1. No changes required

• Bulk Bill PDF Generation and Performance Testing

  1. Enhancement is part of the new build release.

• W&S Bulk Bill Generation and Performance Testing

  1. PR List

     • W&S calculators

     • Bug Fixes on calculators

     • Billing service

     • UM-1035: Bulk Bill Performance:: Bills are not generating after hitting the job scheduler API.SIGNED OFF
     • UM-591: W&S: Bulk bill performance fixes merge it to product from 2.3 (Odisha branch) and testSIGNED OFF
• privacy integration - PT

  1. Covered as part of privacy above

• Notification based on channels - PGR

  1. Localisation added as part of the release KIT

• Notification based on channels - mCollect

  1. Localisation added as part of the release KIT

• OBPS/ BPA (Notifications only)

  1. Localisation added as part of the release KIT

• National Dashboard Adaptor Integration Testing

  1. The Docs are specific to Punjab implementation, generic product document is in the pipeline.

• NationalDashBoard 3 New KPI

  1. CharApiConfig.json

  2. MasterDashboardConfig.json

     • Overview Card config

     • Property Tax config

  3. DevOps change

• Finance Module State DSS

  1. Dss Chart API config

• MDMS & Configs -

  1. Complete Localisation

  2. Complete MDMS

  3. Complete configs

BackWard Compatibility Results -

• Folder Link

UI Changes

Please add all MDMS changes before deploying the UI code.

• W&S: W&S UI/UX Revamp

  • No changes are needed, it will work automatically if we deploy. There are two enhancements in the W&S flow, i.e Edit by normal user and Edit by config user, it is based on the MDMS configuration (Link). This is applicable in all 3 flows.

• W&S disconnection

  • No changes needed, it will work automatically if we deploy.

• Bill amendment W&S UI/UX RevampI

  • No changes needed, it will work automatically if we deploy.

• Bill Genie UI/UX revamp

  • No changes needed, it will work automatically if we deploy.

• OBPS Tabular Reports in old

  • No changes needed, it will work automatically if we deploy. It is based on the configuration of the backend.

• TL Tabular Reports

  • No changes are needed, it will work automatically if we deploy. It is based on the configuration of the backend.

• Standard Reports for WnS

  • No changes are needed, it will work automatically if we deploy. It is based on the configuration of the backend.

• Core UI Changes (Banner Images of Each module)

  • No changes are needed, it will work automatically if we deploy. It is based on the configuration of the MDMS (Link)

  • We need to add the below images in the S3 bucket:PGR: https://egov-uat-assets.s3.amazonaws.com/PGR.png

  • PT: https://egov-uat-assets.s3.amazonaws.com/PT.png

  • TL: https://egov-uat-assets.s3.amazonaws.com/TL.png

  • OBPS: https://egov-uat-assets.s3.amazonaws.com/OBPS.png

  • FSM: https://egov-uat-assets.s3.amazonaws.com/FSM.png

  • WS: https://egov-uat-assets.s3.amazonaws.com/WS.png

  • Bills: https://egov-uat-assets.s3.amazonaws.com/Bill.png

• Navigation re-direction from New UI to OLD UII. Mdms Changes are required for this (Link).

Old UI

Only Fire Noc and Tabular reports are PO signed off in the current release for the OLD UI, the rest of the modules are covered as part of backward compatibility tests shared above.