Looking for ways to make this better
cross index sub queries
the full view of the PO is not enough
More information from the PO could be incorporated
when you select, would the better mode to combine PO 'header' with info from the POL?
from chat (What’s the maximum number of POLs you are likely to see on a single PO? )
Answer: You could have up to 999 POLs on a PO
from chat (Is the basis for that maximum a real use case or just a system limit that happens to have been implemented? (I’m sort of assuming the latter)
from chat (Yes, we are Cornell do use multiple line items for one time orders. Having the PO and POL information together would be nice to see. When I look at the PO I also think of it as the header. )
multiple POLs on a single PO can cause issues of tracking, cleanup, etc
The looking at PO in orders does not provide enough information to be helpful
POL has so much more information
each POL has to be clicked into to see what is actually what (to know which titles are associated with each order)
from chat (I’m interested in how this is solved in a UI/UX sense because there’s a parallel to Agreements + Agreement Lines and I’ve wondered if we need to have an Agreement Line search like the POL search … but OTOH don’t want to end up recreating the same problem being discussed here (although obviously there are differences in the two scenarios and what is the key information) )
key distinctions between ongoing and one-time (context is so different)
don't want to click between 2 records to figure things out
no way to filter between one-time and ongoing (order type is in the header, the PO)
But order status, type, etc are very important
we need to continue to talk about search (not perfect, even if it's quick)
How to rethink the back end WHILE integrating some of the PO and POL info better
from chat (There’s search and there’s display right? //
For example I could see some of the issues resolved by an additional pane (if we had the room!))
from chat (I’m not saying that’s the right way to do it, but it seems like a possible approach )
elasticSearch opens more doors for data coming from other apps, not just the app in which you're currently working
Possible display that shows the PO and the POL info
ref:
UXPROD-491
from chat (tbh I don’t think UXPROD-491 takes us in the right direction for what we are needing for Orders )
from chat (sure, just the point being the need for enhanced view of parent-child relationships on POs and POLs)
from chat (Rather than another pane why not expand each pol as you click with PO persisting on top )