Legacy platform

Managing saved search

IBM® Sterling™ Field Sales enables you to save and manage searches for opportunities and quotes.

A Field Sales Representative may want to save a search for future use to avoid entering the same criteria every time the Field Sales Representative wants to search for a particular entity. For example, a Field Sales Representative, who is currently working on closing all the quotes created for a customer, may have to frequently search for the quotes created for that customer.

Solution

Sterling Field Sales enables a user to manage saved searches for the following entities:

  • Opportunity
  • Quote

As part of saved search management, a user can perform the following tasks:

  • Saving a Search
  • Searching for a Saved Search
  • Renaming a Saved Search
  • Viewing and Executing a Saved Search
  • Deleting a Saved Search

Solution for saving a search

A user can save a search to avoid entering the search criteria every time the user searches for an entity. The createSavedSearch API is called to save a search after the user clicks Save in the Saved Search dialog box.

Solution for searching for a saved search

A user can search for a saved search. The getSavedSearchList API is called to retrieve the saved searches matching the search criteria.

Solution for renaming a saved search

A user can search for a saved search and rename the saved search. After a user modifies the name of the saved search, the modifySavedSearch API is called to save the changes.

Solution for viewing and executing a saved search

A user can view and execute a saved search. The getSavedSearchList API is called to retrieve the available saved searches that a user can view and execute. The getSavedSearchDetails API is called to display the corresponding search screen for a saved search. Based on the SearchContext attribute of the saved search, the corresponding strut action is invoked to execute the saved search.

Solution for deleting a saved search

A user can delete a saved search if the saved search is no longer required. The deleteSavedSearch API is called to delete the saved search.

End-user impact

None.

Implementation

None.