Update purchase order number pattern
CSP Request Details
None
CSP Rejection Details
None
CSP Approved
None
Description
Environment
None
Potential Workaround
None
relates to
Checklist
hideTestRail: Results
Activity
Show:
Siarhei Hrabko November 20, 2019 at 4:10 PM
I have created a separate story for that https://folio-org.atlassian.net/browse/MODINVOICE-116
Kruthi Vuppala November 18, 2019 at 4:17 PM
There is also a PO Number field in invoice.json, the pattern has to be changed there too. I know this is a mod-orders story , create a separate story if you prefer, but please make sure it is merged in this sprint
Kruthi Vuppala November 18, 2019 at 4:15 PM
verified on folio-testing:
1. create an order with PO Number-123
RESPONSE:
Siarhei Hrabko November 18, 2019 at 11:49 AM
Verified on testing environment
1. Create an order with short poNumber
2. Assign poline to order. polineNumber is short as well
Done
Details
Assignee
Kruthi VuppalaKruthi VuppalaReporter
Dennis BridgesDennis BridgesTester Assignee
Craig McNallyCraig McNallyLabels
Priority
P3Story Points
1Sprint
NoneDevelopment Team
ThunderjetFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Kruthi VuppalaReporter
Dennis BridgesTester Assignee
Craig McNallyLabels
Priority
P3Story Points
1
Sprint
None
Development Team
Thunderjet
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created November 6, 2019 at 3:37 PM
Updated October 6, 2021 at 1:30 PM
Resolved November 20, 2019 at 4:31 PM
Overview
The currenty minimum number of digits for the PO number (5) is preventing users from migrating orders from other systems.
Approach
Change the purchase_order.poNumber pattern from
to
Change the po_line.poLineNumber pattern from
to
Acceptance criteria
schemas have been updated (don't forget about the composite schemas)
adjust sample data so that at least one order has a shorter poNumber/polNumber