Edit

PT - Steps To Configure Privacy

Detailed steps to configure privacy in property tax module

Overview

To ensure that the system works as expected after enabling privacy, we will require some configurations to be made in the environment. This document contains the steps to ensure the successful implementation and working of the Property Tax module.

Steps

Following will be the changes required to move it to other environments:

"_source": {
        "excludes": [
          "Data.street",
          "Data.doorNo",
          "Data.ownerNames"
        ]
      }

Sample index at the bottom.

In the params list in both the above curls, “tenantIds” param can either be provided with a single tenantId or a list of tenantIds for encrypting the data with respect to the provided tenantIds. However, to encrypt the data for all tenantIds in the system, tenantIds param itself should be removed.

To validate if the encryption is completed, you can check with the following dB queries:

  • select * from eg_pt_enc_audit order by createdtime desc;

  • select count(*) from eg_pt_id_enc_audit;

With this query, it can be validated if all records are there or not. The count should match with the total count of records in the eg_ws_connection table.

  • select * from eg_pt_id_enc_audit;

This can help you check what all properties have been updated so far. This table contains the id, applicationnumber, connectionnumber and tenantid.

Sample Index for point 8:

PreviousPT Privacy ChangesNextPT - Create Property UI Details

Last updated

Was this helpful?