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.

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.

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

Overview

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

Release Highlights

Daily collection report

Application status report

Trade license registry

Trade license renewal pending report

Release Features

Trade license daily collection report

Trade license application status report

Trade license registry

Trade license renewal pending report

Known Issues

Upcoming Release Features

None

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

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.

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

   • List of user manuals, help videos etc (Also in local language)

3. Link to access service via WhatsApp

4. Helpline Numbers

5. Address of Service Centres

   • Link to navigate to google maps

6. Static data

   • Ex. Days to process applications/ Amount to pay while applying etc

7. Dynamic Data

   • Number of citizens applied for service in last n months/ Amount collected etc

Known Issues/ Upcoming Features

https://digit-discuss.atlassian.net/browse/UM-5628 https://digit-discuss.atlassian.net/browse/UM-5721 https://digit-discuss.atlassian.net/browse/UM-5640 https://digit-discuss.atlassian.net/browse/UM-5725

Related Doc Links

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

Release Summary

Local Governance 2.9 release includes the following changes:

• Citizen Consent Form

• Citizen Feedback Rating

• KPI List (National Dashboard)

  • Citizen Feedback Score

  • Citizen Service Delivery Index

  • Aggregated SLA

  • Pendancy

• mCollect (demand-based revenue collection) Pdf -QR code bug fix/alignment issues

• Residential Construction Permit System - bug fixes

• Local Business License Issuing System - bug fixes

• Property Tax System - bug fixes

• Finance - bug fix

• Central Instance-related changes for modules - Property Tax, Trade License, Citizen Complaint Resolution System, Residential Construction Permit System, Water and Sewerage Connections, Fire Safety Certification, Birth and Death, mCollect, Reports and Inbox.

New ‌Feature Additions

Enhancements

‌Document Resources & Links

Overview

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

Release Highlights

About page for the dashboard is added which helps users to understand the purpose, how data is secure and from where the data is being pushed.

And 3 new KPIs were added for administrative purposes.

Release Features

About page

FAQ

3 KPIS - Non-tax revenue collected, Non-tax revenue contribution % and Average PT collected.

Related Doc Links

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.

1. Properties amalgamation

2. Property bifurcation

3. Capital value system

4. Property mutation bug fixes

Release Features

None

Known Issues

Bug

UM-5322: PT: Mutation flow: In Acknowledgement Form only one Transferor Details are present.SIGNED OFF

Upcoming Release Features

None

Reference Doc Links

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

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.

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

   • Questions

     • Short Answer

     • Paragraph

     • Single Answer

     • Multiple choice questions

     • Date

     • Time

4. Survey Results

   • Aggregated view of all survey results in specific charts for each question type

   • Download the excel report with the survey results

5. Modify surveys

   • Survey questions

   • Extend the Survey date and 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)

https://digit-discuss.atlassian.net/browse/UM-5697 https://digit-discuss.atlassian.net/browse/UM-5700

Related Doc Links

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

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.

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.

To view property details, follow the steps outlined in the Search Property 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.

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

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.

Using Property Tax Module

This section guides you through the details of using the PT module for each role. Click on the relevant role below to learn more about how to use the PT system.

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 -

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.

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.

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.

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.

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.

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.

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.

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 Service-request module

2. Add the new persister file: service-request-persister

3. Add the Helm chart

4. Configure the build

- name: "builds/digit-dev/core-services/service-request"
    build:
      - work-dir: "core-services/service-request"
        image-name: "service-request"
        dockerfile: "build/maven/Dockerfile"
      - work-dir: "core-services/service-request/src/main/resources/db"
        image-name: "service-request-db"

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

AccessControl Actions Test

AccessControl Role Actions

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 Citizen Feedback service.

4. Create the Citizen Feedback Service definitions (as mentioned in the above Citizen Feedback Service document) for modules and flows as per requirement before using it on the UI.

New KPIs

1. Refer to KPIs: Pendancy, Citizen Feedback and Pt-SLA changes 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.

UI build preparation 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 file

Documentation: a. Refer to Citizen Consent Form 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: https://github.com/egovernments/egov-mdms-data/blob/QA/data/pb/common-masters/RatingAndFeedback.json

{
  "tenantId": "pb",
  "moduleName": "common-masters",
  "RatingAndFeedback": [
    {
      "type": "isCitizenRatingEnabled",
      "value": true
    },
    {
      "type": "headerByRating",
      "value": [
        {
          "minvalue": 1,
          "maxvalue": 3,
          "code": "CS_WHAT_WENT_WRONG"
        },
        {
          "minvalue": 4,
          "maxvalue": 5,
          "code": "CS_WHAT_WENT_GOOD"
        }
      ]
    },
    {
      "type": "enabledScreensList",
      "value": [
        {
          "module": "PT",
          "bussinessService": "PT_CREATE",
          "screenfrom": "pt/property/new-application/acknowledgement",
          "cardHeader": "PT_RATE_HELP_TEXT_CREATE",
          "cardText": "PT_RATE_CARD_TEXT_CREATE"
        },
        {
          "module": "PT",
          "bussinessService": "PT_MUTATION",
          "screenfrom": "pt/property/property-mutation/acknowledgement",
          "cardHeader": "PT_RATE_HELP_TEXT_MUTATE",
          "cardText": "PT_RATE_CARD_TEXT_MUTATE"
        },
        {
          "module": "PT",
          "bussinessService": "PT_UPDATE",
          "screenfrom": "pt/property/edit-application/acknowledgement",
          "cardHeader": "PT_RATE_HELP_TEXT_UPDATE",
          "cardText": "PT_RATE_CARD_TEXT_UPDATE"
        },
        {
          "module": "PT",
          "bussinessService": "PT",
          "screenfrom": "digit-ui/citizen/payment/success",
          "cardHeader": "PT_RATE_HELP_TEXT_PAY",
          "cardText": "PT_RATE_CARD_TEXT_PAY"
        }
      ]
    }
  ]
}

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: Rating.js.

Documentation

a. Refer to Citizen Feedback Documentation for more details.

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

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.

5. Download Trade License, Payment & Acknowledgement Receipts online.

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

1. Trade Category

2. Trade Type

3. Trade Sub Type

4. Trade License Documents Attachment

5. Structure Type

6. Structure Subtype

ULB Level

1. Trade License Fee

Module Reports

1. Receipt Register

2. Application Status

3. Cancelled Receipt Register

4. ULBwise Collection Report

5. ULBwise Application Status

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 New Property Registration to submit the changes.

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

• Open link for stakeholder registration flow

• Daily collection report

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

​https://digit-discuss.atlassian.net/browse/UM-5599

Upcoming Release Features

None

Reference Doc Links

Overview

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

Release Highlights

Birth count report

Death count report

Birth and death certificate payment records

Release Features

Birth count report

Death count report

Birth and death certificate payment report

Known Issues

https://digit-discuss.atlassian.net/browse/UM-5256

Upcoming Release Features

None

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.

Goals

The urban mission offers digital governance solutions that encapsulate the core platform principles. The apps provide

• Secure & reliable governance tools

• Simple reusable modules for effective integration

• Scalable & standardized solutions

• Open APIs to promote interoperability

• Multiple channel support

• Configurable building blocks that support customization at each stage

Approach

The local governance focuses on inclusion and is designed to enhance both platform openness and choice for citizens. The platform uses open APIs and standards, creating a powerful framework to drive convergence across the multiple systems currently in use and to lower the barrier to entry for locally developed solutions.

Keeping in mind that most Indians use the internet through their phones, we follow and advocate a “mobile-first” approach, while supporting multi-channel access to accommodate diverse needs and preferences.

• Open Source - The local governance stack is open source and has been built using the best-in-class open-source technology stacks powering the most advanced companies in the world. The solution can provide the lowest total cost of ownership and helps ensure that governments retain strategic control of their systems and data.

• Mobile-Enabled - The local governance solution design follows a mobile-first approach, with robust mobile applications enabling citizens to access government services through their phones easily. Government officials and field workers are also empowered with mobile applications that enable them to deliver 24×7 governance with ease.

• Real-time Dashboards - The real-time dashboards provide governments with actionable insights on demand. Administrators and department heads are empowered with verified data that enables them to manage their work and budgets better. Field-level employee reports enable effective performance management and ensure efficient usage of government resources.

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.

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 -

• ​Register New Property​

• Search & Pay​

• ​My Bills

• My Payments​

• ​My Properties

• ​My Applications

• Update Property

• ​​Transfer Property Ownership​

• ​Update Mobile Number

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.

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.

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.

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.

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.

Result Table

Result Table uses the Table react component and the result from API is adapted to the table config using a custom hook inside the common parent wrapper and passing the response to individual components.

Search License has a fixed param where the status of the application is “APPROVED”, other than differences in table config

APIs

The API end point for searching trade licenses is {env}/tl-services/v1/_search

API CURL -

curl 'https://qa.digit.org/tl-services/v1/_search?tenantId=pb.amritsar&fromDate=1625077800000&toDate=1627410599000&limit=10&sortBy=commencementDate&sortOrder=DESC&status=APPROVED&_=1627375567840' \
  -H 'authority: qa.digit.org' \
  -H 'sec-ch-ua: " Not;A Brand";v="99", "Google Chrome";v="91", "Chromium";v="91"' \
  -H 'accept: application/json, text/plain, */*' \
  -H 'dnt: 1' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36' \
  -H 'content-type: application/json;charset=UTF-8' \
  -H 'origin: https://qa.digit.org' \
  -H 'sec-fetch-site: same-origin' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-dest: empty' \
  -H 'referer: https://qa.digit.org/digit-ui/employee/tl/search/license' \
  -H 'accept-language: en-US,en;q=0.9,hi;q=0.8' \
  --data-raw '{"RequestInfo":{"apiId":"Rainmaker","authToken":"18158d2b-0a50-4a60-baa3-a83c157e7aad"}}' \
  --compressed

DIGIT Urban 2.9 release has a new following features:

• DIGIT Urban 2.9 Beta Features

• DIGIT as a Service

• Bug Fixes

NUDM Roll Out

The NUDM Team has shared the following requirements for upgrading UPYOG with the Central Instance:

*Conditions for Upgrading UPYOG with Central Instance

• Role & Access Management at Cluster Level so that each State SI can do its scope of work

• Role & Access Management at Logs Level so that each State SI can do its scope of work

• Role & Access Management at Elastic Search & Kibana Level so that each State SI can do its scope of work

• Enhancement & verification of Product default Kafka with more nodes, partitions, etc so that it sustains and performs for National Level traffic

• Enhancement & verification of Product default ElasticSearch with more nodes, shards, etc so that it sustains and performs for National Level traffic

• Availability of all States data in its DB schemas and the same should apply with ElasticSearch

• Other enhancements so that the State Infra & DevOps team can manage their resources independently.

Adoption Metrics

Success Metrics

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.

Key Features

Section Overview

This section contains all docs and information required to understand the property tax module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the PT module.

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.

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.

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.

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

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.

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.

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.

2. Transfer of title (Mutation)

   • Online application

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

3. Generating the demand

4. Collection of property tax through various modes (Cash, Cheque, POS (Credit/ Debit Card), NEFT/RTGS, Online - Through Payment Gateway)

5. Auto calculation of rebate, interest and penalty.

Module Ontology

State Level

1. Property Type

2. Property Sub Type

3. Property Usage Major

4. Property Usage Minor

5. Property Usage Sub Minor

6. Property Usage Detail

7. Construction Type

8. Ownership Category

9. Ownership Sub Category

10. Owner’s Special Category

11. Special Category Documents

12. Road Type

ULB Level

1. Unit Rate

2. Tax Rate

3. Interest Rate

4. Penalty Rate

5. Rebate Rate

6. Mutation Fee

Module Reports

1. Receipt Register

2. Cancelled Receipt Register

3. Demand Register

MDMS Changes

Config Changes

DevOps Changes

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.

Click on the link below to download the trade licence brochure.

Key Features

Section Overview

This section contains all docs and information required to understand the Business Licensing module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customising, and using the business license issuing module.

• Functional Specifications

• Local Business License Issuing User Manual

• Master Data Configuration Templates

• Local Business License Issuing System Service Configuration

• Implementation Handbook

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: digit-ui-internals/ApplicationDetails.js at main · egovernments/digit-ui-internals

Trade Details

Timeline View

It is common for all modules, find the path here: digit-ui-internals/ApplicationDetailsContent.js at main · egovernments/digit-ui-internals

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:

https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pages/citizen/EditTrade/index.js

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:

digit-ui-internals/index.js at main · egovernments/digit-ui-internals

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 digit-ui-internals/index.js at main · egovernments/digit-ui-internals

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.

Trade License - Apply Flow

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.

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.

The user can download the Application Acknowledgement Form (status - pending for payment ) or TL Certificate or the payment receipt using the Download Link button available at the top right corner of the page.

If the status is Pending for Payment for the application or Action required by a citizen (discussed elaborately here), a button will be visible to pay or edit at the end of the page respectively. On clicking on the Make Payment button it will redirect to the common pay screen through which the user can make the payment.

Timeline Component - timeline component is present at the end of the application details which tells about the current status and history of the application being initiated, Applied, Pending for Document Verification, Pending for Field Inspection, Pending approval, Pending payment, Approved etc.

Technical Implementation Details

The link for the Applications and Application Details main code is given below, it can be used to understand the working of the code, Below is the folder link.

digit-ui-internals/packages/modules/tl/src/pages/citizen/Applications at main · egovernments/digit-ui-internals

The template for My Application List is present under https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pages/citizen/Applications/Application.js and Application Details page is present inside - https://github.com/egovernments/digit-ui-internals/blob/main/packages/modules/tl/src/pages/citizen/Applications/ApplicationDetails.js .

All the Application lists are retrieved by calling the search API "/tl-services/v1/_search". If the view is set as “bills”, all the application is loaded using the hook useFetchBill which calls the /billing-service/bill/v2/_fetchbill API. SLA value in the Application List Screen is calculated from the data received from workflow API : /egov-workflow-v2/egov-wf/process/_search

Following is the hook used for the trade search API.

const { isLoading, isError, data, error, ...rest } = view === "bills" ? Digit.Hooks.tl.useFetchBill(
    {
      params: { businessService: "TL", tenantId, mobileNumber },
      config: { enabled: view === "bills" }
    }
  ) : Digit.Hooks.tl.useTLSearchApplication({}, {
    enabled: view !== "bills"
  });

To get the Application details in key-value format, in order to make it more compatible, the following hook is being used, which is a common service to be used across modules.

 const { isLoading, isError, error, data: application, error: errorApplication } = Digit.Hooks.tl.useTLApplicationDetails({
    tenantId: tenantId,
    applicationNumber: id,
  });

MDMS

No MDMS data is being used here, all the data is being loaded from Search API/Fetch Bill API.

Localization

For My Applications also the localization keys are added in the ‘rainmaker-tl’ locale module same as other parts of the TL module. Change, update or add any new localization key is done in the same locale module only.

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

• Provide Ownership Details - select the ownership type

• Enter owner Name - the name of the transferee

• Select the Gender of the transferee

• Enter the Mobile No. of the transferee

• Enter the Guardian’s Name of the transferee

• Enter a Relationship with Guardian of the transferee

• Enter the Email address of the transferee

• Select the applicable Special Applicant Category

• Enter the Correspondence Address of the transferee

Select the Yes or No option to answer the question Is Mutation Pending in Court? If yes, enter the Details of Court Case.

Select the Yes or No option to answer the question Is Property or part of property under state/central government acquisition? If yes, enter the Detail of government acquisition.

On the Registration Details page provide the following questions:

• Reason for Property Transfer

• Property Market Value

• Registration Document Value

• Registration Document Issue Date

• Remarks

Click on the Next Step button to proceed to the Document Upload section.

Select the type of document that will be uploaded for Address Proof, Identity Proof, and Registration Proof.

Click on the Next Step button to move to the Summary section. Click on the Submit button once all details are reviewed. The system displays the application success message. Click on the Download Acknowledgement button to download a PDF version of the acknowledgement.

Click on the Go back to home page button to navigate back to the home page.

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.

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

The table above contains sample data.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document for more details on data type, size, and definitions.

3. Contact the person who shared this template with you to discuss and clear your doubts.

4. Enter the relevant structure types.

5. Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per specifications. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

A separate entity-specific checklist is not needed for this entity data template.

Attachments

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.

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

• ​​

• ​​

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.

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

The table above contains sample Trade Category data.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.

3. Enter a unique Trade Category Code for each trade head.

4. Enter the Trade Category Name. Some trade categories are already defined in the master. Add new categories as required.

5. Enter the Trade Category Name (Local Language).

Checklist

The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

This checklist covers the activities which are specific to the entity.

Attachments

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.

File path: digit-ui-internals/TLCard.js at main · egovernments/digit-ui-internals and digit-ui-internals/DesktopInbox.js at main · egovernments/digit-ui-internals

Clicking on New Application navigates to the New Trade License Application screen.

Route: mSeva

File Path: digit-ui-internals/index.js at main · egovernments/digit-ui-internals

Technical Implementation Details

Initial MDMS call is being made on page load like old UI.

MDMS Data

Structure Type and Sub Structure Type field data is fetched from egov-mdms-data/StructureType.json at master · egovernments/egov-mdms-data

Trade Category, Trade Type, Trade Sub Type field data is fetched from egov-mdms-data/TradeType.json at master · egovernments/egov-mdms-data

Mohalla Data - egov-mdms-data/boundary-data.json at master · egovernments/egov-mdms-data (For Amritsar)

Accessories - egov-mdms-data/AccessoriesCategory.json at master · egovernments/egov-mdms-data

Type of Ownership and Type of Sub ownership - egov-mdms-data/OwnerShipCategory.json at master · egovernments/egov-mdms-data egov-mdms-data/OwnerType.json at master · egovernments/egov-mdms-data

documents: egov-mdms-data/documentObj.json at master · egovernments/egov-mdms-data

Data fetch, load and render

• Clicking on Submit button, tl-services/v1/_create api is called and create the application, after getting success response, we are calling update API tl-services/v1/_update.

• On loading the page, /tl-calculator/billingslab/_search api is called for showing the licence type (File Path: digit-ui-internals/TLTradeDetailsEmployee.js at main · egovernments/digit-ui-internals ) and accessories options (File Path: digit-ui-internals/TLAccessoriesEmployee.js at main · egovernments/digit-ui-internals ).

Acknowledgement Screen

After the success of creating and updating calls will route to the acknowledgement screen.

File Path: digit-ui-internals/getTLAcknowledgementData.js at main · egovernments/digit-ui-internals

Role Action Mapping

Introduction

Once the Trade Ontology is defined, the next step is to allocate the license fee associated with the Trades.

Dependent on the Trade Classification Level (/ ), the fee allocated might be the same across the Sate or could vary from ULB to ULB. There could be a distinct fee(s) for two different types of applications (new and renewal).

Following are the key tasks to be executed :

• Allocate the License Fee according to Trade Classification Level (Types/Subtypes).

• Map the License fee with the respective Trade Classification Level.

Data Table

The table above contains sample data.

Procedure

How to fill data

1. Download the data template attached to this page.

2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

3. Identify the “” that exists at a ULB/ State level.

4. Collect the above information and feed it below the “Trade Sub Type Name” column accordingly. The Description of Trade Sub Type Name must be provided as per the language specified in the respective column.

5. Add the “Trade Sub Type Code” respectively against the identified trade type(s).

6. Fill in the New License Fee & New Renewal Fee accordingly. The New License Fee & Renewal Fee can be the same as well as distinct, depending on the by-laws/ mandate followed by the State/ULB.

7. Fill in the fields related to Units of Measurement (UOM Unit, From/To) for the available trades only.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

This checklist covers the activities which are specific to the entity.

Attachments

Introduction

Once the are defined, the next task is to -

• Define Trade Types

• Map Trade Category to listed Trade Types

The Trade Type can be defined as the next (2nd) level classification of Trade. There can be multiple trade types and the list may vary from one State/ULB to another.

Data Table

The table above contains sample Trade Type data.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to learn more about the template sheet, data type, size, and definitions.

3. Select the relevant Trade Category Code from the available drop-down list of Trade Category. This will map the listed Trade Type to the corresponding Trade Category.

4. Enter a unique Trade Type Code to identify the type of trade.

5. Enter a Trade Type Name (In English).

6. Enter the Trade Type Name (In Local Language).

Checklist

The checklist contains a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

This checklist covers the activities which are specific to the entity.

Attachments

All the fields in this flow are the same as the New TL Application. The difference here is that max fields are having pre-populated data (On Loading the page, search is made for that particular application).

Will get the Renew Trade License option, when the application is in an approved state and the same financial year application is not present in the workflow.

File path:

When we click on the Renew Trade License application, it will route to Renew screen

File Path:

File Path:

Direct Renewal: There is no change in any fields and directly clicks on submitting an application, an update API call is made for the respective application with respective to Direct Renewal (applicationType: RENEWAL, workflowCode: DIRECTRENEWAL, )and it will go into direct renewal flow.

Edit Renewal: If there is any change in any fields and clicks on submitting an application, an update API call is made with respect to edit renewal (applicationType: RENEWAL,workflowCode: EDITRENEWAL )and update the application and it will go into the edit renewal flow.

Units, Accessories, Owners and documents details in case of Edit/Renewal flow

1. Employee can edit units in both cases, employee can add and delete multiple units, please find the file below reg all use cases:

2. Employee cannot edit accessories in both cases, the employee can not add and delete multiple units and all fields are in disable state, please find the file below reg all use cases:

3. Employee can edit in both cases, expect ownership details, ownership details field is in disable state in both cases. please find the file below reg all use cases:

4. Employee can edit the documents in both cases, please find the file below reg all use cases:

Acknowledgement Screen

After a successful update call, the user is routed to the acknowledgement screen.

File Path:

EDIT Flow: It is also the same as renewal flow only, but we are passing the action action: RESUBMIT on the update call with all the changes.

Application/ Trade Details:

TL Create New Application:

Role Action Mapping