UXPROD-3257 - Getting issue details... STATUS
Problem(s):
- There is no logic in place to manage the cancellation of orders and order lines. User currently need to understand and take all individual steps needed to completely cancel an order and release all encumbrances etc. This also makes it difficult/impossible for other applications to trigger the cancelation of an order.
Use Cases & Requirements:
| Requirement | Status | Use cases |
|---|---|---|
| Allow user to cancel a POL with one action | VALIDATED | Ongoing orders may include multiple POLs. The library may choose to cancel one or more of those titles but not all. This could be for monetary reasons, lack of use or lack of availability. |
| Release any remaining encumbrance when order line payment status is set to canceled | VALIDATED | When an order line is canceled the library would expect any remaining encumbered values would be release back into the budget so it is less likely that value will remain unused. |
Proposed workflow:
Status matrix
| Order status | Pending | Awaiting | Partially | Ongoing | Fully | Receipt not required | Canceled |
|---|---|---|---|---|---|---|---|
| Pending | Pending | NA | NA | NA | NA | Pending | NA |
| Awaiting | NA | Open | Open | Open | Open | Open | Open |
| Partially | NA | Open | Open | Open | Open | Open | Open |
| Ongoing | NA | Open | Open | Closed | Open | Open | Open |
| Fully | NA | Open | Open | Open | Closed | Closed | Closed |
| Receipt not required | Pending | Open | Open | Open | Closed | Closed | Closed |
| Canceled | NA | Open | Open | Open | Closed | Closed | Closed |
Questions:
Question | Status | Conclusion | Comments |
|---|---|---|---|
| Are there use cases for "Un-cancelling" orders? | OPEN |
Work Breakdown Structure:
Features:
UXPROD-3257 - Getting issue details... STATUS