Property Mutation Document MDMS configuration

In this Document we see about MDMS configurations that are being used in the Property Mutation flow.

In the MDMS call we will get the Dropdown values and List of Documents that is present while entering the Form .

  MdmsCriteria: {
      tenantId: tenantId,
      moduleDetails: [
          {
            moduleName: "common-masters",
            masterDetails: [{ name: "OwnerType" }, { name: "OwnerShipCategory" }]
          },{
            moduleName: "egov-location",
            masterDetails: [
              {
                name: "TenantBoundary"
              }
            ]
          },
          {
            moduleName: "tenant",
            masterDetails: [
              {
                name: "tenants"
              }
            ]
          },
          {
            moduleName: "PropertyTax",
            masterDetails: [
              { name: "OwnerTypeDocument" },
              { name: "ReasonForTransfer" },
              { name: "MutationDocuments" }
                       ]
          }
        ]
    }

Here we can see detail about each master details, in Property Tax

1. OwnerTypeDocument is the Document type corresponding to each owner’s special category type.

each document type will have following structure,

 {
      "name": "Certificate issued by DC/ Competent Authority",
      "code": "COMPETENTAUTHORITY",
      "ownerTypeCode": "FREEDOMFIGHTER",
      "active": true
    },

https://github.com/egovernments/egov-mdms-data/blob/a20c764ae669c86cdfbcbccd80cacd496361e084/data/pb/PropertyTax/OwnerTypeDocument.json

2. ReasonForTransfer is list of transfer ownership options available for applying mutation.

https://github.com/egovernments/egov-mdms-data/blob/d561850081af55c4d2b22ac657d7aebc4b2b8d64/data/pb/PropertyTax/ReasonForTransfer.json

3. MutationDocuments is the list of documents required for transfer of ownership.

we see more about MDMS call for Document .

It is being used in two screens,

1.Document Required popup

2.Document Upload screen (Step 4 in Creating Property)

Reference :

https://github.com/egovernments/egov-mdms-data/blob/master/data/pb/PropertyTax/MutationDocuments.json

1.Document Required Popup .

It is a Popup shows user before applying about what all documents required for Transfer of Ownership of a Property.

Its Configuration are present in the ,

dev-packages\egov-pt-dev\src\ui-config\screens\specs\pt-mutation\requiredDocuments\reqDocs.js

https://github.com/egovernments/frontend/blob/0024529285b09a257154e15c5202f2f084fd6469/web/rainmaker/dev-packages/egov-pt-dev/src/ui-config/screens/specs/pt-mutation/requiredDocuments/reqDocs.js

2.Document Upload Screen,

It is the last screen before summary while transferring ownership of a Property , here it collects document information to verify the entered User Information is Valid.

Here we see detail about each configuration in the MDMS Documents.

Each Document value will have following structure

  {
      "code": "OWNER.SPECIALCATEGORYPROOF",
      "documentType": "OWNER",
      "required": true,
      "active": true,
      "hasDropdown": true,
      "additionalDetails": {
        "filterCondition": {
          "filterValue": [
            "NONE"
          ],
          "jsonPath": "Property.ownersTemp",
          "onArray": true,
          "arrayAttribute": "ownerType"
        },
        "dropdownFilter": {
          "parentArrayJsonPath": "Property.ownersTemp",
          "parentJsonpath": "ownerType"
        }
      },
      "dropdownData": [
        {
          "code": "OWNER.SPECIALCATEGORYPROOF.SERVICEDOCUMENT",
          "active": true,
          "parentValue": [
            "FREEDOMFIGHTER",
            "DEFENSE"
          ]
        },
        {
          "code": "OWNER.SPECIALCATEGORYPROOF.HANDICAPCERTIFICATE",
          "active": true,
          "parentValue": [
            "HANDICAPPED"
          ]
        },
        {
          "code": "OWNER.SPECIALCATEGORYPROOF.BPLDOCUMENT",
          "active": true,
          "parentValue": [
            "BPL"
          ]
        },
        {
          "code": "OWNER.SPECIALCATEGORYPROOF.DEATHCERTIFICATE",
          "active": true,
          "parentValue": [
            "WIDOW"
          ]
        }
      ],
      "description": "OWNER.SPECIALCATEGORYPROOF.SPECIALCATEGORYPROOF_DESCRIPTION"
    }

In Each Document we have configurations

1.Attribute “dropdownFilter” it can be used for filtering all the options for each document in document upload screen based on previous value that is being entered in previous screens.

it is configured as

here parentArrayJsonPath is the JSON path of the Array element if we need to check the values in an array

if it is not a type array then use “parentJsonpath”.

once the value is fetched then it will compare with each option of the dropdown

here “parentValue” is an array which will have all the values for which it should be shown.

Similar to the Dropdown filter we have option to show / hide document upload option based on previous values.

configuration for that is as follow

here “filterValue“ is an array which will have all the values for which it should be shown.

“jsonPath“ corresponds to the objects path where it should be compared with.

“onArray“ is true if it needs to be compared with an Array of objects

“arrayAttribute“ the value corresponds to the array attribute from which values will be compared

Based on this document will be shown / hidden.

“dropdownData“ will have the following structure

here code corresponds to the Label of the dropdown option

active corresponds to option is active / inactive

parent value used for filtering the options present in the document upload .