Details
-
Type: Story
-
Status: Open
-
Priority: Critical
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Web Pages Release
-
Component/s: None
-
Labels:None
Description
we need to have a lock exclusion on Orders so that more than one user will not try to fulfill the order at the same time. Risks involved include unnecessarily spending money on domain and call tracking provisioning (not reflected in screen shot below since web pages are a 2.5 release feature).
user opens order and clicks on the ASSIGN TO ME button. UI displays Currently assigned to: username. (This is system generated based on user login name). default is "unassigned"
The user will need a way to unassign themselves in the event they cannot complete the fulfillment process for some reason. perhaps the ASSIGN TO ME button toggles to UNASSIGN.
If the user completes the fulfillment process, either clicks the REQUEST DEPLOYMENT button (FULFILLED status) or REJECT ORDER button (REJECTED status) or SAVED button (OPEN status), the order becomes unassigned. Clicking the Cancel button also unassigns the order.
List of Orders will include column for Created By, Assigned To, Date Submitted and Status. Status values include: ASSIGNED, REJECTED, FULFILLED, OPEN (default), ERROR (tried to deploy but failed) and DEPLOYED (but these orders are not listed in the Order List view).
Attachments
Issue Links
- blocks
-
AML-361 Manage Orders
- Resolved