Page Comparison

eGov-Survey-Service

...

Persister config

...

Mdms

...

• 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

  • Workflow config

• Sewerage modify connection

  • Workflow config

• Sewerage Disconnection

  • Workflow config

• Water Disconnection

  • Workflow config
    

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

...

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

• Files to be updated

  • Security policy complete file

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

• References for reading

  • PT,W&S decryption policy

  • Decryption Disabled config for PT,W&S

  • W&S Plumber enc/dec

  • Inbox decryption config

  • Reindexing enc/dec config

...

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

...

• 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

  • PR List 

    • W&S calculators

    • Bug Fixes on calculators

    • Billing service

    • Jira Legacy
      server System JIRA serverId f37df377-51a7-3f0b-bde6-77fa6960492d key UM-1035

    • Jira Legacy
      server System JIRA serverId f37df377-51a7-3f0b-bde6-77fa6960492d key UM-591

      
      

• 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

...