Page Comparison

Agenda

Presenter

Duration

Discussion

Review pending action items

 Esther Ogunjimi

 10 minutes

Payment BB with ID, Digital Registries, Registration BB Leads and MiFos representative met to discuss user interface that would be exposed by the payments building block at the time of verification of eligibility.

MiFos has agreed to use the user interface from the registration building block, so they will use that on their side for exposing that user interface for the beneficiary to enter their banking or payment details.

Pub sub was suggested to be used for messaging i.e. telling the user that the message or the information on the submitter has been sent to the payments building block and also letting registration know that the users actually entered that information.

V1.0 publication feedback

Esther Ogunjimi

10 minutes

https://govstack-global.atlassian.net/l/cp/H96X5GCR

Roadmap breakown

Steve Conrad

15 minutes

2023 Roadmap

https://govstack-global.atlassian.net/jira/plans/reports/7bfKt

Wave 3 use cases can be added here Use Case Discussions

Status Update

Leads

30 minutes

• BBs Update

  • IM BB

    • Discussing how to handle API gateway - on-going discussion and no decision has been made.

  • Messaging BB

    • Worked on outstanding specs issues

    • About to deliver implementation of messaging in different existing products

  • Payment BB

    • Discussed the alignment of the functional ID and seeding of the account mapper with MiFos team and Registration BB.

    • Waiting to receive the updated technical report for G2P bug disbursement and P2G payment - these report will be reviewed by the team

    • Working with G2P connect on alignment on G2P payment.

  • Consent BB

    • Working on the next version of the spec with focus on delegation

    • Aligned with UI/UX BB on the input needed to develop consent spec and the way UI should be explaining the role of consent.

    • Working on testing consent APIs

    • Selected vendor to develop DPG for consent

  • ID BB

    • Working on onboarding of ID BB on social element. The objective is to either unroll from an external registration system being a client or server, or to be capable to also import existing form of ID.

    • Working on integration ID BB with consent BB

  • UI/UX BB

    • Migrating spec into GitBook - these are the functional requirements, the front end design standards.

    • Ongoing work on patterns for the common workflows.

    • Created basis wireframe and will be involving an international designer to work on more detailed user interfaces.

    • Next steps

      • Getting feedback from the Consent BB and will also be reaching out to registration BB.

• USCT use case definition

  Jira Legacy
  server System JIRA serverId f5c6bdaf-d23e-347d-a1e8-579e20a81dda key TECH-225

  • Made changes to USCT steps and waiting for sign off

• Testing

  • Finalised testing for ID BB and almost finalising Registration BB

  • Added SSL certificates to the app

  • Discussed how to integrate open images into the test hardness

• Sandbox TeamBasic guidelines for building block Sandbox deployment

  • Finalising stimulation of front end journey

  • Working on MVP implementation

• Architecture Team

Working through cross building block authorization and documenting how building blocks interact with one another, both through information mediator and in scenarios where there are services that are co-located.

Issues related to X-Road central server cloud native deployment

Aleksander Reitsakas Allan Bernard

20 minutes

X-Road central server cloud native deployment

Satya - Do we know of areas where X-Rd central server has been possible to deploy cloud natively? If not how do we handle this particular situation so that we can move forward because Nortal has a requirement to deploy X-Rd which includes the central server and the security server in a cloud native environment.

This topic will be discussed internally with procurement.

Example Implementations for USCT use case

Damian Borowiecki (Deactivated)

10 minutes