UIOR-1159 Provide 'instanceTenantId' from the PO form to PO line form #1513

usavkov-epam · 2023-10-12T16:17:54Z

Purpose

https://issues.folio.org/browse/UIOR-1159

This PR is for the missed part of #1511

There are two ways of navigating to the orders app from the inventory (when creating an order from an instance): to the PO form and to the PO Line form. In both cases, we should handle the provided instanceTenantId. The previous PR (#1511) covers only the second way. So we still need to provide instanseTenantId to the PO line form, but now from PO form.

Approach

Pass the instanceTenantId value from inventory to PO line form through PO form.

Screenshots

chrome_a4vnUgWJPU.mp4

Pre-Merge Checklist

Before merging this PR, please go through the following list and take appropriate actions.

I've added appropriate record to the CHANGELOG.md
Does this PR meet or exceed the expected quality standards?
- Code coverage on new code is 80% or greater
- Duplications on new code is 3% or less
- There are no major code smells or security issues
Does this introduce breaking changes?
- If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
- There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

What other modules will these changes impact?
Do JIRAs exist to update the impacted modules?
- If not, please create them
- Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
- Do they have all they appropriate links to blocked/related issues?
Are the JIRAs under active development?
- If not, contact the project's PO and make sure they're aware of the urgency.
Do PRs exist for these changes?
- If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.

While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.