The Create Saved Search page is identical to the Duplicate Saved Search and Update Saved Search pages, except that the fields in the latter pages are pre-populated with settings from the selected personalization.

1. Edit the following General Properties for your table or HGrid region:

   • Saved Search Name - the name of the personalized end user saved search as it appears in the Personalize Saved Searches page or the Personal Table Saved Searches page for end-users.

   • Number of Rows Displayed - the number of rows of data you wish to display in the table.

   • Set Saved Search as Default - check if you want to make this personalized saved search the default saved search. As an Administrator, you can only set an "Admin-seeded" end user saved search as a default.

     Note: If an "Oracle-seeded" end user saved search and an "Admin-seeded" end user saved search of the same region are both marked as defaults, the "Admin-seeded" end user saved search takes precedence and is displayed as the default for the end user. However, if an end user also has a personalized saved search of the same region that he or she marks as the default, then the end user's personalized saved search takes precedence over both seeded saved searches and is the default for that end user. See Default Sved Searches for additional information.

   • Securing Function - the function for which this saved search is available. Specifying a securing function allows you to restrict the use of this saved search to only users who have been granted access to that function. Refer to the section on Securing Saved Searches for complete information.

   • Description - an optional description for this personalized saved search.

2. Use the Columns Shown and Column Order shuttle to specify the columns to display in the table or HGrid region. Select an item from the Available Columns or Columns Displayed list and use the arrows between these lists to either move the selected item to or remove the selected item from the Columns Displayed list.

   Note: Columns that are required fields table appear with an asterisk (*) and cannot be removed from the Columns/Attributes Displayed list.

   Example

   Following is an example of an advanced table with two levels of column spans.

   

   Each of the columns in the top row (labeled "Group X" and "Group Y") spans two columns in the second row (labeled "Group A" and "Group B" in both cases). Each "Group A" column in turn spans "Column 1" and "Column 2" below it, while each "Group B" column spans "Column 3" and "Column 4."

   If the region you are personalizing is an Advanced Table that displays column spans, as shown in the example, the columns listed in the Available Columns and Columns Displayed shuttle will have the entire hierarchy of column group names appended to each column name. This ensures that you hide/show the correct column, especially in the case where multiple columns of the same name may exist within different column groups. For the example shown, the columns shown in the Available Columns and Columns Displayed lists would be:

   Group X: Group A: Column 1
   Group X: Group A: Column 2
   Group X: Group B: Column 3
   Group X: Group B: Column 4
   Group Y: Group A: Column 1
   Group Y: Group A: Column 2
   Group Y: Group C: Column 3
   Group Y: Group C: Column 4

3. Once you are satisfied with the columns to display, use the arrows to the right of the Columns Displayed list to reorder their sequence.

4. Choose Rename Columns / Totaling to rename or show a total for a column.

5. You can specify up to three levels of sorting for your data in the Sort Settings region. Select a column from the Column Name poplist for each level of sorting you wish to perform.

   Note: Only columns whose Sort Allowed property is set to Yes are displayed in the Column Name poplist. If this property is initially set to no and you want to be able to sort on this column, you must first create an admin-level personalization of the table region that updates the Sort Allowed property for the column to yes.

6. For each sort column, specify whether to sort in ascending or descending order.

7. You can filter the data that is displayed in the table based on criteria that you specify in the Search Query to Filter Data in Table region:

   1. Indicate how you want the filter to match your search conditions by selecting one of the following radio buttons: Show table data when all conditions are met = Match All or Show table data when any condition is met = Match Any.

   2. The first four columns of the table are listed for you to specify search criteria. Using the poplist following the column name, choose a search condition and enter a value to search for in that column.

   3. Select a column from the Add Another poplist and choose Add to add more search criteria to your filter.

   Note: Only columns whose Search Allowed property is set to True are displayed in the Add Another poplist. If this property is initially set to False and you want to be able to search on this column, you must first create an admin-level personalization of the table region that updates the Search Allowed property for the column to True.

   Suggestion: If you leave the search criteria blank for a column, the filter will not search on that column.

8. When you are done personalizing your saved search of the table or HGrid region, you can choose Apply to save the personalized saved search and return to the Personalize Saved Searches page. If you choose Revert to revert to default settings, the following occurs depending on the page you are using:

   • Create Saved Search page - the page defaults to the pre-seeded display settings, where no query options are set.

   • Duplicate Saved Search or Update Saved Search page - the page defaults to the display settings and query options of the saved existing saved search.

   Note: How you set the Scope of your personalization context in the Choose Personalization Context page affects how your personalized saved search is saved. The saved search may be saved to the current instance of the page as a per instance personalization if you set the Scope to Page. If there is a shared region on the page and you select the Shared region as the Scope, the personalization you create on that shared region is also saved as a per instance personalization of that shared region but will appear in all occurrences of that shared region in any page that extends it. Refer to Per Instance versus Global Personalization for further details.

Securing Saved Searches

OA Personalization Framework secures saved searches through the Securing Function property in the Create/Update/Duplicate Saved Search pages.

If an "Oracle-seeded" or "Admin-seeded" end user saved search has a securing function associated with it, only end users who are granted access to that securing function are able to see that saved search in the Saved Searches poplist of the Saved Searchs panel of their Search page. The securing function, in addition to restricting visibility of a secured Saved Searches in the Saved Searches poplist of the Saved Searches panel, also restricts visibility of a secured saved search in the Personalize Saved Searches page.

As an administrator, you are not able to update or delete "Oracle-seeded" end user saved searches. As a result, seeded saved searches are always visible to all end users. For example, you cannot update "Oracle-seeded" saved searches to restrict them to a specific set of end users or delete some of these saved searches for all end users. However, if you want to turn off an "Oracle-seeded" saved search, you can duplicate the seeded saved search and set the securing function on the duplicated saved search to a function to which a user or group of users does not have access.

If you want to simply control the visibility of a saved search for an end user in the Saved Searches poplist of the Saved Searches panel, first duplicate the saved search and set a securing function on the duplicate, granting the user access to that function. Then in the Personalize Saved Search page, set Display Saved Search to Yes or No for that duplicated saved search.

The following table identifies the accessibility of saved searches to administrators as well as end users, when a securing function is specified for "Oracle -seeded" and "Admin-seeded" end user saved searches.