Release Notes DIGIT 2.0

New release features, enhancements, and fixes

Release Summary

‌DIGIT 2.0 is a baselined release that has got few functional changes, but more of non-functional standardisation changes.

• Functional: Introducing advance payment feature and Advance collection integration with W/S.

• Non-functional: Upgrading spring boot and tracer version of all the backend services to enhance the range of non-functional benefits like performance, metrics, and security. Also, all digit services/configs are baselined to follow the Semantic Versioning. These would enable the partner eco-system, system Integrators and state teams for easy on-going upgrades and integrations.

New ‌Feature Additions

Feature	Description
Advance Payments	Ability to handle advanced payments - platform and Reference implementation in W&S. Advance Collection integration with W&S
API Contracts	Advance Collection integration with W&S
Infra/Ops Simplification & Enablement	Infra & Service monitoring v1.0.0 (Prometheus, Alertmanager & Grafana) Cluster Resource monitoring Request Traffic monitoring DIGIT Service monitoring All Java-based services SpringBoot upgraded from 1.5.X to 2.2.6 for better security, performance and metrics. Backbone Services migrated to Helm templates to ease deployment on Kubernetes. Introduced Minio as a digit platform service for SDCs to leverage S3 like object storage feature. DIGIT on Spot Instances for AWS users saves 60% of the cloud cost. Configurable SSO with GitHub or Google SSO OAuth for all the Infra apps like Jaeger, Grafana, Kibana. Jenkins CI/CD as a service with the pipelines

Enhancements

Updated Feature	Description
Baseline version upgrades	Bulk persister changes to support bulk persisting for migration in Persister Service. Localization URL params to be changed to request params in Localization service Receipt download link in SMS and email notifications. Rainwater Harvesting attribute in Property Service Filestore service enhancement - Support for SDC and S3 implementation. Maven dependencies upgrade and merging the backend services to the master branch (Upgraded Tracer to 2.0.0, spring boot to 2.2.6, flyway-core to 6.4.3, etc along with code cleanup) for all the services across the services. The Changelog has been added. Baseline versioning of all the services as per the streaming strategy.
UI enhancements	Generalized Client-side PDF generation component and integration with Property, Fire NOC, Trade License, and W&S applications). Generalize acknowledgement screens component MDMS namespace common component and integration with PT and TL modules.
Non-functional enhancements	Versioned Git Tags for all the services Versioned MDMS and Config data.

Upgrade Notes

DIGIT 2.0 is a baselined release - considering simplification and standardization as a theme. It is strongly recommended all-state teams upgrade to leverage benefits.

• All services versioning will follow SemVer 2.0, naming conventions and Git Tagging are improved for better tracing.

• Next release might have a few more enhancements to the services naming conventions and handling MDMS and Configs better.

• Impact: Functionally, the upgrade to DIGIT 2.0 will not impact the existing environments.

Document Resources and Links

UI Technical Documents	Backend Service Documents	Infra/Deployment Documents
PGR Property Tax Trade License Fire NOC Bill Genie MCS Common Pay Advance Payment mSeva 2.0 Water & Sewerage MDMS UI Configurations Required documents dialogue implementation Generation of Acknowledgement PDF How to add dynamic dropdown for MDMS data Common Acknowledgment screens	Advance Payment Kafka Connect for reindex TL Service Renewal Upgradation Filestore service Persister Service Collection Migration v1 to v2 Consumer Code Uniqueness Migration Property Registry Migration Notification SMS service Water Service Sewerage Service Water Calculator Service Sewerage Calculator Service W&S Promotion document	Monitoring & Alerting SSO OAuth (GitHub) for Kibana, Jaeger, etc Grafana dashboard for Infra and Service monitoring Jenkins as a service for CI/CD Minio Helm templates

Upcoming Release Highlights

• Renaming of the backend services with a naming convention in place.

• Config (MDMS, Configs) Baseline versioning.

• Readme.md and Localsetup.md documentations for Core, Business, Municipal, and Other services.