Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Duplicate
-
None
-
None
-
-
ACQ Sprint 71
-
Thunderjet
Description
Overview
There's a new requirement to protect order approval with a separate assignable folio permission.
Approach
- Define a new permission orders.item.approve
- Add that permission as a "permissionDesired" for the PUT /orders/composite-order/<id> endpoint.
- In the implementation for that endpoint, validate the permission if the order is being approved (via inspecting X-Okapi-Permissions).
- Return an appropriate error message/code if the required permission is missing.
See the OKAPI guide for a description of "permissionDesired"
Acceptance Criteria
- ModuleDescriptor is updated
- Implementation is updated
- Unit tests are updated (Since we're enforcing permissions in this case we can actually test this in unit tests)
- API tests are updated
TestRail: Results
Attachments
Issue Links
- has to be done before
-
OKAPI-1070 Check permission names during install
-
- Closed
-
- relates to
-
-
- Closed
-
-
MODINVOICE-93
Approve invoice permission and require approval to mark as paid
-
- Open
-
-
MODORDERS-290
Enforce new setting: approval required to open orders
-
- Closed
-
-
MODORDERS-291
Add approvedBy and approvalDate fields to purchase_order/composite_purchase_order
-
- Closed
-
-
UIOR-235
Settings: require approval for orders to be opened
-
- Closed
-