Create the secondary filter options for Orders

Overview: Until the PO/POL search results can be displayed in a hierarchical view, we will show the PO and POL search results separately. This story describes the secondary, less-urgent filter options for POs. The most urgent options are described in UIOR-265. Users need the ability to search and filter orders by a number of different field values. This will help them find exactly what they are looking for and what they should be working with.

There is a column in this Google sheet marked "Filter on This?" (column I) which identifies the fields that should appear as filter options. There is a tab for each App so you will need to navigate to the "Order" tab in this sheet for order fields, and only pay attention to the yellow filter options for the PO, not the green or the POL. https://docs.google.com/spreadsheets/d/1F88PoSnEKD7oFnza1ZuOgzAgKnK95XOyTQzxyww3tZA/edit#gid=1408113181

1. Scenario 1
   • Given the Orders app landing page
   • When a user wants to filter within POs (the purchase order toggle is highlighted)
   • Then they should see the following additional options in the filters area, in this order (existing filters also included, marked in red)
     • Status
     • Approved
     • Assigned to What list populates the Assigned to dropdown? All users? All active users? It might be good if we could restrict it somehow - maybe just users with order app permissions. Also, they dropdown options are not in any predictable order. There's no sample data for Assigned to, so I created a new order. Filter seems to be working. Let's clarify the data in the dropdown, and then I think will be OK, or we'll create an additional story to refine it. (DB: Unfortunately I don't think it makes sense to filter this list unless we can filter it by users who are currently assigned to orders. Perms and active or inactive will change over time and that could make it difficult to find certain orders)
     • Created by Same questions/observations as the Assigned to (DB: Unfortunately I don't think it makes sense to filter this list unless we can filter it by users who have created orders. Again perms and active or inactive will change over time and that could make it difficult to find certain orders)
     • Date created (by date range)
     • Date ordered (by date range)
     • Order type
     • Acquisitions unit (formerly team)
       • NOTE: excluded from this story; will be handled in a future story, once the acq unit work is completed. See UIOR-317
     • Vendor (name, followed by code in parentheses)
     • Reason for closure Filter does not seem to be working. I tried creating and closing a new order with reason Duplication, but the filter didn't find it. Also dennisbridges, should we include a value for "Complete"? It's not a listed reason for closure, but seems to be assigned automatically by the system. DB: Yes, it should be a "Listed" reason for closure as well.
     • Re-encumber
     • Renewal date (by date range)
     • Renewal manual
     • Renewal review period
   • And all filter accordions should be closed except for Status [workflow status], [since that filter is used in UIOR-269 as the default filter when the PO toggle is first opened]
   • And results should be displayed as indicated in UIOR-269
2. Scenario 2
   • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

NOTES:

• Leaving out PO prefix and suffix filtering for now; figure out if we need to include in the future, and if so, how