cancel
Showing results for 
Search instead for 
Did you mean: 
BethanyPare
Level 5
Status: New

The search drop down list within Processor Workspace is forced to be in alphabetical order. We are given the ability to specify the order that lookups are in within the LOOKUP resource parameters list, so the drop down should obey this order. Having frequently used searches at the top of the list is more streamlined and user friendly for the end users. This used to be functionality that existed but was taken away.

3 Comments
Status changed to: Reviewed
Karen_Hunter
Staff
Staff

Logged BPMP-I-22

Status changed to: New
Karen_Hunter
Staff
Staff

Update on current behavior.  Processor workspace provides two ways to list searches (2/3 below) where the order can be managed in the custom menu configuration.  The ability for a user to save a preference for the search list order or pin their favorites to the top is under consideration as a usability enhancement but it not prioritized at this time.  Keeping open for client feedback.

  1. Classic Workspace used two menu resources to configure the ordered list of baseline searches followed by the ordered list of client defined searches.  The user is presented only with searches that are in their security profile.  These two menus have always had a character limitation so many clients use shortened naming conventions and/or custom menus to manage the search list navigation and order. 
  2. Processor Workspace does not use these two menu resources. The Search Icon in the left navigation menu is available to all Users.  The Standard Search list includes all search resources (baseline and client defined) ordered alphabetically, that are in their security profile.  The  My Searches includes any reusable search criteria saved as a user preference – unlike searches saved as resources and secured via profiles.
  3. The PROCSRMN resource parameter can be configured to add baseline and saved searches into custom menus in the left navigation panel – subject to the same character limitation in the  parameter field for each menu (one level deep menu in a menu) but providing an alternative for .
BethanyPare
Level 5

For us, we do not prefer the recent movement to user preferences as it introduces differences between user's workstations and makes troubleshooting issues harder. 
Having the My Searches below the Standard Searches means that many users do not even realize they exist and those that do need to scroll through the entire list. 
The PROCSRMN resource adding new custom menus seems like more resources to do what Classic could already do. More overhead when we already have all of the resources to sort the searches the way we want them from Classic.