Find the service build updates below:
Category (Tag)
Services
Docker Artifact ID
Remarks
Facility
egovio/facility-db:v1.1.2-00a7accbda-14
Changed
Household
egovio/household-db:v1.1.3-00a7accbda-12
Changed
Individual
egovio/individual-db:v1.1.5-00a7accbda-6
Changed
Project
egovio/project-db:v1.1.4-00a7accbda-5
Changed
Product
egovio/product-db:v1.1.0-00a7accbda-31
Not Changed
Referral Management
egovio/referralmanagement-db:v1.0.2-00a7accbda-14
Changed
Stock
egovio/stock-db:v1.1.3-00a7accbda-18
Changed
Transformer
egovio/transformer:v1.1.2-00a7accbda-19
Changed
HRMS
egovio/egov-hrms-db:v1.2.7-00a7accbda-19
Changed
Pgr
egovio/pgr-services-db:v1.1.7-00a7accbda-19
Changed
Service-request
egovio/service-request-db:v1.0.0-00a7accbda-16
Changed
Health-attendance
egovio/health-attendance-db:v1.0.2-30824c427-11
Changed
Digit-Ui
egovio/digit-ui:health-dashboard-product-3cb11409c9-636
Changed
Dashboard
egovio/dss-dashboard:v1.8.0-0d70d60e63-53
Unchanged
egovio/dashboard-analytics:master-impel-f705ac483a-48
Unchnaged
egovio/dashboard-ingest:v1.1.4-72f8a8f87b-10
Unchnaged
WORKBENCH-1.0
egovio/project-factory:v0.1.0-6caaf2700e-6
Changed
egovio/workbench-ui:v0.1.0-6caaf2700e-16
Changed
Checklist
Yes/No/Partially
Reference Link/ETA
Owner
Reviewer
Remarks
The development is complete for all the features that are part of the release.
Yes
Test cases are documented by the QA team, reviewed by product owners, and test results are updated in the test cases sheet.
Yes
The incremental demo of the features showcased during the sprint showcase and feedback is incorporated. If possible, list out the JIRA tickets for feedback.
Yes
12-June-24
UI/UX audit review is completed along with feedback incorporation for any changes in UI/UX.
Yes
30-May-24
Mail has been communicated to Andrew Jones for UI/UX audit
QA sign-off is completed by the QA team and communicated to product owners. All the tickets’ QA sign-off status is updated in JIRA.
Yes
Lata
UI, and API technical documents are updated for the release along with the configuration documents.
Yes
UAT promotion and regression testing from the QA team is completed. The QA team has shared the UAT regression test cases with the product owners.
Yes
Lata
The API backward compatibility testing is completed.
Yes
No breaking changes are made.
The communication is shared with product owners for the completion of UAT promotion and regression by the QA team. The product owners have to give a product sign-off within one week of this communication.
Yes
4-June 24
As part of admin console product owner sign-off has been completed
The UAT product sign-off communication is received from product owners along with the release notes and user guides (if applicable).
Yes
20-June-24
As part of admin console product owner sign-off has been completed
The GIT tags and releases are created for the code changes for the release.
Yes
Verify whether the release notes are updated.
Yes
Link
Verify whether all the UAT builds are updated along with the GIT tag details.
Yes
Link
Lata
Verify whether all MDMS, configurations, infra-ops configurations are updated.
Yes
Verify whether all docs will be published to http://health.digit.org by the Technical Writer as part of the release.
Partially
Verify whether all test cases are up-to-date and updated along with the necessary permissions to view the test cases sheet. The test cases sheet is verified by the test lead.
Yes
Verify whether the UAT credentials' sheet is updated with the details of new users and roles, if any.
Yes
Link
Verify whether all the localisation data was added in UAT, and updated in the release kits.
Yes
No functional changes were made
Verify whether the product release notes and user guides are updated and published.
No
No product functional changes were made
The demo of the released features is done by the product team as part of a sprint/release showcase.
Yes
20-June-24
Demo has been give as a part of the HCM Console release
Technical and product workshops/demos are conducted by the engineering and product teams respectively to the implementation team (implementation handover).
Yes
Architect sign-off and technical quality report.
Yes
Verify Bug Bash has been completed
Yes
31-May-24
Gate 2
21-Jun-24
The internal release communication along with all the release artefacts are shared by the engineering/ product teams.
The HCM v1.4 release required migration of the boundary and MDMS data if the server is not a fresh deployment but an existing v1.3 deployment
If the current environment has boundary data in MDMS v1 please follow the steps mention in the document below to migrate to boundary v2. Boundary migration from v1 to v2 LTS
If the environment is new the one click installer and data loader will by default load the data required.
If the Environment has pre existing data then the MDMS v2 migration tool should be run using the below document:
MDMS migration from v1 to V2 LTS
Following is the code link:
HCM v1.4 is a tech release with only server upgrade to DIGIT 2.9 LTS with some additional cleanup.
Digit core LTS integration
MDMS v2 integration
Boundary V2 integration
HCM Admin Console
DIGIT HCM app modules as package extractions
Missing unique validation on client reference ID added in all offline supported services.
Project types have been moved to project additional details from MDMS.
UI modules extracted as packages
Registration and delivery
Referral reconciliation
Inventory management
Attendance management
DIGIT scanner
DIGIT showcase
All core services have been upgraded to core 2.9 LTS barring the services modified for offline use cases.
All data models have been restructured with an "is a relationship" from base eGov model and the base eGov search model.
All data models have been moved to the health common library and duplicates removed.
Removed reflection until code in the health common library that is Incompatible with Java 9 and above.
All the master data for the DIGIT HCM app are separated by functionality from one single master.
Flyway version upgrade to 9.22.3 for LTS upgrade.
Boundary v2 Integration