Implement logic for updating Item fields when Piece was changed
CSP Request Details
None
CSP Rejection Details
None
CSP Approved
None
Description
Environment
None
Potential Workaround
None
Attachments
1
defines
has to be done before
Checklist
hideTestRail: Results
Activity
Show:

Artsem Churakou February 21, 2022 at 12:55 PM
Verified on testing via API tests https://github.com/folio-org/folio-integration-tests/pull/452

Andrei Makaranka February 18, 2022 at 12:51 PM
Verified on testing https://github.com/folio-org/folio-integration-tests/pull/452
Done
Details
Details
Assignee

Reporter

Priority
Story Points
3
Sprint
None
Development Team
Thunderjet
Fix versions
Release
Lotus R1 2022
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created September 13, 2021 at 6:25 AM
Updated March 4, 2022 at 11:23 PM
Resolved February 21, 2022 at 12:56 PM
TestRail: Cases
TestRail: Runs
Purpose/Overview:
Item fields need to be updated (displayOnHolding, enumeration, chronology, discoverySuppress) when Piece was changed.
Requirements/Scope:
Updated fields (displayOnHolding, enumeration, chronology, discoverySuppress) from Piece should be reflected in the Item
Approach:
1. Update Item by calling inventory using REST call : org.folio.service.pieces.PieceService#updatePieceRecord
1.1. Create new class org.folio.service.pieces.PieceUpdateFlowManager (contains all business logic for updating piece), if it not created before.
1.2. Create holder for storing intermediate data, which will be used in the async future flow), if it not created before. Example org.folio.models.pieces.PieceCreationHolder
1.3. Add logic to update fields (displayOnHolding, enumeration, chronology, discoverySuppress) from Piece should be reflected in the Item
Acceptance criteria:
Update Piece logic implemented
Unit tests
API tests