Update Orders Search Interface Design

Problem(s):

  1. Users are not able to see orders and order lines at the same time.
  2. When searching users need to choose between order and order line details. This limits possible search criteria for both types of record and is not user friendly.

Use Cases & Requirements:

RequirementStatusUse cases
Allow user to search combined list with search and filter criteria from either PO or POL

PENDING

  • Often times we will search orders base on order type and receipt date or other sets of data that combined info from the PO and POL in FOLIO. 
  • User may want to search for orders based on title and filter by Date ordered, prefix or suffix or even Bill to address etc.
Display PO and POL details in a  single search result list. allow user to select either PO or POL to view details

PENDING

  • When working with orders lines it would be helpful to be able to see what type of order the line is related too. Some titles can be ordered in different ways and the PO information helps distinguish between the lines
  • When searching POs it is time consuming to move between order lines. First you need to return to the PO and then select the next POL.


Proposed workflow:

  • User can choose the "Tab based" or "One search" view (Mockup TBD)
  • With "One search" user can search and filter based on order OR order line criteria
  • For each PO user can see the number count of POLs that appear on that PO
  • When a search is executed the result lists show a hierarchical list rather than a table
  • When search query hits POL data the PO is expanded by default in the result list (How to highlight the actual search hits or what the search hit on. Ie PO or POL)

  • Changing relevancy selection adjusts the order of the result list. (How to change between ascending or descending??)
  • When users selects a PO or POL the record is displayed in the third pane

Draft proof of concept for hierarchical lists in search results:

Here's a draft PR for the POC
https://github.com/folio-org/stripes-components/pull/1611
Please ignore anything related to Pagination component - I created my branch from John's Pagination work. It's used only in Storybook and not needed by the actual implementation

User Questions:

Question

Status

Conclusion

Comments

How segmented do filters need to be? Would you want to search Date created, but only order date created and not POL?

OPEN


AISIG: Could see this being valuable in some situations

How could the search and filter are be better organized. There will be a lot of filters. How will the search terms work? There will now be a lot of search possibilities in the drop down.


Vendor Questions:

Question

Status

Conclusion

Comments


CLOSED



Development Questions:

Question

Status

Conclusion

Comments


OPEN



Work Breakdown Structure:

Features:




UI Stories


MOD Stories