With the iFIX v2.4-alpha update, some of the DIGIT core services also need to be deployed. The builds of the same are also listed below. These have been picked from DIGIT-v2.8.
| Category | Services | Docker Artefact ID | Remarks |
|---|---|---|---|
Here are the test cases for Program Service, Digit Exchange, Mukta-ifix-adapter.
v2.4-alpha release details
IFIX 2.4 is a new release that offers new platform features and functions, the details of which are provided below.
DIGIT Exchange - This service offers the capability to exchange data while ensuring it is signed.
Program Service - This facilitates the creation of programs, sanctions, allocations, and disbursements.
MUKTA iFIX Adapter - This transforms data from Mukta payment to program disbursement.
IFMS Adapter - Integration to program disburse and on-disburse APIs.
NA
| Features | Description |
|---|
If Kafka malfunctions, data will be directed to the error queue, necessitating manual processing until an error queue handler is developed.
If the disbursement status is set to be SUCCESSFUL then it should not be changed to INITIATED again for the disbursement id.
As per IFMS guidelines, if a transaction fails, the amount is deducted and if a revised payment is not generated within 90 days, the amount should be deducted again.
Establishing alert mechanisms for critical errors, particularly in the context of billing, is required.
Performance testing and benchmarking of services.
This migration is mukta-specific, it will not be part of our master code.
After installation of all required services, port-forward the program service and create programs for each ULB. Sample curl is added bellow.
Configure alll program codes that you created for each ULB to the MDMS.
IFMS adapter data migration for mukta-adapter ad program service
Update environment variables according to the environment.
Build the python migration script and deploy it in the environment.
Port forward the service and call the API to start the migration.
Use specific branch for iFix migration.
IFIX Domain Services
Digit Exchange
This is new service for exchange data
Program Service
This is new service for implemented with iFix specs.
Adapters
ifms-adapter
Connects iFix to IFMS system.
iFix-mukta-adapter
Transform works plateform bills to disbursement
Core Services
egov-mdms-service
egov-mdms-service:v1.3.2-44558a0-3
egov-indexer
egov-indexer:v1.1.7-f52184e6ba-25
egov-idgen
egov-idgen:v1.2.3-72f8a8f87b-7
SSU Details
MDMS Service
Head Of Accounts
MDMS Service
ID Gen
Program Service
Exchange
Program Service
Exchange indexer
Digit Exchange
Exchange devops
Digit Exchange
ifms-pi-indexer
Mukta-ifix-Adapter
mukta-ifix-adapter-persister
Mukta-ifix-Adapter
Charts
Program Service
Environment
Program Service
Secrets
Program Service
Adapter Helm
Mukta-ifix-Adapter
Adapter Environment
Mukta-ifix-Adapter
Adapter Encryption
Mukta-ifix-Adapter
DIGIT Exchange | This service offers the capability to exchange data while ensuring it is signed. |
Program | This facilitates the creation of programs, sanctions, allocations, and disbursements. |
MUKTA iFIX Adapter | This transforms data from Mukta payment to program disbursement. |
IFMS Adapter | Integration to program disburse and on-disburse APIs. |
| # | Checklist | Sign-off Status | Reference link | Owner | Reviewer | Remarks |
|---|
1 | Development is completed for all the features that are part of the release. | Yes | Shailesh | Satish N |
2 | Test cases are documented by the QA team, reviewed by the product owners and test results are updated in the test cases sheet. | Yes | Anuraj | Shailesh | Test cases are reviewd by product owners. |
3 | The incremental demo of the features showcased during the sprint showcase and feedback incorporated. If possible list out the JIRA tickets for feedback. | Yes | Anuraj | Satish N | Internal demo was done on 14th March 2024. |
4 | UI/UX Audit review by UX Architect is completed along with feedback incorporation for any changes in UI/UX. | NA |
5 | Incremental demos to the product owners are completed as part of the sprint and feedbacks are incorporated. | Yes | Anuraj | Satish N | Internal demo was done on 14th March 2024. |
6 | QA signoff is completed by the QA team and communicated to the product owners. All the tickets QA signoff status is updated in the JIRA. | Yes | Anuraj | Satish N |
7 | UAT promotion and regression testing from the QA team are complete. The QA team has shared the UAT regression test cases with the product owners. | No | Anuraj | Satish N |
8 | The API backward compatibility testing is completed. | No | Anuraj | These are new services, so this is not applicable. |
9 | The communication is shared with the product owners for the completion of UAT promotion and regression by the QA team. The product owners have to give a Product signoff within one week of this communication. | No | Anuraj | Satish N | QA Sign off given on March 21, 2024 |
10 | UAT Product Signoff communication is received from the Product owners along with the release notes and User guides (if applicable). | Yes | Satish N | Prashanth |
11 | The GIT tags and releases are created for the code changes for the release. | Yes | Shailesh | Pritish |
12 | Verify whether the Release notes are updated | Yes | Shailesh | Pritish |
13 | Verify whether all UAT Builds are updated along with the GIT tag details. | Yes | Anuraj, Shailesh | Pritish |
14 | Verify whether all MDMS, Configs, InfraOps configs updated. | Yes | Anuraj | Shailesh |
15 | Yes | Satish N, Shailesh, Pritish, Anuraj, Sameer, Arindam, Anjoo | Anjoo |
16 | Verify whether all test cases are up to date and updated along with necessary permissions to view the test cases sheet. The test cases sheet is verified by the Product owner. | Yes | Anuraj | Shailesh |
17 | Verify whether the UAT credentials sheet is updated with the details of new Users and Roles if any | No | It will be internally shared |
18 | Verify whether all the localization data was added in UAT including Hindi and updated in Release Kits. | No |
19 | Verify whether the product release notes and user guides are updated and published | Yes | Satish N | Prashanth | User Manual - Not Required |
20 | The Demo of released features is done by the product team as part of the Sprint/Release Showcase. | In-Progress | Satish N | Becuse of technical issue not completed showcase. |
21 | Technical and Product workshops/demos are conducted by the Engineering and Product team to the implementation team (Impel handover)
| Yes | Shailesh | Arindam | Implementation handover done on - 13th March 2024. |
22 | Architect SignOff and Technical Quality Report | Yes | Shailesh | Manish | Issues are documented in Known Issues. Also documenting this in JIRA for tech debt fixes. |
23 | Success Metrics and Product Roadmap | No | Success Metrics | Satish N | Success metrics would be same as MUKTA as it would be adopting the specifications. |
24 | Adoption Metrics | No | Adoption Metrics | Satish N | Prashanth | Same as MUKTA |
25 | Program Roll-out Plan | No | Pilot Roll-out plan | Sameer | Prashanth |
26 | Impel checklist | No | Arindam | Elzan |
27 | Impel roll-out plan | Yes | Arindam | Elzan |
28 | Gate 2 | In progress | Gate 2 JIRA dashboard | Sameer, Satish N, Pritish, Arindam | Ex co | Gate 2 is scheduled on 28th March 2024 |
29 | The Internal release communication along with all the release artefacts are shared by the Engineering team. | Satish N | This will be shared after Gate 2. |
Development is completed and tag is generated,
Verify whether all docs are published to website by the Technical Writer as part of the release.