Master Migration Document for 2.8

Owned by Kaviyarasan P
Last updated: May 17, 2023 by Hina Makhija
4 min read

 

  • 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

      • Update has to be added as a patch to the first release of 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

  • Sewerage modify connection

  • Sewerage Disconnection

  • Water Disconnection

  • Water and sewerage Disconnection Localization

    • Upsert the localizations as mentioned in the sheet


  • Privacy feature - By default encryption & privacy 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"

    }

 

 

 

  • After above changes, deploy following builds:

    • Ws-services

    • Property-services

    • Sw-services

    • Inbox

    • Restart egov-user service

 

  • Impact of privacy framework 

    • The privacy implementation masks the PII information based on mdms config(Security Policy)

    • 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.

    • 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.

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

    • Policy should be defined for adding or removing fields from encryption process

 

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

    • Deploy the latest builds provided for the 2.8 release {builds}

    • Add privacy configs to MDMS (SecurityPolicy.json)

    • Restart the MDMS service followed by the encryption service

    • 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.

    • Trigger the encryption of old data through the provided APIs 

    • Validating the encryption of old data {Doc Link}

    • Disable & enable decryption.privacy

      •  water.decryption.abac.enabled=true 

      • sewerage.decryption.abac.enabled=true

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

    • Deploy the latest builds provided for the 2.8 release

    • Add privacy configs to MDMS (SecurityPolicy.json)

    • Restart the MDMS service followed by the encryption service

    • Add the temporary index config update index with encrypted data

    • Add the new index config for the fuzzy search index 

    • Trigger the encryption of old data through the provided APIs 

    • Validating the encryption of old data {Doc Link}

    • Disable & enable decryptionprivacy 

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

  • Inbox
    Devops changes:

    • Add path for searcher for inbox: file:///work-dir/configs/egov-indexer/privacy-audit.yaml here.

    • Add path for searcher:
      file:///work-dir/configs/egov-searcher/inboxBillAmendmentWsSearch.yml,file:///work-dir/configs/egov-searcher/inboxBillAmendmentSwSearch.yml here

    • Add new property for inbox 

    • Add searchpaths - "NewWS1,ModifyWSConnection,DisconnectWSConnection":{"searchPath":"http://ws-services.egov:8080/ws-services/wc/_search","dataRoot":"WaterConnection","applNosParam":"applicationNumber","businessIdProperty":"applicationNo","applsStatusParam":"applicationStatus"},"NewSW1,ModifySWConnection,DisconnectSWConnection":{"searchPath":"http://sw-services.egov:8080/sw-services/swc/_search","dataRoot":"SewerageConnections","applNosParam":"applicationNumber","businessIdProperty":"applicationNo","applsStatusParam":"applicationStatus"},"WS.AMENDMENT,SW.AMENDMENT":{"searchPath":"http://billing-service.egov:8080/billing-service/amendment/_search","dataRoot":"Amendments","applNosParam":"consumerCode","businessIdProperty":"amendmentId","applsStatusParam":"status"} here

    • Following variables need to be added in env-secrets file :

      elasticsearch: egov-es-username egov-es-password

    • Following variables need to be overridden in env file:

      #W&S indexes water.es.index=water-services sewerage.es.index=sewerage-services

       



  • Bill genie

    • No changes required

  • Bulk Bill PDF Generation and Performance Testing

    • Enhancement is part of the new build release.

  • W&S Bulk Bill Generation and Performance Testing

  • privacy integration - PT

    • Covered as part of privacy above

  • Notification based on channels - PGR

    • Localisation added as part of release KIT

  • Notification based on channels - mCollect

    • Localisation added as part of release KIT

  • OBPS/ BPA (Notifications only)

    • Localisation added as part of release KIT

 

MDMS & Configs -

BackWard Compatibility Results -

UI changes:

Please Add all mdms changes before deploying the UI code

  • W&S: W&S UI/UX RevampI.

    • No changes needed, it will work automatically if we deploy.II. There are two enhancements in 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 needed, it will work automatically if we deploy. It is based on the configuration of the backend.

  • Standard Reports for WnS

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

 

Old UI: 

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