National Dashboard New KPIs

Citizen Feedback

Citizen Consent Form

Central Instance

No additional test cases have been added for the central instance. The existing test cases should work for the central instance as is.

About Local Governance

The DIGIT-powered local governance solution catalyses digital transformation across towns and cities - changing how citizens interact with government bodies. As a digital public good, the DIGIT Local Governance stack fosters an open digital ecosystem, enabling co-creation and deployment of locally relevant solutions that enhance business operations and improve overall quality of life. By transforming local governance, this initiative not only elevates citizen well-being but also accelerates the nation's economic growth.

Useful Links

Contact Us

Release Summary

Local Governance 2.9 release includes the following changes:

• Citizen Consent Form

MDMS Changes

Trade license applications pass through various stages where details are scanned, verified, and inspected before the final approval. The workflows are defined at the State or ULB level and adjusted to meet individual department requirements.

The prescribed stages through which trade license applications are routed include -

1. Document Verification

2. Field Inspection

3. Approval

Overview

This page contains the changes related to core and municipal services along with the MDMS, DevOps and configuration setups required to accommodate multi-tenancy. Browse through the details below to learn more about the Central Instance.

Refer to SAAS Guidelines for Central Instance to find additional information.

Migration Steps

Service-request Module - Citizen Feedback Module

The service-request module is required for the surveys to work. Follow the steps given below:

1. Add the

2. Add the new persister file:

3. Add the

4. Configure the build

1. Make the role action-mapping changes in the MDMS

1. Click on the Job-builder once the above steps are complete.

2. Restart the following services: egov-accesscontrol, egov-mdms-service, egov-persister

3. Deploy the service-request module build

   For further details on how to use Citizen-feedback APIs refer to the .

New KPIs

1. Refer to and make changes as per the document.

2. Restart dashboard analytics with Cluster-configs.

UI Migration Changes

• Central Instance:

Find the details for prepping the UI build for a new instance.

• Citizen Consent Form:

This feature allows citizen users to give their consent at the time of logging in.

Add this MDMS

Documentation: a. Refer to b. Restart MDMS and deploy the latest front-end builds.

• Citizen Feedback:

A functionality that allows users to provide the user facility to submit feedback/ratings at the end of the service.

Add the MDMS file available here:

In the provided configuration, the parameter headerByRating is utilized to specify the value for the star condition, along with the corresponding message to be displayed on the UI screen. The enabledScreensList parameter is used to indicate the specific flows where the Citizen feedback screen will be presented, allowing citizens to provide reviews.

The rating component is utilized for displaying star ratings on the citizen feedback screen. You can locate this component within the micro-ui-internals folder on the following GitHub link: .

Documentation

a. Refer to for more details.

b. Restart MDMS and deploy the latest front-end builds.

Click on Inbox to view the list of applications submitted.

Click on the relevant Application Number hyperlink to open and view the application details.

Scroll down the application and click on the Take Action button. Click on Pay.

Enter the Payment and Payer Details. Click on Collect Payment to process the payment.

The system generates a unique payment Receipt Number. Click on the Print Receipt button to print the receipt. Click on the Go Back to Home Page button to navigate back to the home page.

Click on the Renew Trade Licence option on the home page.

Click on the relevant Trade Licence Number to renew. Edit the trade license details in the application form as required.

Click on the Take Action button. Click on the Renew Trade Licence option.

The user can renew it without modifying the trade details or it can be modified. If it is modified, it goes into application processing similar to a new TL application. If it is not edited then renewal happens in real time after making payment.

Log in with Document Verifier credentials.

The employee landing page displays the list of applications waiting for processing. Use the search filters on the page to find specific applications from the list.

Click on the Application Number hyperlink to open the application.

Scroll through the application details and review the uploaded documents.

Click on the Take Action button and click on Verify and Forward option if all documents are found complete and satisfactory.

Select the Assignee Name. The application will be forwarded to the selected assignee for field inspection.

In case, the documents are found incomplete or missing, click on Send Back to Citizen option. This will send back the application to the citizen for necessary action.

Click on the Reject option if the application details are found inaccurate. This will reject the application.

Log in with Field Inspector credentials.

The employee landing page displays the list of applications waiting for processing. Use the search filters on the page to find specific applications from the list.

Click on the Application Number hyperlink to open the application.

Scroll through the application details and review the details.

Click on the Take Action button and click on the Verify and Forward option if all details are found complete and satisfactory.

Select the Assignee Name. The application will be forwarded to the selected assignee for approval.

In case, the documents and details are found incomplete or missing, click on Send Back to Citizen option. This will send back the application to the citizen for necessary action.

Click on the Reject option if the application details are found inaccurate. This will reject the application.

Click on Send Back option to send the application back to the previous employee (document verifier in this case) for further action.

Log in with Approver credentials.

The employee landing page displays the list of applications waiting for processing. Use the search filters on the page to find specific applications from the list.

Click on the Application Number hyperlink to open the application.

Scroll through the application details and review the details.

Click on the Take Action button and click on the Approve option if all documents and details are found complete and satisfactory. The trade license is approved and a Trade License certificate is issued to the applicant.

Click on the Reject option if the application details are found inaccurate. This will reject the application.

Click on Send Back option to send the application back to the previous employee (field inspector in this case) for further action.

The TL application is approved and the TL Certificate is issued to the applicant. Click on the Download or Print button to download or print the TL Certificate.

Overview

A few reports are added to the TL module for administrative purposes.

Release Highlights

Overview

Reports have been added to birth and death for administrative purposes.

Release Highlights

Overview

About page, FAQ and 3 new KPIs are added to the DSS page

Release Highlights

Overview

The Local Governance stack is a set of open APIs, services, and reference implementations, set up as a public good, to allow government entities, businesses, startups, and civil society to use a unique digital infrastructure and build solutions for urban India at a large scale. It provides a set of open standards, specifications and documentation to create a level playing field and enable ecosystem players to innovate on the stack. As a public good, the solutions are available to all members of society without profits or restrictions.

Citizens can renew their existing trade applications on the DIGIT portal. CE can also apply for TL renewal on behalf of the citizens.

My Applications option allows applicants to view their applications and track their status.

Employees can -

Citizens and CE

Citizens represent individuals, communities, or business entities who are the system end-users. The TL module allows business owners to apply for a trade license online or even apply for the renewal of an existing license.

The citizen can also approach the Counter Employee (CE) to submit new TL applications or raise renewal requests for existing licences.

The Citizen or CE role can -

Follow the same steps as outlined in the workflow to update the application.

Log in to the employee portal using your credentials.

Click on the New Application option in the top left corner of the landing page.

An employee can create the application on behalf of citizens over the counter.

Select the applicable Financial Year for which the trade license is to be issued.

Fill in the application details (same as given in the citizen application process).

Click on the Submit button once all details are found complete and accurate.

A unique application reference number is generated. This number is used to access the application and for further processing. The citizen receives a notification along with this application number in the registered mobile number.

Overview

This release provides PRDs of 3 property tax features and a few bug fixes.

Release Highlights

PRDs of 3 property tax features and bug fixes.

4. Property mutation bug fixes

Release Features

None

Known Issues

Bug

Upcoming Release Features

None

Reference Doc Links

Overview

This release offers the UI/UX revamp of the Residential Construction Permit System, workflow timeline changes and reports.

Release Highlights

The functionality in OBPS remains the same - only the UI/UX has changed.

Two reports were added for administrative purposes.

Changes made to the workflow timeline for clear representation of application status to the users.

Notification based on channels.

Release Features

• Stakeholder registration and employee approval flow

• Architect flow (permit application creation) and employee approval flow

• Architect occupancy certificate creation and employee approval flow

• Fire NOC employee approval flow

Residential construction permit application status report

Workflow timeline changes in application flow - The image below the one illustration on the right displays the old status view. Here the application status shows pending even if the task is completed. As per the current release, the application displays only the current state where the action is marked as pending. The remaining status is marked as done or completed or in a submitted state.

Notification based on channels - The residential construction permit application allows the user to configure different messages for different channels (In-app, mobile messages, email) for the same event in the application process flow.

Known Issues

​

Upcoming Release Features

None

Reference Doc Links

Overview

UI/ UX revamp of bill amendment.

Release Highlights

UI/UX revamp of Bill Amendment Inbox and Application View.

Release Features

Known Issues

None

Upcoming Release Features

None

Reference Doc Links

Overview

UI/ UX revamp of Bill Genie.

Release Highlights

UI/UX revamp of Bill Genie features.

Release Features

Known Issues

None

Upcoming Release Features

None

Reference Doc Links

Overview

This module allows employees to create surveys for citizens and let them fill out surveys. Later survey results can also be seen on the Survey results dashboard.

Release Highlights

The Survey module consists of the following

For Employees

1. Surveys section on Home Page

2. Surveys inbox

3. Create survey

   • Meta Data - Title, Description, Survey start & end date/time

For Citizens

1. Notification on Survey creation.

2. Survey Filling

Known Issues/ Upcoming Enhancements

1. Expansion to other types of questions

2. More notifications to citizens prior to survey start, and survey end.

3. Making surveys open. (Right now citizens need to be logged in to fill out the survey. This needs to be made open)

Related Doc Links

Overview

This module gives citizens more information on a service delivery module than just links to access the service.

Release Highlights

Product Specific Pages Module consists of the following:

For Citizen

For a module and tenant that is configured.

1. FAQs

   • List of FAQs for each module

2. How it works

Known Issues/ Upcoming Features

Related Doc Links

The module offers citizens and governance bodies a convenient and transparent means of processing trade licenses. A trade licence is permission the local governing bodies issue to carry on a specified business or trading activity within the authorized area. It is a mandatory document required to run a business or commercial activity.

Using Local Business License Issuing Module

Click on the relevant role below to learn more about how to use the trade license solution.

Introduction

The Local Business License Issuing application makes the process of obtaining a business license easy, smooth, and transparent. The module removes the need for manual processing and streamlines the key business license management functions to provide a better user experience.

Module Features

The module enables citizens to -

1. Apply for a new trade license or renew an existing trade license.

2. Upload all the relevant documents required for the license.

3. Make payment for the Trade License (New/Renewal) fee using the online payment gateway.

4. Receive notifications and alerts by email or SMS for new application status updates and pending renewals.

The module enables employees to -

1. Create flexible role-based workflows.

2. Configure license fee calculation logic.

3. View custom dashboards for module statistics.

4. Filter search results using advanced configurable search parameters.

Module Ontology

State Level

ULB Level

Module Reports

1. Receipt Register

2. Application Status

3. Cancelled Receipt Register

4. ULBwise Collection Report

Citizens

Citizens represent individuals, communities, or business entities who are the system end-users. The PT module allows property owners to register their property details online. These details are then used for various property-related transactions.

The citizen can also approach the Counter Employee (CE) to register new property, assess property or pay property tax.

The citizen can -

• ​​

The search application facility enables users to search for an application.

Click on the Search Application option available in the employee inbox.

Enter at least one or multiple search parameters to find the application. The parameters are Application No., Owner Mobile No., Unique Property ID., Application Type, Application Status, From Date and To Date.

Search results show 10 records at a time on a page with the option to navigate to the next page.

Employee Inbox provides the option to search for applications in different states or workflow. Employees get a view of applications assigned to them for further processing.

Enter at least one or multiple parameters to refine the search for property applications. The parameters include Application No., Mobile No., and the Unique Property ID.

Click on the Search button to view the search results. The search results show the filtered list of property applications along with their status.

Other filters available to refine the view of applications are -

• Assigned to Me

• Assigned to All

• Locality

• Application Type

Click on the Unique Property ID hyperlink in the search list screen to access the details. Click on the Clear Search button to renew the search parameters.

Edit property allows users to make changes to the property details. The system allows users to make partial edits too.

To make changes search and view the property details. Click on the Edit Property option in the Action column for the corresponding property. The following details can be edited for the property:

• Only Street Name and Door No. can be edited in the Location Details.

• All information can be edited in the Assessment Details.

• None of the information allowed for edits in the Ownership Details.

• Documents can be re-attached.

Follow the same flow as in to submit the changes.

Find the relevant property and click on the Unique Property ID to view the property details.

Click on the Payment History option available right below the Total Dues detail on the Property Information page. All payments made to date for the given property are displayed on the screen.

Click on the Download Receipt link available for individual cards to download the receipt in PDF format.

To edit applications, navigate to the Inbox page. Search for the application you want to verify by entering any of the search parameters.

Scroll down the application page and click on the Take Action button. Click on the Edit option.

Update the application details and attached documents as required. Submit the application for subsequent processing.

To reopen the application find and open the desired application. Scroll down the application page and click on the Take Action button. Click on the Reopen option.

Select the Doc Verifier name who will be responsible for verifying the application. Enter any Comments if required. Click on the Choose File button to upload any file or images in context. Click on the Reopen button.

The application is forwarded to the selected doc verifier for verification of documents.

About Local Business License Issuing System

The Local Business License Issuing System enables local government bodies to regulate trading establishments. It also serves to protect the interest of the public at large against possible health hazards and inconveniences that any business operation can cause. With the Business License Issuing application traders can obtain the trade certificate in a simplified manner and ensure compliance with rules and safety guidelines issued by the government. The module offers the citizens and governance bodies a convenient and transparent means of processing trade licenses.

The application makes obtaining a trade licence easy, smooth, and transparent. Hence, the module removes the need for manual processing and streamlines the key trade licence management functions to provide a better user experience.

The Inbox page contains 4 react components:-

Application Links

Application Links is a separate component that holds links to other pages of possible navigation from the inbox. This component is common in both mobile and desktop views. Links are conditionally rendered according to the user roles.

Introduction to PT

The Property Tax (PT) module offers the citizens and governance bodies a convenient and transparent means of processing property taxes. Local governing bodies identify the applicable tax slabs for different types of properties. The PT module assesses properties, calculates tax amounts, processes tax payments and generates tax collection reports.

About Property Tax

The Property Tax System is a self-serve web and mobile-based, easy-to-use and configurable application that addresses the objectives of municipal corporations and local government to automate all property tax operations, thus providing property tax assessment and payment services to citizens in real-time.

Search Application and Search License pages are used for searching any application/ license that may or may not be relevant to the workflow action of the logged-in users.

Search Application has 2 components.

Search Fields

A search field component is a form which takes inputs and passes them into tl-search API params. It utilizes SearchForm and SearchField components to create and arrange the form.

Property applications are rejected if the supporting documents uploaded by the applicant fail to comply with the property regulatory requirements or the details provided in the form are incorrect.

To reject applications navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on Application No. to open the application. Scroll down the form to review the filled-in details.

Click on the Take Action button available at the bottom of the page. Click on Reject.

Enter your Comments to state the reason for rejection. Click on the Upload Files button to upload any supporting documents to validate the rejection. Click on the Reject button.

The applicant will receive a rejection notification on his mobile number or email address.

DV sends back the applications to the citizens if some vital information is missing in the application or there is a mistake in the information provided.

To send back applications to the counter employee, navigate to the Inbox page. Search for the application you want to verify by entering any of the search parameters. Click on the Take Action button available at the bottom of the page. Click on the Send Back To Citizen option.

Select the Assignee Name who will be responsible for verifying the application. Enter any Comments stating why the application is sent back. Click on the Choose File button to upload any files or images in context and then click on the Send Back To Citizen button.

The application is assigned back to the selected assignee for verification of documents and at the same time, the citizen is allowed to edit the application to update the missing details.

To view property details, follow the steps outlined in the to find the property. The search results display the Unique Property ID, Owner, Locality, Application Status, Tax Due and Action details.

Click on the Unique Property ID hyperlink to view the corresponding property details.

The DV verifies and forwards the property applications to the Field Inspector if the DV finds all information and documents provided by the applicant correct.

To verify and forward the application navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on Application No. to open the application. Scroll down the form to review the filled-in details.

Click on the Take Action button available at the bottom of the page. Click on the Verify and Forward button. Select the relevant Assignee Name from the list of available employees for subsequent processing.

Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Upload Files to upload any supporting documents for the application. Click on the Verify and Forward button.

The property application is assigned to the selected assignee for subsequent processing.

To search for submitted applications or track the status of submitted applications

Navigate to the Property Tax home page. Click on the Search Property link.

Select the Locality. The system displays the registered localities based on the ULB selected at the time of logging in.

Enter any of the following search parameters or combinations to refine the property search - the Owner Mobile No. or the Unique Property ID allotted by the system or the Existing Property ID if there is any legacy ID linked to the property.

Click on the Search button to view the results. Click on the Clear Search button to renew the search with different parameters.

Renewal Flow

This feature allows the user to renew any trade license applications, which either has been expired or had to be renewed for current financial year (Approved and Paid), it also had integration with the payment component, in order to complete the flow all together for renewal.

Renewal can be two types:

• DIRECT RENEWAL

• EDIT RENEWAL

Renewal List

Once the user clicks on Renew Trade License button on the home page, it will redirect to the renewal list page which will display all the applications eligible for renewal corresponding to the mobile number on which the user has logged in. It will show the Trade name, License Number, Owner Name and status whether active or expired.

Once the user clicks on Renew Button, it redirects the user to the summary page just like in edit Trade license, with all the values pre-populated from the search API. The info card will be declared so that the user will understand how to proceed with either direct renewal or edit renewal.

Direct Renewal

If the user just wants to renew the same application without updating any data, it will cross-verify all the values in the summary page and then click on submit button directly at the end of the page, this will lead the application to the next status as pending for payment and user can go through payment flow from the acknowledgement screen also, by clicking on the Make Payment button.

Edit Renewal

If the user before renewal needs to update the application, they can do so by clicking on the change button on the summary screen, this will tell that the flow has been changed from direct to edit renewal, and the user will need to follow the same apply flow in order to complete the editing part of it. the values from the application will be pre-populated in the respective screens, to get the details about the edit flow, one can refer to this link. .

Once the user clicks on submit button it will change the current action of the application to pending for document verification as the data has been updated.

Technical Implementation Details

Renewal Trade main index can be found in the below-given link:

in this, we are calling the trade license search API, In order to get all the applications, through which the sorting is happened to classify which applications are eligible for renewal for the current financial year.

the hook which has been used for the API is:

The data from here then are sorted into the application which doesn’t have any open renewal application for the current financial year or which has a status of approved or expired. the significant method to get the renewal list of applications is mentioned below:

From here the Trade License List Component has been called which displays the list of the renewal application.

The main functionality of converting the License Object received from the API to the object structure for formdata for apply flow, following is done in a similar way as the edit trade, and the same method is being used to convert the response object, to know more details please refer to

Once the user has completed the flow as required or clicked the submit button directly, the method convertToEditTrade is being called, which re-arranges the data for the request body for the updated API /tl-services/v1/_update.

If it is a direct renewal only one update API is being called which updates the financial year only.

but if it is an edit renewal, two updated API is called after the first API successful call the application status gets changed to Initiated but after the second API call it is changed to applied. with the next action pending for document verification.

the code for these can be found in the utils folder index please refer to the below link for the same:

MDMS

MDMS data which is being used here is the same as the Apply flow only, as the flow structure used for edit renew trade is the same as the Apply for Trade License. Please refer to the link for detailed MDMS information.

Localisation

For Renew Trade also, the Localization keys are being added in the ‘rainmaker-tl’ locale module. Change, update or add any new localization key will be done in the same locale module only.

Objective

Provide employee purpose workflow actions.

The same screen is used for both application details and trade details.

Based on the conditions, we are showing the details here

Example: If the application is not in an approved state and the business Service New TL, then we are showing application details otherwise we are showing trade details.

Application Details

For workflow action details, please refer to the file below.

File Path:

Trade Details

Timeline View

It is common for all modules, find the path here:

The workflow is the same as Old UI only, please refer to the documentation link below.

Role Action Mapping

Edit Trade License

This feature allows the user to edit the application already created under their mobile number. After verifying employee can send the application back to the citizen with remarks on any changes that needed to be done, which can be edited by the user using this flow.

Edit Application

On the Application details page, on the employee side, if the application is marked with “Send Back to Citizen”, the edit option will appear dynamically at the end of the application details page, which the user can navigate through my applications.

After this, On clicking the button, the user can edit the trade license details by going through the Create Flow again. First, it will land on the Summary page, where for each section “change” button is there. Clicking on the Change button, the user will be redirected to the particular content, the only exception here will be the values will be pre-populated from the License object received from Trade License Search API, on completing the flow, Update API will be called and License application will get successfully updated.

Technical Implementation Details

Edit Trade License main index can be found in the link given below:

Here the main code consists of the function which results in transforming the License object received in Search API to the object structure which is suitable for citizen Apply flow (owner details, units, accessories etc), as the user needs to go through Apply flow again with pre-populated details and update the value of any accordingly. it also consists of the routing for the pages in the Apply flow.

getTradeEditDetails() function is being used so that the License object which is received from the Trade Search API, is converted to the Apply flow relevant structure so that the values can be pre-populated for the user convenience, on completing the flow, the application is updated. The link for the same can be found below:

User can delete and add as many accessory or units as it needs but there should be at least one unit to complete the application, to add a new unit or accessory “Add” button is used which is located at the end of the page. A new array is formed with all the updated details or with the old unit/accessory, when the flow is completed, this new array is then compared with the old array of accessories and units, and a new resulting array object is formed for the request body, you can find the respective code in the following method : gettradeupdateaccessories & gettradeupdateunits. this can be found in the below link

Similarly, for owners the method which is used to form the new request param array is gettradeownerarray

It is similar to Accessories and Units - the only difference is in UI. Users can’t select multiple owners and only add one owner, it needs to either add more than one owner or select a single owner in the ownership category and proceed. After the successful update, the application's next action will be “Pending for document verification” as there is an update in the data.

On completing the flow, the same object structure which was being used earlier in the flow gets changed into the request body structure for the update API: /tl-services/v1/_update, for this, the method which gets used is declared inside the Utils folder. Method name: convertToResubmitTrade and it can be found in the below link:

MDMS

MDMS data that is being used here is the same as the Apply flow only, as the flow structure used for edit trade is the same as the Apply for Trade License. Please refer to the link for detailed MDMS information.

Localisation

For Edit Trade also, the localisation keys are added to the ‘rainmaker-tl’ locale module. Change, update or add any new localization key is done in the same locale module only.

The amalgamation process is a service requiring the owner(s) to apply. A single application should include the details of all the properties and the necessary supporting documents. No application or processing fee is required for the amalgamation of properties.

Note: Users can search and pay the property taxes without even logging in to the application.

To collect the property tax, follow the steps outlined in Search Property to find the property. The search results display the property's Unique Property ID, Owner, Locality, Application Status, and Tax Due details.

Click on the Collect Tax hyperlink in the Action column for the specified property.

Verify the bill details. Click on Collect Payment to process the payment.

Citizens or CE can register new property details through the DIGIT web portal or the DIGIT mobile app.

To register a new property click on the Property Tax panel on the home page.

Click on the New Property Registration option on the panel. The new property application form page contains various sections that include Location Details Property Assessment Details, and Ownership Details Document Required.

On the Location Details page enter the Pincode, City, Locality/Mohalla, Street Name, and Door/House No.

On the Property Assessment Details form enter the Property Usage Type, Property Type, and Plot Size details.

Enter the Floor/Unit details based on the selected Property Type. Select Floor, Usage Type, Occupancy, and Built-Up Area (sq ft) details. Click on the Add One More Unit option to add more unit details.

In the Ownership Details section, enter the owner's Name, Gender, Mobile Number, Guardian Name, Relationship, Special Category, Email, Correspondence Address, and Firm/Business Name.

In the Documents Required section upload the relevant documents for Usage Proof, Construction Proof, Occupancy Proof, Address Proof, Identity Proof, and Registration Proof.

Click on the Submit button once all the details are entered and documents uploaded. The application is submitted and the New Property Successfully Added acknowledgement message appears on the screen along with the Application Number and the Property ID details.

Click on the Download or the Print button on top of the page to download or print the application.

The update mobile number feature allows citizens and ULBs to change the existing mobile numbers to current numbers. The details are updated accordingly in the property owner records. Citizens can update their mobile numbers in the property details through an OTP validation.

FI sends back the applications to the citizens if some vital information is missing in the application or there is a mistake in the information provided.

To send applications back to the citizen navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on Application No. to open the application. Scroll down the form to review the filled in details.

Click on the Take Action button available at the bottom of the page. Click on the Send Back to Citizen button. Enter any Comments stating why the application is sent back.

Click on the Choose Files button to upload any files or images in context to the application. Click on the Send Back to Citizen button.

The system displays a success acknowledgement message stating that the application is sent back to the initiator.

DIGIT Urban 2.9 release has a new following features:

• DIGIT Urban 2.9 Beta Features

• DIGIT as a Service

• Bug Fixes

Introduction

The Trade Category List can be defined as the primary or the 1st level classification “head” for trade(s) defined at a ULB/State Level.

Data Table

Introduction

The structure type is the first level of classification of the premises where the trade has to be established and conducted. This is mostly used as management information in the trade detail.

Data Table

Objective

The trade license 'apply' is the major feature in TL Module. It allows Citizens or Counter Employees to create TL Applications for the current financial year.

Every application is a part of the workflow. Once the user login with TL_CEMP role, then the User will get the option for creating a New TL Application in the TL card as well as in the inbox.

The PT module allows users to transfer the ownership of property.

To transfer the ownership of a property, search and open the property details page. Scroll down the page and click on the Take Action button. Click on the Transfer Property option.

Note the required documents for ownership transfer listed in the Required Documents - Transfer of Ownership screen.

Click on the Transfer Ownership button to proceed.

The Transferor Details page in the Transfer of Ownership form displays the current owner details.

Enter the following details in the Transferee Details

Overview

Users can review the list of applications and their status registered under their mobile numbers in the My Applications tab. Each Application for the initial view displays the Application No, Service Category, Owner Name (Multiple with a comma), status, SLA, and Trade Name with the View Details option. If the status is pending for payment the View Details & Pay button is available that enables the users to look up more details about the application.

Once the user clicks on the View Details or View Details & Pay button, the Application Details Page is displayed with all the necessary information about the application.

A property can be transferred from person to person or from organization to organization or from organization to person or vice versa. The transfer can be due to the property sale, gift, will, succession etc. Whenever such transfers happen the transferee is required to get the ownership change done in the municipal records.

Listed properties are assessed based on the changes to calculate the property tax amount.

To assess properties, find the property for assessment. Open the property details page and scroll down to click on the Take Action button. Click on the Assess Property option.

Select the relevant Financial Year in the pop-up window and then click on the Assess Property button.

The property tax assessment estimate details are displayed on the page. Click on the Assess Property button after reviewing the details.

The assessment is completed successfully. Click on the Proceed to Payment button to pay the property tax.

The Approver signs off the PT application once the information and documents provided by the applicant are found correct.

To approve the application navigate to the Home page. Search for the application you want to verify by entering any of the search parameters. Click on Application No. to open the application. Scroll down the form to review the filled-in details.

Click on the Take Action button available at the bottom of the page. Click on the Approve button.

Enter any additional information in the Comments field in context to the application for the assignee’s knowledge. Click on Choose Files to upload any supporting documents for the application. Click on the Approve button.

The property application is approved.

Overview

The page assumes that the deployment of the central instance will happen in a Kubernetes-based environment independent of whether it’s a cloud-based or a bare metal deployment with a Kubernetes-based orchestrator. This page lists all types of services available in a DIGIT SAAS package and the steps to deploy, implement, and add a new service.

Useful Terms

Namespace/deployment-space - refers to the Kubernetes namespace or the equivalent by establishing access restrictions.

State/Tenant - A state is a separate entity whose applications and data are separated from the rest by namespaces and schemas in the database.

Deployment Setup

1. Backbone Services - The backbone services include Kafka, Redis, and Elastic stack. The number of deployments and the namespace where the services will be deployed are taken care of by the deployment manager itself.

2. State Deployment space - Namespace - In DIGIT SAAS, the private application/deployment space (namespace in K8s & schema in DB) is provided for different tenants (states) when they onboard, the steps to create and provide the same are mentioned in the following document.

3. Central/Shared Services - In DIGIT SAAS, each new tenant is given a separate namespace, but most use some unmodified out-of-box services provided by DIGIT deployed in a shared space known as the central namespace. These sets of services include some of DIGIT’s core services and registries. Among the services mentioned some can never be modified by the state (tenant) actors and some can be modified. In case of any modification, the services should be deployed in their own space.

The above-mentioned services cannot be modified by the state actors and should only be deployed in the central/shared namespace.

• The modifiable registries

  • Registries of any kind are provided by eGov out of the box and are not customized by the state actors. for ex property-registry, TradeLicense-registry etc..,

  • These registries should be deployed in the central namespace to improve usage and reduce cost.

4. State services

The services that are by default deployed and run in the state namespaces whether there are modifications or not. Since they have functionalities that are directly related to the specific requirement of the state.

These services can be divided into multiple categories -

• User Interface - The DIGIT UI by default requires customisation related to the state(tenant), hence will always be deployed in state-specific deployment spaces.

• Core state services (Unmodifiable) - The DIGIT core services will be deployed in state-specific deployment spaces due to their nature of being dependent on the state(tenant) base configs.

  • MDMS

Configuration Setup

The DIGIT applications require different types of config setup, they are as follows the MDMS data, persister, indexer, pdf, report, searcher and internal gateway.

1. MDMS Data

The MDMS data is required for the Master data management service to supply the data required by other modules to perform their basic validation and verify the validity of the data. The prescribed format of the same can be found in the application setup. Since the application is deployed in all the namespaces central and state. Each deployment will need its own GitHub repo.

Central MDMS - central MDMS repo

State 1 MDMS - state1 MDMS repo

2. Persister & Indexer

The persister and indexer configuration for all states should be added in a single GitHub repo in the same branch. Since both applications run in a single place. Each state deployment will have to modify their KAFKA topic names with a prefix of their state schema name.

3. PDF

The pdf configs have to be added in a separate repository since the format of pdfs printed will change with each different tenant.

4. Report & Searcher

The configs of report and searcher have to be added in the same GIT repo and same branches as the persister and indexer. The additional change that needs to be done here is that their URL should be appended with state schema names like the topic names with persister config.

5. Internal Gateway

The internal gateway config should be added to the since the app is deployed in the central namespace.

Development Guide

The development of any service in DIGIT should be based on this development guide.

1. Common Update For All Services

The following library versions are a minimum requirement before any service can be made central instance compatible.

Changes to pom.xml

1. Add Tracer 2.1.1 and above

1. Services-common 1.1.0 and above

1. MDMS-Client 0.0.4 and above

1. ENC-Client 2.04 and above

2. Multi-Schema Services List

The following document helps to make multi-environment applications (Services which will run in the DIGIT namespace but store their data in state-specific namespaces of DB based on tenant-id) central instance compatible. These services include the likes of -

1. Billing-service

2. Collection-service

3. workflow-service

4. egov-apportion-service

Any service that needs to share its data among multiple DB schemas can be added to the above category.

3. Migration Changes For Multi-Schema Services

Certain services in the Central-instance will only be deployed in the central (DIGIT) namespace but their data needs to be stored in different schema belonging to different state namespaces. The migrations of foretold services need to be run in all Required schemas (for instance: namespaces that want to make use of the centrally deployed services). To enable the above functionality the following changes are required.

1. Migrate.sh

This file is needed for building migration docker image is located in the DB folder of resources. eg: . Update the file with the following contents:

1. values.yml

The DB configuration is by default provided in the common file in the helm chart and need not be edited in normal scenarios. Since we are injecting the multiple schema list for app-specific purposes all the DB-migration ENV variables should be overridden in the app-specific values.yml file.

#Values.yml of the specific service before multiple schema changes

#Values.yml of the specific service after multiple schema changes.

- the full updated sample file can be found here

Only the - name: SCHEMA_NAME variable needs to be added and other fields can be copied from the common as it is without any changes. The above file contains an if-else condition with two new variables

The "property-ismultischema-enabled" Boolean value to check if the feature is enabled and "property-schemas" to derive the value from respective environments YAML. This example of two variables should be named differently based on service-name to avoid conflicts.

1. Environments.yml

In the respective environment’s file add the two new variables, one for the if condition and the other field for actual values under the respective service names. Lines 6 and 7 are the sample values provided here.

eg :

4. Code Changes For Multi Schema Services

Any services that could potentially be commonly used by all environments in the central instance (refer to for details).

Application.properties variables to be added.

1. state.level.tenantid.length=2 State-level tenant value will be picked from the full tenant-id separated by the '.' dot. once the tenant-id is separated by a dot the resulting array of sizes given above will be considered state level.

2. is.environment.central.instance=true

   Declares whether the environment in which the service is deployed belongs to a central-instance kind of setup.

3. The both above said variable has to be overridden in the values YAML file of the respective service to pick up the values from the environment.

1. The host of the state-specific services referred by this service should be changed to the internal gateway host for tenant-based(namespace) redirection.

file to refer to the above-said changes

1. If this service allows the search of data without tenant-id then the following validation should be added to all the search APIs belonging to the service. searches without state-level tenant-id (as described by this variable - state.level.tenantid.length) will render the application useless, so the following is mandatory

1. Update the Kafka producer in the service with the following code to enable the service to post to a tenant (namespace) specific topic based on the tenant-id.

1. Replace all the table names in the queries present with the {schema} placeholder

1. Add the following Schema replacer utility method and use the same to replace all queries with the respective schema.

1. Change the persister config to alter the Kafka topic names for the configs belonging to your respective multi-schema service. The Kafka topic name should be appended with the schema name of the respective state schema.

5. Central Instance Enabled Development

Whether a service is going to be deployed in a central instance or not, it should follow and integrate with the central instance util library of common services.

1. Refer to the common update document .

2. Make use of centralInstanceUtil class to perform any tenantId manipulations. Manual manipulation of tenantId is to be avoided for common purposes like getting state-level tenantId, and state-specific Kafka topics. Read the following methods from MultiStateInstanceUtil class found in the common-services package and make use of them as mentioned in the document.

1. New environment variables are to be added mandatorily for environments.

1. The environment should be set to false when the current server is not for multi-state(non-central-instance), disabling and enabling this make the methods in the multiStateUtil class behave as required.

2. The state-level tenant length describes what part of the whole tenantId represents the state part. for eg: in tenantId “in.statea.tenantx”. in.statea represents the state part so the value will be 2.

3. The schema index position points to the substring of the tenantId whose value represents the schema name of the database for the given state.

Citizens or CEs can apply for a new trade licence through the DIGIT web portal or the DIGIT mobile app. To apply for a new trade licence click on the Trade Licence card available in the Citizen Services section of the DIGIT home page.

Counter Employee (CE)

The citizen can approach the Counter Employee (CE) to register new properties, update property details, apply for title transfer or pay property tax.

The CE can

Document Verifier (DV)

DV is responsible for verifying the supporting documents uploaded by the property applicants or the counter-employee on behalf of the applicants.

The DV can

• ​

• ​​​

Field Inspector (FI)

FI is responsible for inspecting and verifying the field details of the property in the application.

The FI can

• ​​

• ​​

• ​​

• ​​​

Approver

The Approver is responsible for the final approval of the PT application.

The Approver can

• ​​

• ​​

Introduction

DIGIT Property Tax facilitates ULBs and citizens to automate the assessment/ re-assessment of property tax for a property and its demand billing and collection. It also enables the ULBs and citizens to process the transfer of title of a property in case of a sale, gift or will and captures the ownership history.

Module Features

The main features of the product are given below.

1. Completely automated assessment and re-assessment of property tax against a property.

   • Online self-assessment process

   • Integrated workflow for ULB staff to perform the check and approve.

Module Ontology

State Level

ULB Level

Module Reports

1. Receipt Register

2. Cancelled Receipt Register

3. Demand Register

Introduction

Trade Type can be further sub-classified into Trade Sub Type depending on the trade ontology existing in the ULBs or States. Hence, Hotels can be further classified into Dhabas in North India or Udupis in South India.

Once the are defined, the next task is to -

• Define Trade Sub Types