Search queries that are executed regularly can be created as a ‘Saved Search’ and made available to end-users. A Saved Search will comprise sort and filter criteria as well as a definition of which fields to show on the data set. By default, every new Saved Search is available to any user. Role-based restrictions can be configured using an exception profile.
The application comes with the following pre-delivered saved searches that are not removable:
object |
Pre-Delivered Saved Searches |
---|---|
Accounts, Leads, Opportunities, Quotes, Products, Emails |
‘All [Object]’ and ‘My Favourite [Object]’, e.g. ‘All Accounts’ and ‘My Favourite Accounts’ |
Tasks, Phone Calls, Meetings |
‘All [Object]’ and ‘Upcoming [Object]’, e.g. ‘All Tasks’ and ‘Upcoming Tasks’ |
Create New Save Search
Users with administration rights can create new Saved Searches by going to the respective data set. Once a search query has been configured (including sort and filter criteria as well as the respective columns to be shown), the administrator can launch the search configuration popup, and click on ‘Save as…’:
Customization
The user(s) may adjust the sequence of how the saved searches appear in the dropdown (the first search is the default search), maintain localization information as well as hide or delete saved searches.
Note: The pre-delivered searches cannot be deleted.
In this profile, the administrator can define whether the search query should be shown or hidden, or whether it should inherit the display or hide parameters from the Saved Search itself. For example, if a Saved Search is configured to be hidden, but the exception profile overwrites this by setting the visibility to ‘Show’, the search will only be available to users with the respective profile assigned to their roles.
Comments
0 comments
Please sign in to leave a comment.