Skip to Main Content
Return to Navigation

Understanding PeopleSoft Search Definitions for ELM

Each PeopleSoft application provides predefined application-specific search definitions for implementation within the PeopleSoft Search Framework. Tables later in this documentation provide a list of the search definitions that Oracle delivers preconfigured for PeopleSoft ELM.

You can use PeopleSoft ELM global search definitions and search page (component) definitions as delivered, copy and modify them, or create new ones.

Note: For easier maintenance and patch upgrades, Oracle recommends that you preserve the preconfigured application-specific search definitions as default definitions. To modify a delivered search definition, manually copy it and then modify the copy.

For information about the building blocks or objects that are associated with a search definition (query types, delete query, security type, attributes, facets, search category, and so on), and to learn how to create and implement search definitions using PeopleSoft Search Framework, you must read .

To view the preconfigured ELM search definitions that are listed in this topic, access the Search Definition component select (PeopleTools, then select Search Framework, then select Designer, then select Search Definition).

PeopleSoft Search Considerations for ELM

When implementing PeopleSoft Search Framework for ELM, keep these general considerations in mind.

PeopleSoft ELM searches:

  • Are enabled for Global Search.

    Note: There are component level Keyword Search Page searches are preconfigured for ELM at this time.

  • Are delivered for some administrative components (Keyword Search Page searches). These searches are also enabled for Global Search.

  • Consider only current effective-dated rows. Incremental indexing should be run daily to index changed data into the SES system and return most recent information. Consider the rate at which your data changes to determine the frequency for incremental indexing. For example, the Time and Absence indexes may need to be incrementally indexed multiple times in a day, whereas Succession Planning might only need to be incrementally indexed once in a quarter.

  • Are based solely on the fields and values that are indexed.

  • Rely on the last updated date/time stamp field for incremental search indexing. (If a date/time stamp field is not present in the underlying tables of a search definition, then changes to that table will not be tracked by SES. Date and numeric fields cannot be added as facets.)

  • Allow non case-sensitive free text search.

  • Accept only an asterisk (*) as a wildcard in keyword search. Searching by any other special character is not supported. (Wildcards are not allowed at the beginning of keywords. Consult your Oracle SES documentation for more information about wildcard use and limitations.)

In addition to these general considerations, each PeopleSoft ELM search definition may have its own, more specific set of considerations.