diff --git a/SUMMARY.md b/SUMMARY.md index df91ba9c..ea0a0523 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -379,7 +379,7 @@ * [Tech Guides](g2p-bridge/tech-guides.md) * [User Guides](g2p-bridge/user-guides/README.md) * [Releases](g2p-bridge/releases/README.md) - * [1.0.1](g2p-bridge/releases/1.0.1.md) + * [1.0.2](g2p-bridge/releases/1.0.2.md) * [Utilities and Tools](utilities-and-tools/README.md) * [ODK](utilities-and-tools/odk-collection-app.md) * [📔 User Guides](utilities-and-tools/odk-collection-app/user-guides/README.md) diff --git a/g2p-bridge/releases/1.0.1.md b/g2p-bridge/releases/1.0.2.md similarity index 83% rename from g2p-bridge/releases/1.0.1.md rename to g2p-bridge/releases/1.0.2.md index 4805c11d..7dc7850c 100644 --- a/g2p-bridge/releases/1.0.1.md +++ b/g2p-bridge/releases/1.0.2.md @@ -1,12 +1,12 @@ -# 1.0.1 +# 1.0.2 -### Release version: 1.0.1 +### Release version: 1.0.2 ### Release date: 3rd December 2024 ## Summary -openg2p-g2p-bridge Release 1.0.1 represents a fully functional digital cash disbursement hub. This subsystem accepts disbursement payloads from upstream the PBMS (aka Program MIS) systems. It then interfaces with the downstream Sponsor Bank to initiate the corresponding payment requests. It also accepts account statement from the Sponsor Bank (account statement for the program funding account) and reconciles the payments and failures if any with the original disbursement requests. +openg2p-g2p-bridge Release 1.0.2 represents a fully functional digital cash disbursement hub. This subsystem accepts disbursement payloads from upstream the PBMS (aka Program MIS) systems. It then interfaces with the downstream Sponsor Bank to initiate the corresponding payment requests. It also accepts account statement from the Sponsor Bank (account statement for the program funding account) and reconciles the payments and failures if any with the original disbursement requests. To demonstrate the end to end lifecycle of disbursments, this release also ships a Sponsor Bank simulator - called openg2p-g2p-bridge-example-bank. This simulator implements all the APIs expected from a Sponsor Bank. It also generates Account Statement in MT940 format. @@ -18,23 +18,23 @@ The g2p-bridge subsystem has the following microservices and libraries #### openg2p-g2p-bridge-api -1. Microservice - that implements all the APIs (incoming APIs from upstream PBMS/MIS systems, outgoing APIs into Sponsor Bank and incoming APIs from Sponsor Bank) +Microservice - that implements all the APIs (incoming APIs from upstream PBMS/MIS systems, outgoing APIs into Sponsor Bank and incoming APIs from Sponsor Bank) #### openg2p-g2p-bridge-celery-beat-producers -1. All processing in g2p-bridge is handled asynchronously. This asynchronous processing is orchestrated using Celery Beat producers. +All processing in g2p-bridge is handled asynchronously. This asynchronous processing is orchestrated using Celery Beat producers. #### openg2p-g2p-bridge-celery-workers -1. The beats produced by the aforementioned beat producers are processed by celery workers. This module implements the necessary workers. +The beats produced by the aforementioned beat producers are processed by celery workers. This module implements the necessary workers. #### openg2p-g2p-bridge-models -1. This is a library that contains the pydantic schemas and sqlalchemy models for the g2p-bridge subsystem +This is a library that contains the pydantic schemas and sqlalchemy models for the g2p-bridge subsystem #### openg2p-g2p-bridge-bank-connectors -1. This library contains the interface definitions for connecting with the sponsor bank. It also contains an implementation of this interface, to connect with Example Bank. +This library contains the interface definitions for connecting with the sponsor bank. It also contains an implementation of this interface, to connect with Example Bank. Connecting with different sponsor banks during implementations will require custom connectors to be written - on the lines of Example Bank Connector. ### openg2p-g2p-bridge-example-bank