You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background:
As the FX API’s have not been completely ratified by the community, it seems logical for the first FX delivery to be a POV to illustrate the end to end functioning is a basic way. This way if there are API changes that are made, they can be accomodated in subsequence hardening of the POV stories.
As Community member interested in the FX workflow
I would like to prove that the FX use case meets the product requirements
So that I can validate and confirm the FX design
Acceptance Criteria
Build basic functionality for the fxTransfer Prepare & Fulfil at the switch only without unit tests/integration tests
Build basic functionality for the FX related changes to transfers Prepare & Fulfil at the switch only without unit tests/integration tests
PaulGregoryBaker
changed the title
FX Transfers Prepare & Fulfil POC for switch
FX Transfers Prepare & Fulfil POV (proof of value) for switch
Oct 23, 2023
PaulGregoryBaker
changed the title
FX Transfers Prepare & Fulfil POV (proof of value) for switch
FX Transfers Prepare & Fulfil POV (proof of value) for switch (1pt left)
Nov 20, 2023
PaulGregoryBaker
changed the title
FX Transfers Prepare & Fulfil POV (proof of value) for switch (1pt left)
FX Transfers Prepare & Fulfil POV (proof of value) for switch (2pt left)
Nov 20, 2023
JaneS321
changed the title
FX Transfers Prepare & Fulfil POV (proof of value) for switch (2pt left)
FX Transfers Prepare & Fulfil POV (proof of value) for switch
Nov 28, 2023
Background:
As the FX API’s have not been completely ratified by the community, it seems logical for the first FX delivery to be a POV to illustrate the end to end functioning is a basic way. This way if there are API changes that are made, they can be accomodated in subsequence hardening of the POV stories.
As Community member interested in the FX workflow
I would like to prove that the FX use case meets the product requirements
So that I can validate and confirm the FX design
Acceptance Criteria
Tasks
Prepare handler
for handling FX transfers [@geka-evk ]Position-prepare handler
for handelling FX transfers [@vijayg10 ]Position-commit handler
for handelling FX transfers [@vijayg10 ]Fulfil handler
for handelling FX transfers [@vijayg10 ]Feature Branches
Pull Requests
The text was updated successfully, but these errors were encountered: