shubhamchaudhary29 opened a new pull request, #6261: URL: https://github.com/apache/fineract/pull/6261
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_transfer` lookup 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_INTERQUOTE` to `READ_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 - Added Interoperation integration coverage for prepared and committed transfer lookup, response fields/completed timestamp, unknown pairs, and both mismatch directions. - `:fineract-provider:compileJava` completed during focused compilation. - `git diff --check` passed. 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 `PaymentDetail` or `m_payment_detail` changes, quote/transaction-request persistence, audit-command queries, broad refactoring, dependencies, CI workflow changes, or historical backfill are included. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
