Release Notes

New release features, enhancements, and fixes

Release Summary

DIGIT-Works release v1.0 is a new release that offers new platform features and functions, the details of which are provided below.

Functional changes

• Added detailed estimate capability in estimate service

• Added revision of estimate in estimate service

• Added SOR and Non-SOR in estimate service

• Added revision contract in contract service

• Added measurement service validation while revision estimate and contract

• Added SOR and Rate master using MDMS-v2

Non-functional changes

• Added contact details encryption in organisation service

• Removed Tenant ID splitting from all the services and added modules in master-config.json

• Expense service & calculator to read effectiveFrom and effectiveTo dates from master data and pick rates accordingly

• Updated attendance service query while the changing CBO

New ‌Feature Additions

Feature	Description
Estimate	Ability to add details like length, width, height, etc in an estimate details.
Estimate	Ability to create revision of an estimate.
Contract	Ability to revise contracts
Measurement Service	Create, modify, view & search Measurements in workflow
Measurement Registry	Create, modify, view & search Measurements without workflow

Known Issues

The list below are known issues that need to be addressed as part of the platform roadmap:

• Multiple measurements can not be created at the same time for one contract.

• Integrated error queue implementation for all services along with the necessary measures for addressing issues, is required. In situations of unrecoverable failures, this setup will provide a means to trigger prompt alerts and implement corrective actions.

• Establishing alert mechanisms for critical errors, particularly in the context of billing, is required.

• Managing offline & low connectivity use cases as a best practice.

• Improved logging across services to help troubleshoot.

• The expense service should include the workflow as part of the payload and push it into the Kafka topic for persistence.

• Separate SMS-related localization from all services and migrate it to a dedicated service.

• Performance testing and benchmarking of services.

• Security audit.

• Multiple mdms-v2 calls in services, because mdms-v2 was returning only one master's response.

• Code refactoring of works-services like

  • Remove unused models

  • Change package names

  • Remove duplicate validation logic

Document Resources and Links

Technical Documents

Doc links
High Level Design
Low Level Design

Service Documents

Doc Links
Estimate
Contract
Measurement