Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
ACQ Sprint 67, ACQ Sprint 68, ACQ Sprint 69
-
5
-
Thunderjet
Description
Overview
Restrict Creation of orders, poLines and pieces based upon the acquisitions unit memberships of the user and the acquisitions unit being assigned to the record.
Acquisitions units are described on the wiki . The order-specific details which this story covers can also be found there.
Acceptance Criteria:
- Acquisitions units are used to determine if a user can create the PO/POL/Piece record
- Unit tests are updated
- API tests are updated to cover different cases:
- the user created for API tests should be assigned to several acquisition units
- the user created for API tests should be assigned to one
- the user created for API tests should be assigned to none
TestRail: Results
Attachments
Issue Links
- has to be done after
-
MODORDERS-266
Implement basic CRUD for /orders/acquisitions-unit-assignments
-
- Closed
-
-
MODORDSTOR-82
Implement basic CRUD for /acquisitions-unit-storage/units
-
- Closed
-
-
MODORDSTOR-83
Implement basic CRUD for /acquisitions-units-storage/memberships
-
- Closed
-
-
MODORDSTOR-92
Implement basic CRUD for /orders-storage/acquisitions-unit-assignments
-
- Closed
-
- has to be done before
-
MODORDERS-256
Restrict search/view of PO, POL, Piece records based upon acquisitions unit
-
- Closed
-
-
UIOR-300
Ability to assign acquisition unit(s) to order records
-
- Closed
-
- is cloned by
-
MODINVOICE-69
Restrict creation of invoice, invoiceLine records based upon acquisitions unit
-
- Closed
-
-
MODORDERS-254
Restrict updates of PO, POL, Piece records based upon acquisitions unit
-
- Closed
-
- relates to
-
MODORDERS-285
Restrict receive/checkin records based upon acquisitions unit
-
- Closed
-
-
UXPROD-1687 Manage users ability to view and work with Acquisitions records based on assigned "Acquisition Unit(s)"
-
- Closed
-