Release Notes

v2.10 release version

Release Summary (CCRS)

CCRS v2.10 is now updated to work with the DIGIT Platform v2.9 LTS, delivering improved modularisation, enhanced security, and streamlined configurations for municipal governance services.

Key Highlights

This release focuses on:

Installation & ease of setup:

• Packaging the CCRS product (including all components required for the functioning of the product) as a 1-click installer on AWS using GitHub Workflows for ease of development. Production setup will still need to be followed using traditional methods.

• The 1-click installer adds all requisite base master data for the CCRS product (and the core platform) to work out of the box. No extra setup is needed to experience the product with the default data.

• Upgraded all Helm charts to support Kubernetes version upgrade from 1.20 to 1.30.

UI improvements:

• Unified UI Design Across Modules – Provides a seamless and intuitive user interface.

• Decoupled Component Architecture – Improves reusability and simplifies micro-frontend management.

• Usage of the Inbox V2 component in the UI for faster, efficient Inbox search.

• FormComposerV2 for All PGR Forms – Ensures consistent, modular, and maintainable form structure.

• Config-Driven UI Rendering and Behaviour – Enables rapid customisation without direct code changes.

• Responsive Layouts – Optimised for desktop, mobile, and tablet screens.

Backend service improvements & fixes:

• Robust Error Handling and Exception Management – Supports better debugging, user feedback, and stability.

• Inbox-v2 service has been introduced as a component – offers advanced filtering, faster performance, and extensibility.

• Boundary service validation is added in the backend service (pgr-service) while creating or updating complaints to ensure the boundary code passed in from the UI matches an existing one configured in the system.

New Components:

• Inbox v2 service with integration to ElasticSearch for search

• Workbench Integration – Provides master data management (MDMS) and localisation data loading for module configurations. Note that workflow configuration will still need to be done via API.

• Default data handler - Loads the default master data for the platform + CCRS modules to work out of the box. This service is called as part of the installation workflow.

Refer to the architecture section to see the full list of components used for CCRS. Regular updates, including both minor tweaks and major enhancements, will be released as needed to ensure ongoing performance and reliability.

Known Issues

• Localization

  • Hindi localizations are not available on some Citizen and Employee page labels.

• Notifications

  • Citizen in-app notifications are not working.

• UI Issues

  • Privacy policy text is missing.

  • Login page not scaled properly on 1366×768 resolution.

  • Employees are able to log in without selecting the Privacy Policy checkbox.

• Complaint Handling

  • Complaint reopen time limit is hardcoded and only applies to rejected complaints.

  • While assigning a complaint, the dropdown shows additional/unexpected employees.

  • SLA resets to 0 after a complaint is reassigned/updated.

  • Employee UI saves "Complaint Sub-Type" even after the user changes the selected "Complaint Type".

• Workbench

  • UI crashes when user clicks on Show JSON.

• Employee Data & Inbox

  • Total and active employee count, along with active status, does not update automatically.

  • Employee Inbox sorting options not working.

  • Status filter shows only one option.