Release Summary

IFIX 2.4 is a new release that offers new features and functions, the details of which are provided below.

Functional changes

• 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.

Non-functional changes

NA

New ‌Feature Additions

Known Issues

• 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.

Document Resources & Links

Technical Documents

High Level Design

Low Level Design

Backend Service Documents

DIGIT Exchange

Program Service

Mukta iFix Adapter

IFMS Adapter

MDMS Changes

Config Changes

Infra Changes

Here are the test cases for Program Service, Digit Exchange, Mukta-ifix-adapter.

Program Creation

After installation of all required services, port-forward the program service and create programs for each ULB. A sample curl is added below.

curl --location 'http://localhost:8082/program-service/v1/program/_create' \
--header 'Content-Type: application/json' \
--data-raw '{
    "signature": null,
    "header": {
        "message_id": "123",
        "message_ts": "1708428280",
        "message_type": "program",
        "action": "create",
        "sender_id": "program@https://unified-dev.digit.org",
        "receiver_id": "program@https://unified-qa.digit.org"
    },
    "message": {
        "location_code": "pg.citya",
        "name": "ifix",
        "description": "Empowering local communities through sustainable development projects.",
        "start_date": 1672531200,
        "end_date": 1704067200,
        "children":null,
        "status": {
            "status_code": "INITIATED",
            "status_message": "ACTIVE"
        },
        "additional_details": {},
        "function_code": "in.pg.OGES",
        "administration_code": "in.pg.ac.HUDD.UID",
        "recipient_segment_code": "in.pg.rsc",
        "economic_segment_code": "in.pg.CE.IA.OC",
        "source_of_fund_code": "in.pg.CSS",
        "target_segment_code": null,
        "currency_code": "INR",
        "locale_code": "in.pg.citya"
    }
}'

• Configure all program codes that you created for each ULB to the MDMS.

IFMS Data Migration

• IFMS adapter data migration for mukta-adapter ad program service

  • Use this specific branch for iFix migration.

  • 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.

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.

digit-exchange:develop-1b9d9a2-23

program-service:develop-92a135f-55

ifms-adapter:develop-bd05fc83-113

mukta-ifix-adapter:develop-4799181a-46