FINERACT-2751: Implement interoperation transfer query - #6261
Open
shubhamchaudhary29 wants to merge 1 commit into
Open
FINERACT-2751: Implement interoperation transfer query#6261shubhamchaudhary29 wants to merge 1 commit into
shubhamchaudhary29 wants to merge 1 commit into
Conversation
shubhamchaudhary29
force-pushed
the
FINERACT-2751-query-interoperation-transfer
branch
from
August 11, 2026 17:44
4d09b54 to
0a9c086
Compare
shubhamchaudhary29
marked this pull request as ready for review
August 11, 2026 18:00
Contributor
Author
|
Hi maintainers, the workflows for this PR are currently blocked with action_required, |
Contributor
Author
|
@adamsaghy can you please approve the workflows, i did some changes for the conflicts. |
shubhamchaudhary29
force-pushed
the
FINERACT-2751-query-interoperation-transfer
branch
from
August 13, 2026 11:04
4cafc3f to
f3d3fb9
Compare
Contributor
Author
|
hi @adamsaghy , all the CI faliures happened because of the added PRs (thats what i think), but i think it should work out. please approve the workflow |
Contributor
Author
|
hi @adamsaghy, can you please review this pr. thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira: https://issues.apache.org/jira/browse/FINERACT-2751
Problem
GET /interoperation/transactions/{transactionCode}/transfers/{transferCode}previously returned no result because an Interoperation transfer did not retain a durable association to its transaction code.Change
Adds a small tenant-scoped
interop_transferlookup record containing only the transaction code, transfer code, action state, and latest completion timestamp. Successful PREPARE, CREATE/COMMIT, and RELEASE actions create or update that exact pair in their existing transaction. The GET endpoint performs an exact-pair lookup and returns 404 for an unknown or mismatched pair.The endpoint permission is corrected from
READ_INTERQUOTEtoREAD_INTERTRANSFER.Migration and compatibility
The additive Liquibase migration creates a composite unique constraint on
(transaction_code, transfer_code). Existing transfer behavior and the response route/schema are preserved. Legacy transfers cannot be backfilled reliably because their transaction-code association was never durably stored; therefore, they return 404.Tests and checks
:fineract-provider:compileJavacompleted during focused compilation.git diff --checkpassed.The full Interoperation integration test and complete quality matrix have not completed locally in this environment; GitHub CI will be monitored and any branch-caused failure will be fixed.
Scope exclusions
No
PaymentDetailorm_payment_detailchanges, quote/transaction-request persistence, audit-command queries, broad refactoring, dependencies, CI workflow changes, or historical backfill are included.