11Adaptive Search and Workspace

This chapter contains the following:

Overview of Adaptive Search and Workspace UI

Workspace improves and speeds up searches and makes key sales information available all within a single, unified work area. No more navigation to the Opportunities work area to see your key opportunities and then to the Leads work area to work on your leads. But there's more. The Workspace UI is built on top of Adaptive Search, a high-performance search engine that provides keyword searching and enhanced filtering capabilities. After you enable Adaptive Search, the Workspace UI icon appears on the home page in a separate Workspace tab. When you configure navigation, you can move the icon to the Sales tab so salespeople see all the navigation icons together in one tab.

You can enable the following objects for Workspace:

  • Account

  • Activity

  • Asset

  • Case - (available only in Adaptive Search REST API)

  • Campaign

  • Contact

  • Deal Registration

  • HR Help Desk Request - (available only in Adaptive Search REST API)

  • Internal Service Request - (available only in Adaptive Search REST API)

  • Lead

  • Opportunity

  • Partner

  • Partner Contact

  • Product - (available only in Adaptive Search REST API)

  • Product Group - (available only in Adaptive Search REST API)

  • Quotes and Orders

  • Quote and Order Line

  • Service Request

  • Territory

  • Work Order - (available only in Adaptive Search REST API)

Not all the objects are sales objects. Partner and Partner Contact are only pertinent for Partner Relationship Management. HR Help Desk Request, Internal Service Request, and Service Request are specific to B2B Service. You can also access and manage any custom objects or child objects that your administrator created in Application Composer.

Workspace UI

After you enable Workspace, the Workspace UI icon appears on the Welcome (home) page.

Salespeople can now do all of their work in Workspace instead of the individual work areas. However, you may want to enable individual work areas if you want to take advantage of these features not yet available in Workspace:

  • Inline editing

  • Enrichment of multiple accounts on the page

Here are some key actions salespeople can do in Workspace and how you can configure their behavior. See the setup topics in this chapter for the configuration details.

How Salespeople Use Workspace What Administrators Can Configure

When salespeople open Workspace, they select the business object and saved search they want to display. The saved search determines the scope of any search you perform on the page.

You determine which business objects and saved searches are available to users. You can create your own saved searches targeted to specific roles within the sales organization or available to everyone. And you can specify which object and saved search appears when users open Workspace. Salespeople can create their own personal saved searches and override the administrator defaults.

You can enter one or more search terms in the Search field.

You can use related information for your searches. For an account, you can search by company name, the city where the account is located, or the primary contact at the company, for example. You can even search for an account by the name of the salesperson on the sales team.

The search results match whole terms, but you can use the (*) wildcard for partial words. For searches with multiple terms, you can use the OR and NOT operators. For example, searching for "Oracle NOT Portland" returns Oracle locations not in Portland.

Use the Between operator for a date field. You are prompted to enter a specific date range for the search, such as between 1/3/2021 and 1/5/2021. Workspace search returns all records between January 03 2021 to January 04 2021. Records for January 5th aren't returned because Workspace considers the given filter values between 03-01-2021 12 AM and 05-01-2021 12 AM.

The saved search you select determines the scope of your search. For example, if you select All Accounts, you're searching all accounts you can view. If you select My Accounts, then you're searching only the accounts that you own.

You can enable or disable the attributes available for search. Oracle enables the most common attributes for you, but you must enable the search for any child objects and fields you create in Application Composer.

You can view the filters used in the saved search by clicking the Show Filters link. You can also add filters of your own.

You can specify which additional fields users can add as filters and you can set up groupings of values the filters show. For example, you can break down opportunities by revenue ranges: 0 to 10,000, 10,000 to 100,000, 100,000 to 500,000, and 500,000 and up.

Filters show the most common values and the number of records in each. For example, a search of accounts with the primary industry as a filter, automatically displays the most frequent industries and the number of records for each. A search of opportunities using win probability as a filter, displays different ranges of win probabilities and the number of records in each range.

Your filter selections are additive, if you select Health Care as the primary industry and then Lisa Jones as the owner, Workspace displays only those Health Care accounts Lisa owns.

You can configure value ranges for numeric, corporate currency, percent and date filters. For example, you can configure value ranges for the opportunity win probability filter and other similar filters.

Salespeople can save any search criteria they enter as their own personal saved search.

You can create saved searches for use by the whole sales organization and you can tailor them to different roles.

You can expose the Workspace saved searches as filters in Workspace infolets to display key sales information right on the home page.

Sales administrators and sales managers can download search results into an Excel spreadsheet. Salespeople who have the privilege ZCA_WORKSPACE_EXPORT can also use the Export List feature.

You can remove the Export List button from the page using Application Composer. You can also enable other custom sales roles to use the button, by granting the privilege ZCA_WORKSPACE_EXPORT.

Note: Service users can keep multiple records open at the same time in nested tabs, a Workspace feature not available to the sales job roles provided by Oracle. If you want to provide salespeople with the same nested dynamic tab capability, you can create custom job roles with the following additional privileges:
  • Open Objects in Dynamic Tabs

  • Open Objects in Dynamic Tabs for FSCM

  • Open Objects in Dynamic Tabs for HCM

If you choose to use dynamic tabs, then record-level navigation won't be possible. That means that the Previous and Next buttons on the record details page won't be available for navigating lists of records for Account, Contact, Lead, Opportunity, Activity, Campaign, Territory, and custom objects through the Workspace UI.

Here's a screenshot of the Workspace UI highlighting some of its key features.

Workspace showing sample list of accounts. The
page shows the open Filter panel with filters for Primary Industry,
Owner, and Type. Key features discussed in the text are highlighted
by callouts.
Callout Number Feature Description

1

Select the object and saved search you want to display in Workspace.

2

Use the Search field to search within the constraints of the saved search you selected. If you selected My Accounts, you get to view and search only the accounts where you're on the territory or in the sales team. Selecting All Accounts, makes it possible for you to search them all.

3

Control the display of filters by clicking Display Filters and Hide Filters.

4

View the number of records in your search results.

5

Use filters to understand your search results and to narrow down your search further. Filters show you the items with the highest number of results, for example, the industries with most accounts or salespeople who own the most opportunities.

6

Log calls, take notes, create tasks, and take other actions on search results without having to drill down into them. For accounts, you can even create an opportunity.

Adaptive Search Setup

Here's a quick rundown of the Configure Adaptive Search page. The rest of this chapter provides the details.

The Configure Adaptive Search page is made up of five tabs:

  • Monitor

  • Setup

  • Parameters

  • Configure UI

  • Configure Global Search

Setup

The setup tab includes the Quick and Advanced subtabs. You can select the business objects you want to enable in Workspace on the Quick subtab and click Publish to enable the search configuration provided by Oracle.

Sample screenshot of the Quick setup tab of the
Configure Adaptive Search UI

On the Advanced subtab, you can change which objects and fields are enabled for search, how they're searched on, and other search configurations. You can also enable and disable objects for searching. Click Publish to save these changes. Once the publish job is complete, any user with permission to access an enabled object can search on fields enabled within the object, retrieve search results, create saved searches, and more.

The left side of the Advanced subtab shows the ready-to-use objects, including any custom objects or child objects you created in Application Composer. The right portion lists the fields, including any custom fields you created. You must publish your changes before they take effect. See the Search Setup section of this chapter for details.

Note: To enable search on custom fields and custom child objects, you must first publish them from the sandbox. You can't use the Configure Adaptive Search UI within a sandbox.
Screenshot of the Advanced setup tab of the Configure
Adaptive Search UI

Monitor

You can monitor the publish process as well as other indexing and maintenance processes on the Monitor tab. See the Monitor Adaptive Search Background Processes topic for details.

Screenshot of the Monitor tab of the Configure
Adaptive Search UI

Parameters

You can configure various parameters to specify how Workspace behaves, using the Parameters tab available in the Adaptive Search setup page. For example, you can enable mass update and actions, set record-level navigation, specify the fuzziness level for search, and so on. See the Enable Adaptive Search Parameters topic for details.

Screenshot of the Parameters tab of the Configure
Adaptive Search UI

Configure UI

You can use the Configure UI tab to specify which fields are available for selection as Workspace filters and for display as columns in search results. You can also set up filter value groupings or value ranges for date and numeric fields. Users can select these value groupings to filter search results. See the Enable Fields for Display as Filters and Search Result Columns topic for details.

Note: The default layout specifies that a minimum of four fields must be displayed for your Workspace UI configuration. Therefore, when editing Workspace UI columns and specifying fields, always ensure that you have at least four fields selected for both standard and custom objects.
Screenshot of the Configure UI tab of the Configure
Adaptive Search UI

Configure Global Search

Global search enables you to search for any object to which you have access across CX Sales and B2B Services. Searches are performed across various fields and related objects and across custom fields. Results can be filtered based on objects and Last Updated Date.

Once you enable global search to use the adaptive search engine, you can use the Configure Global Search tab to:

  • Configure objects to be included in Global search

  • Define attributes to be included in the search results

  • Define the format and content of Title, Line 1, and Line 2 of each matching record's search result.

For more information about how to enable Global Search, see the topics in the Global Search section of the Global and Work Area Search chapter of the Implementing Sales guide.

Screenshot of the Configure Global Search tab of
the Configure Adaptive Search UI

Here is a summary of the setup steps for enabling and configuring Adaptive Search. You must have the Application Implementation Consultant job role to complete the setup. Only the first two setups are required. Detailed steps and navigation details are provided in the referenced topics.

When you enable the business objects you want to use from the Setup tab in the Configure Adaptive Search page and change the way search is implemented, then you run the Publish indexing process for the changes to take effect. Other setups take immediate effect.

Here's a table that lists and describes the steps required to enable and configure Adaptive Search. It also specifies whether you run the publishing process or not and refers you to the associated topics in this guide for more information.

Step Description Publish Required? Where to Get More Details

1

Enable the Workspace feature by clicking Configure Adaptive Search task link.

NA

For detailed steps, see Enable Workspace and Other Features That Use Adaptive Search in this chapter.

2

Open the Configure Adaptive Search task and select the objects you want to use for Workspace on the Setup Quick tab.

To use the configuration provided by Oracle, click Publish to run the indexing process. Workspace is ready for use and accessible from the home page after the process completes. You can monitor the process progress by clicking the Publish link on the Monitor tab.

Yes

See the following topics in this chapter:

  • A Quick Rundown of the Adaptive Search Search Setup UI

  • Monitor Adaptive Search Background Processes

3

You can modify how search operates on the Setup Advanced tab of the Configure Adaptive Search page. For example, you can specify which fields of an object and its related objects can be used in searches and displayed as search filters. Because Oracle configures the fields for you, setup is optional unless you want to enable search on custom child objects and fields, or to change Oracle's default search configuration.

You must run the Publish process for your changes to take effect.

Yes

See the Configure Search Attributes section of this chapter and the Monitor Adaptive Search Background Processes topic.

4

You can configure search filters on the Configure UI tab of the Configure Adaptive Search page. You can:

  • Specify which fields can be used as filters in UI searches and for display in search results

  • Define groupings of filter values for use during search.

    For example, you can break down opportunities by revenue ranges: 0 to 10,000, 10,000 to 100,000, 100,000 to 500,000, and 500,000 and up.

No

See the following two topics in this chapter:

  • Define Groupings of Values for Display in Search Filters

  • Enable Fields for Display as Filters and Search Result Columns

5

You can create and share saved searches for different roles in the organization. You must open Workspace to complete this setup.

No

See the Create and Manage Saved Searches topic.

Here's how to enable the Workspace UI and build the Adaptive Search index that's also used by Global Search, REST web services, and Workspace infolets.

  1. In the Setup and Maintenance work area, open the Configure Adaptive Search task:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Show: All Tasks

    • Task: Configure Adaptive Search

    Note: If this is your first time configuring Adaptive Search, then with the Sales Foundation functional area selected, click Actions and then select Change Feature Selection from the list. In the Edit Features: Sales Foundation page, click Enable for Configure Adaptive Search and click Done.
  2. On the Configure Adaptive Search page, click the Setup tab.

  3. On the Setup tab, Quick subtab, select the objects you want to enable for Adaptive Search:

    • Account

    • Activity

    • Asset

    • Case - (available only in Adaptive Search REST API)

    • Campaign

    • Contact

    • Deal Registration

    • HR Help Desk Request - (available only in Adaptive Search REST API)

    • Internal Service Request - (available only in Adaptive Search REST API)

    • Lead

    • Opportunity

    • Partner

    • Partner Contact

    • Product - (available only in Adaptive Search REST API)

    • Product Group - (available only in Adaptive Search REST API)

    • Quotes and Orders

    • Quote and Order Line

    • Service Request

    • Territory

    • Work Order - (available only in Adaptive Search REST API)

    Enabling an object enables any custom child objects and any custom fields you created. Not all the objects are sales objects. Partner and Partner Contact are only pertinent for Partner Relationship Management. HR Help Desk Request, Internal Service Request, and Service Request are specific to B2B Service. The Case, HR Help Desk Request, Internal Service Request, Product, Product Group, and Work Order objects can be enabled for REST web services only.

    Note: Making the selection on the Quick tab enables the default search configuration. Use the Advanced tab to modify search behavior and to enable custom objects.
  4. By default the objects you enable on the Quick subtab are enabled in the Workspace and global search UIs as well. You can disable objects from appearing in those UIs using the Configure UI and Configure Global Search tabs, but keep them available for REST web services.

  5. Click Publish.

    Your action runs an indexing process and an hourly index refresh for the objects you selected. You can monitor the progress of the indexing process on the Monitor tab. The process can take several minutes to complete, depending on your data volume.

  6. Click the Monitor tab and Publish subtab to monitor the process. After the process completes with a SUCCEEDED status, the Workspace icon appears on the home page. If the process completes with errors, contact your help desk.

Monitor Adaptive Search Background Processes

Adaptive Search requires a number of background processes to run periodically. You can monitor these processes on the Monitor UI tab of the Configure Adaptive Search page.

The Monitor UI tab includes subtabs where you can monitor the processes. The following table describes the processes, provides a recommended run schedule, and explains what actions you can take on each tab.

Note: The recommended schedule for some processes may vary according to your business requirements, existing run assignments, and data load schedules.
Process and Tab Name Process Description Recommended Schedule Available Actions

Periodic Refresh

Indexing enables Adaptive Search to find records based on keyword search terms entered, search filters, saved search criteria, and other search criteria. Periodic Refresh enables Adaptive Search to search for imported records and records that have gone through the mass update process. While records you create and update in the UI are automatically indexed and made searchable within seconds, imported records or records updated by background processes aren't available for search until the process completes.

Note: The Publish process should be completed before running the Periodic refresh.

Every hour

  • Change the process frequency by clicking Schedule Periodic Refresh.

  • Start the process immediately by clicking Start Process.

  • Cancel Process cancels the instance of the process you selected.

Publish

Publishes the Adaptive Search configuration you set up in the Quick Setup and Advanced Setup UIs.

You must click Publish to run the process each time you make changes on the Setup tab.

Your changes become effective when the process completes.

You can monitor the progress of the publish process. Your configuration is live when the process completes successfully.

If the process fails to complete successfully, contact your help desk.

Maintenance

Backs up the current active meta model, removes older snapshots, and cleans up any search server index or snapshots that aren't associated with any workflow state of the meta model.

Note: Restore from Backup is disabled if a meta model is being published.

Daily

You can restore the current active Adaptive Search configuration by clicking Restore from Backup. This action clears any saved changes that aren't yet published.

If you want to restore the last active Adaptive Search configuration version click Revert to Previous Version.

Any other actions should be taken by your help desk.

Territory and Resource Hierarchy Refresh

Updates the index with sales territory and resource hierarchy changes.

Weekly

  • Change the process frequency by clicking Schedule Periodic Refresh.

  • Start the process immediately by clicking Start Process.

  • Cancel Process cancels the instance of the process you selected.

Update Aggregates

Updates the index with aggregate changes.

Weekly or as required.

  • Change the process frequency by clicking Schedule Periodic Refresh.

  • Start the process immediately by clicking Start Process.

  • Cancel Process cancels the instance of the process you selected.

Synchronize Access Rules Data

Updates access group object sharing rules.

Automatically runs when a job, Perform Object Sharing Rule Assignment Processing, or job set is submitted for a batch of access group object sharing rules for all the available assignment objects.

Depending on your requirements, you can change the process frequency by clicking Schedule Periodic Refresh. You can also manually Start or Cancel the process at any time.

How To Change Periodic Refresh Frequency

The default periodic refresh Workspace process runs every hour. However, you may want to change the frequency to run every 15 minutes so that any new records quickly appear in your Workspace saved searches.

Here's how to change the periodic refresh frequency.

  1. Click Navigator > My Enterprise > Setup and Maintenance.

  2. In the Setup and Maintenance work area, go to:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Configure Adaptive Search

  3. From the Configure Adaptive Search page, click Monitor > Periodic refresh.

  4. Select the job row which is currently running hourly and has a status of Wait.

  5. Click Schedule Periodic Refresh.

  6. Click Change Frequency and adjust the schedule to run every 15 minutes or per your specific requirement.

Adaptive Search Meta Models Types

Meta model encodes the information that's necessary to index the entities that are searched. Adaptive Search supports the following meta models, each with a distinct workflow state.

  • Seeded Meta Model

    A ready to use model that's shipped to customers. You can click Restore Defaults to revert to the predefined meta model.

  • Sandbox Meta Model

    A modified version of the Adaptive Search configuration is stored and saved when you make changes to the configuration and click Save or Save and Close.

  • Being Published Meta Model

    When the configuration changes are saved and you click Publish, the meta model is in a state of being published.

  • Active Meta Model

    When the full refresh job is completed successfully, it becomes the active meta model.

  • Archived Meta Model

    The previous successful version of the configuration becomes the archived meta model. There is only one archived version available.

Index Date Ranges for Adaptive Search Objects

Adaptive Search objects are categorized into transactional objects and reference objects. Transactional objects store CX Sales and B2B Service transactions while reference objects don't. The following sections outline how the search records for both types of objects are indexed.

Transactional Objects

When indexing transactional object search records for the first time, Adaptive Search only index records that have the "Last Updated Date" within the last 365 days. Thereafter, records that are modified or created from transactional objects are incrementally added to the index. Here's a list of the Adaptive Search transactional objects:

  • Activities

  • Campaigns

  • Case

  • Deal Registration

  • HR Help Desk Request

  • Internal Service Request

  • Leads

  • Opportunities

  • Quotes and Orders

  • Quote and Order Lines

  • Service Requests

  • Work Order

Note: Adaptive Search transactional object details are updated asynchronously during Near Real-time Indexing. The asynchronous update happens after the objects in the above list are refreshed.

Take a look at the following transactional object examples of what content is indexed for a specific action on a particular date for Opportunity records:

Date Action Index Content

Dec 15, 2018

Publish job is run

Records which have Last Updated Date > Dec 15, 2017

Jan 10, 2019

New Opportunity created with name Green Servers

All previously indexed records plus the new opportunity record (Green Servers) created

Jan 20, 2019

20 new opportunities created by an import job

All previously indexed records plus the 20 new records created (after the periodic refresh job completes)

Reference Objects

All records from the reference objects are indexed. Custom objects are treated as reference objects and hence all of their records are indexed. Here's a list of the Adaptive Search Reference objects:

  • All custom objects

  • Account

  • Asset

  • Contact

  • Partner

  • Partner Contact

  • Product

  • Product Group

  • Territory

You can configure how Adaptive Search works and control how the Workspace interface based on Adaptive Search behaves using the Parameters tab available in the Adaptive Search setup page. Modify the parameters to define the way the Adaptive search engine behaves and runs the search indexing. For example, some of the parameters you can modify include time outs, fetch sizes, maximum number of batches and so on. Based on the server size and other configuration available on a customer pod and the volume of data to be indexed, you can change these parameters so that the indexing process runs successfully.

Among the parameter settings are the ability to enable mass actions and record-level navigation, specify the fuzziness level for search, set the default number of records to be displayed per page, and set the maximum number of records to export at one time. For example, you might want to modify parameter values for the following:

  • Enable Group By in Workspace

  • Enable Mass Actions

  • Enable Mass Update

  • Enable record level navigation

  • Fuzziness Level

  • Maximum Number of Records for Export

  • Number of records displayed per page in Workspace

You can also choose to change current and default values. Here's how to edit Adaptive Search parameters.

  1. Click Navigator > My Enterprise > Setup and Maintenance.

  2. In the Setup and Maintenance work area, go to:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Configure Adaptive Search

  3. On the Configure Adaptive Search page, click the Parameters tab.

    Screenshot of the Edit Adaptive Search Parameters
  4. Highlight the Parameter Name that you want to change and click Edit. This warning is displayed.

    You're about to change parameters that control how Adaptive Search works. Changes should only be carried out by search setup experts. Do you want to continue?

  5. Click Yes.

  6. In the Current Value field, makes the changes that you require and click Save and Close.

This table outlines the list of Adaptive search parameters available and shows the minimum, maximum, and default values.

Parameter Name Description Minimum Value Maximum Value Default Value

Decouple incremental job at the end of Publish

At the end of a Publish process, a periodic refresh is run so that any records updated during the Publish process get updated. By default the decouple parameter is set to N which means that the periodic job is run after the Publish process. Change this parameter to Y if you don't want the periodic process to run.

None

None

N

Enable Group By in Workspace

Enable this parameter to view search results in groups based on the specific fields on the object or related objects. Users get an overview of the number of records in each Grouped By grouping and they can search and filter records within these groupings. Users can also view aggregates such as count, average, and sum of values on the records of each group.

None

None

N

Enable Keyword Highlighting in Workspace

Setting this parameter means that any keywords entered in the Search box are highlighted in the search results returned in Workspace.

None

None

Y

Enable Mass Actions

You can perform some actions on multiple records at the same time. For example, you can select multiple leads in Workspace and qualify them at once by selecting the Qualify action.

None

None

Y

Enable Mass Update

You can update multiple records at the same time. This saves you time and helps improve efficiency. For example, you might want to update the close date for opportunity records at the same time or change the Lead rank from Cool to Warm for a number leads.

None

None

N

Enable record level navigation

You can use Previous and Next buttons on the record details page to navigate lists of records in Workspace.

None

None

Y

Enable Partial Publish

Set this parameter to do a publish on selected set of objects without doing a full publish.

None

None

N

Fuzziness Level

This parameter defines the number of character edits that's considered when a keyword search is performed. For a value of 1, the search term "redwod"" returns Redwood in the search result.

None

Two

One

Lookup Type Cache Concurrency Level

You can configure the Adaptive search lookup caching to build pipelines concurrently when the lookup table or index file is large. The default number of pipelines is 2.

1

10

2

Lookup Type Cache Initial Capacity

Set the initial capacity for the concurrent hash map that's used for the lookup type cache.

16

10000

16

Lookup Type Cache Load Factor

You can modify the cache load factor for the lookup type cache. The default factor is 0.75.

0.5

1.0

0.75

Maximum Age in Days for Production POD

Modify the time limit that you want records to be available for indexing. Records that haven't been updated in the last 365 days in a production POD won't be included in the Publish indexing process.

200

365

365

Maximum Age in Days for Stage POD

Modify the time limit that you want records to be available for indexing in a Stage POD. The default is 90 days.

30

365

90

Maximum Number of Records for Export

This parameter represents the maximum number of records that can be saved to the desktop in a single Export action by users.

1

10000

2000

Maximum number of records that can be selected in Workspace

This parameter enables you to change the maximum number of records that can be selected in Workspace to perform a mass action. The default number is 10 records and you can select up to 25 records.

1

25

10

Minimum Characters to type in Search Box before Suggestions Filters are displayed

This parameter lets you change the minimum number of characters that you must include in the Search box before the suggestion filters are displayed. The default minimum value is 1 character. A value of 0 means the Filter Suggestions display immediately on clicking in the search box.

0

100

1

Number of records displayed per page in Workspace

You can change the number of records displayed on the search results page from the default value of 25 records up to a maximum of 100 records.

1

100

25

Search Filter Limit

Set the number of filters you can include for your search. The default number of filters is 6.

1

10

6

Shard maximum size required for index in GB

This parameter lets you set the shard maximum size for your search index file in gigabytes (GB).

1

9999

45

Initial target shard size required for index in GB

This parameter lets you set the initial target shard size for your search index file. 30 GB is the predefined value.

1

9999

30

You can designate records as favorites so that salespeople can quickly reach them to view and edit the records that they want. Once you enable the favorite field for specific objects, then salespeople can add a filter for favorite records in the Workspace UI to help improve the speed to reach records.

Enable the Favorites field on the object for which you want salespeople to have easy access to frequently used records:

  1. Sign in to the application as a sales administrator or a setup user.

  2. Go to the Configure Adaptive Search task in Setup and Maintenance.

  3. Click Setup and then the Advanced subtab.

  4. Select the business object you want and from the Configure Fields: area, search for the Favorite field.

  5. Select the Enable check box to enable the Favorite field for the selected business object.

  6. Repeat steps 4 and 5 to enable the Favorite fields for all the other business objects.

  7. Click Save and then click Publish.

Once enabled, from the Workspace UI, salespeople can change the columns that display for their search results. For example, they can add the Favorite column to display on the search results page and in what order by clicking Edit Column (the pencil icon).

  1. From the Edit Columns page, search for Favorite.

  2. Select Favorite and move from the Available area to the Selected area.

  3. Click OK.

Those records that are marked as favorites are represented by a color-filled star icon. Those items not marked as favorites have a clear star icon. You can remove and add items to suit your requirements. When selected, the clear star icon changes to a filled star. You can also change the width of the columns by dragging their sides. Your preferences can be saved as part of a saved search.

You can migrate your Adaptive Search configuration along with other configurations from your test environment to your production environment. From the Navigator, select Configuration > Migration. For more detailed information, see the section Moving Application Changes in the Configuring Applications Using Application Composer guide.

To include the Adaptive Search configuration in your configuration migration, select the Workspace Configuration option. Before you migrate any changes, you must ensure that:

  • ZCA_MANAGE_INTERACTIVE_LISTS_SAVED_SEARCH privilege is assigned to your role

  • All changes are published on the target environment.

  • There's no publish job in progress.

An error occurs if a publish job is in progress and if a Configuration Set Migration (CSM) import is triggered. Only migrate changes after your Adaptive Search publish has completed on the target.

Selecting the Workspace Configuration option migrates all of your Adaptive Search configurations except for saved searches you created. You must recreate any custom saved searches in the production environment after the migration is complete.

Trigger the CSM import on the customer environment only when all published jobs are in a successful state. After the successful completion of your CSM migration:

  1. Navigate to your target environment and configure the Workspace UI.

  2. Run a Publish job to ensure that all changes are indexed and available to Workspace.

Note: Don't manually configure the production environment for the features you're migrating.

Oracle provides you with a default Adaptive Search configuration as outlined here. For each of the supported business objects, the table lists:

  • The fields you can add as filters

  • The fields you can search using the Search box at the top of the Workspace UI page or in Global Search

Fields in parentheses can be included as filters. For example, you can filter an account by contact name, primary address, primary phone, and so on.

Business Object Fields Enabled for Use as Filters Fields Enabled for the Search Box

Account

  • Addresses

  • Contacts

    (Name, Primary Address, Primary Email, Primary Phone)

  • Created By

  • Creation Date

  • Emails

  • Industries

  • Instant Messages

  • Last Updated By

  • Last Updated Date

  • Name

  • Organization Types

  • Owner

  • Phones

  • Primary Address

  • Primary Contact

    (Name, Primary Address, Primary Email, Primary Phone)

  • Primary Email

  • Primary Industry

  • Primary Instant Message

  • Primary Organization Type

  • Primary Phone

  • Primary URL

  • Record Set

  • Registry ID

  • Team Members

  • Type

  • URLs

  • Name

  • Primary Address

  • Primary Contact

    (Name, Primary Address, Primary Email, Primary Phone)

  • Primary Email

  • Primary Industry

  • Primary Instant Message

  • Primary Organization Type

  • Primary Phone

  • Primary URL

  • Registry ID

Activity

  • Account (Name, Primary Address)

  • Activity

  • Asset (Asset Number, Serial Number)

  • Call Report Count

  • Consumer

  • Contacts

    (Name, Primary Address, Primary Email, Primary Phone)

  • Created By

  • Creation Date

  • Date

  • Delegated By

  • Description

  • Dismiss

  • Due Date

  • Last Updated By

  • Last Updated Date

  • Lead (Lead Name)

  • Location

  • Meeting Minutes

  • Opportunity (Name)

  • Owner

  • Primary Contact (Name)

  • Priority

  • Private

  • Record Set

  • Start Date

  • Status

  • Subject

  • Team members

  • Type

  • Account (Name, Primary Address)

  • Consumer

  • Description

  • Meeting Minutes

  • Owner

  • Primary Contact

    (Name, Primary Address, Primary Email, Primary Phone)

  • Subject

Asset

  • Account (Name, Primary Address)

  • Asset Name

  • Asset Number

  • Competitor Asset

  • Consumer

  • Contacts

    (Name, Primary Address, Primary Email, Primary Phone)

  • Created By

  • Creation Date

  • Description

  • End Date

  • Install Date

  • Last Updated By

  • Last Updated Date

  • Manufacturer

  • Model

  • Product

  • Product Group

  • Purchase Date

  • Purchase Unit Price

  • Quantity

  • Record Set

  • Serial Number

  • Status

  • Team Members

  • Version

  • Year

  • Account (Name, Primary Address)

  • Asset Name

  • Asset Number

  • Consumer

  • Description

  • Manufacturer

  • Model

  • Product

  • Product Group

  • Serial Number

Campaign

  • Actual Cost

  • Budgeted Cost

  • Campaign Created By

  • Campaign Creation Date

  • Campaign Last Update Date

  • Campaign Last Updated By

  • Campaign Number

  • Created By

  • Created by Module

  • Creation Date

  • Description

  • End Date

  • Last Updated By

  • Last Updated Date

  • Name

  • Owner

  • Parent Campaign

  • Product Description

  • Region Code

  • Source System Campaign ID

  • Start Date

  • Status

  • Total Leads

  • Total Opportunities

  • Total Opportunities Revenue

  • Type (Campaign Number, Name, and Status)

  • Campaign Number

  • Description

  • Name

  • Origin

  • Parent Campaign

  • Source System Campaign ID

  • Status

  • Type

Case

  • Account (Name, Primary Address)

  • Activity ID

  • Actual Start Date

  • Address Line 1

  • Assigned To (Name, Primary Email, Primary Phone)

  • City

  • Contact (Name, Primary Address, Primary Email, Primary Phone)

  • Contact Name

  • Country

  • Created By

  • Creation Date

  • Email

  • Estimated Start Date

  • Favorite

  • Field Service Resource (Name, Primary Email, Primary Phone)

  • Integration

  • Last Updated By

  • Last Updated Date

  • Partner Account (Name, Primary Address)

  • Phone

  • Postal Code

  • Primary Asset (Asset Number, Serial Number)

  • Product (Name)

  • Product Group (Name)

  • Record Set

  • Reference Number

  • Requested Date

  • Requested Date and Start Time

  • Requested Time Slot

  • Resolution Due

  • Scheduled Date

  • Scheduled Date and Start Time

  • Scheduled Time Slot

  • Service Request (Channel Type, Owner Type, Reference Number, Stripe Code, Title)

  • State

  • Status

  • Time Zone

  • Title

  • Work Order Area

  • Work Order Integration Status Code

  • Work Order Status (Status, Status Category)

  • Work Order Type (Work Order Type Code)

  • Reference Number

Contact

  • Affinity

  • Annual Income

  • Buying Role

  • Contact Role

  • Created By

  • Creation Date

  • First Name

  • Job Title

  • Last Contact Date

  • Last Name

  • Last Updated By

  • Last Updated Date

  • Middle Name

  • Name

  • Owner

  • Preferred Contact Method

  • Primary Account (Name, Primary Address)

  • Registration Status

  • Sales Profile Status

  • Type

  • Accounts (Name, Primary Address)

  • Addresses

  • Emails

  • Instant Messages

  • Phones

  • Primary Address

  • Primary Email

  • Primary Instant Message

  • Primary Phone

  • Primary URL

  • Record Set

  • Team Members

  • URLs

  • First Name

  • Job Title

  • Last Name

  • Middle Name

  • Name

  • Primary Address

  • Primary Email

  • Primary Instant Message

  • Primary Phone

  • Primary URL

Deal Registration

  • Approval Decision By (Name, Primary Email, Primary Phone)

  • Approval Decision Date

  • Close Date

  • Contact Email

  • Contact First Name

  • Contact Last Name

  • Created By

  • Creation Date

  • Deal Products (Name)

  • Deal Size

  • Deal Type

  • Existing Account (Name, Primary Address, Registry ID)

  • Existing Contact (Do not call, Do not contact, Do not email, Do not mail, Name, Primary Address, Primary Email, Primary Phone)

  • Expiration Date

  • Job Title

  • Last Completed Activity

  • Last Completed Call Activity

  • Last Completed Email Activity

  • Last Updated By

  • Last Updated Date

  • Lead (Lead Name)

  • Name

  • New Account

  • New Contact

  • Next Task Due

  • Number of Completed Activities

  • Number of Completed Call Activities

  • Number of Completed Email Activities

  • Number of Products

  • Number of Team Members

  • Opportunity (Name)

  • Opportunity Account (Account Name, Name, Primary Address)

  • Opportunity Contact (Do not call, Do not contact, Do not email, Do not mail, Name, Primary Address, Primary Email, Primary Phone)

  • Owner (Name, Primary Email, Primary Phone)

  • Partner (Name, Partner Number, Primary Address, Public Address ID, Public Email ID, Public Fax ID, Public Phone ID)

  • Partner Type

  • Record Set

  • Registration Number

  • Rejected Comments

  • Rejected Reason

  • Returned Comments

  • Returned Reason

  • Status

  • Submitted By (Name, Primary Email, Primary Phone)

  • Submitted Date

  • Team Members (Name, Primary Email, Primary Phone)

  • Registration Number

  • Existing Contact (Name)

  • Existing Account (Name, Primary Address, Registry ID)

  • Partner (Name, Partner Number, Primary Address)

  • Status

HR Help Desk Request

  • Assigned To (Name, Primary Email, Primary Phone)

  • Category Name

  • Channel Type

  • Contact (Do not call, Do not contact, Do not email, Do not mail, Name, Primary Address, Primary Email, Primary Phone)

  • Created By

  • Creation Date

  • Critical

  • Date Closed

  • Date Reported

  • Language Code

  • Last Updated By

  • Last Updated Date

  • Messages (Channel Type, Message Content, Posted By)

  • Outcome Problem

  • Owner Type

  • Problem Description

  • Product (Name)

  • Product Group (Name)

  • Queue (Queue Name)

  • Record Set

  • Reference Number

  • Reported By (Name, Primary Email, Primary Phone)

  • Resolution Code

  • Resolution Date

  • Resolved By

  • Severity

  • Solution Description

  • Status Team Members (Name, Primary Email, Primary Phone) Title

  • Status Type

  • Stripe Code

  • Team Members (Name, Primary Email, Primary Phone)

  • Title

  • Contact (Name)

  • Reference Number

Internal Service Request

  • Assigned To (Name, Primary Email, Primary Phone)

  • Category Name

  • Channel Type

  • Contact (Do not call, Do not contact, Do not email, Do not mail, Name, Primary Address, Primary Email, Primary Phone)

  • Created By

  • Creation Date

  • Critical

  • Date Closed

  • Date Reported

  • Language Code

  • Last Updated By

  • Last Updated Date

  • Messages (Channel Type, Message Content, Posted By)

  • Outcome Problem

  • Owner Type

  • Problem Description

  • Product (Name)

  • Product Group (Name)

  • Queue (Queue Name)

  • Record Set

  • Reference Number

  • Reported By (Name, Primary Email, Primary Phone)

  • Resolution Code

  • Resolution Date

  • Resolved By

  • Severity

  • Solution Description

  • Status Team Members (Name, Primary Email, Primary Phone) Title

  • Status Type

  • Stripe Code

  • Team Members (Name, Primary Email, Primary Phone)

  • Title

  • Contact (Name)

  • Reference Number

Lead

  • Accepted Date

  • Account (Name, Primary Address)

  • Consumer

  • Contacts (Name, Primary Address, Primary Email, Primary Phone)

  • Conversion Reason

  • Created By

  • Creation Date

  • Deal Size

  • Estimated Close Date

  • Existing Contact (Name, Primary Address, Primary Email, Primary Phone)

  • Last Updated By

  • Last Updated Date

  • Lead Name

  • Lead Number

  • Owner

  • Primary Product

  • Primary Product Group

  • Products

  • Qualification Date

  • Rank

  • Reassign Reason

  • Record Set

  • Score

  • Source

  • Status

  • Team Members

  • Account (Name, Primary Address)

  • Consumer

  • Existing Contact (Name, Primary Address, Primary Email, Primary Phone)

  • Lead Name

  • Rank

Opportunity

  • Account (Name, Primary Address)

  • Asset (Asset Number, Serial Number)

  • Close Date

  • Consumer

  • Contacts (Name, Primary Address, Primary Email, Primary Phone)

  • Created By

  • Creation Date

  • Last Updated By

  • Last Updated Date

  • Leads (Lead Name)

  • Line of Business

  • Name

  • Owner

  • Primary Contact (Name, Primary Address, Primary Email, Primary Phone)

  • Primary Revenue

  • Record Set

  • Revenues

  • Sales Stage

  • Status Category

  • Team Members

  • Line of Business

  • Name

  • Primary Revenue

Partner

  • Addresses

  • Created By

  • Creation Date

  • Emails

  • Last Updated By

  • Last Updated Date

  • Level

  • Name

  • Owner (Name, Primary E-Mail, Primary Phone)

  • Parent Partner (Name, Owner, Partner Number, Primary Address)

  • Partner Contacts

  • Partner Number

  • Partner Types

  • Phones

  • Primary Address (Address, City, Country, State)

  • Primary Contact (Name, Primary Address, Primary E-Mail, Primary Phone)

  • Primary E-Mail

  • Primary Phone

  • Primary URL

  • Record Set

  • Registry ID

  • Status

  • Team Members

  • URLs

  • Name

  • Partner Number

  • Primary Address

  • Primary Contact (First Name, Last Name, Middle Name, Name, Primary Address, Primary E-Mail, Primary Phone, Primary URL)

  • Primary E-Mail

  • Primary Phone

  • Primary URL

Partner Contacts

  • Addresses

  • Certification Level

  • Certification Reason

  • Comments

  • Created By

  • Creation Date

  • Department

  • Department Code

  • Duplicate Type

  • Emails

  • Enrichment Status

  • First Name

  • Internal Job

  • Title

  • Last Assigned Date

  • Last Contact Date

  • Last Known Location

  • Last Name

  • Last Updated By

  • Last Updated Date

  • Middle Name

  • Name Partner (Name, Owner, Partner Number, Primary Address)

  • Phones

  • Primary Address (Address, City, Country, State)

  • Primary E-Mail

  • Primary Phone

  • Primary URL

  • Record Set

  • Registration Status

  • Title

  • URLs

  • First Name

  • Last Name

  • Middle Name

  • Name

  • Primary Address

  • Primary E-Mail

  • Primary Phone

  • Primary URL

Quotes and Orders

  • Account (Name, Primary Address)

  • Active

  • Amount

  • Contact (Name, Primary Address, Primary Email, Primary Phone)

  • Created By

  • Creation Date

  • Description

  • Last Synchronized

  • Last Updated By

  • Last Updated Date

  • Name

  • Opportunity (Name)

  • Owner

  • Placed On

  • Quote ID

  • Quote or Order Number

  • Record Set

  • Reference Code

  • Reference Number

  • Status

  • Valid To Date

  • Version

  • Win Status

  • Name

  • Quote or Order Number

Quote and Order Line

  • Account (Name, Primary Address)

  • Contact (Name, Primary Address, Primary Email, Primary Phone)

  • Created By

  • Creation Date

  • Last Updated By

  • Last Updated Date

  • Line Amount

  • Line Contract End Date

  • Line Contract Value

  • Line Discount

  • Line Price Period

  • Line Price Type

  • Line Request Date

  • Line Status

  • Opportunity (Name, Opportunity Number, Status)

  • Order Line Item

  • Product Name

  • Record Set

  • Sales Orders (Active, Creation Date, Valid To Date, Name, Quote or Order Number, Amount, Status, Win Status)

  • Account

  • Contact

  • Opportunity

  • Order Line Item

  • Product Name

  • Record Set

  • Sales Orders

Service Requests

  • Account (Name, Primary Address)

  • Asset (Asset Number, Serial Number)

  • Assigned To (Name, Primary Email, Primary Phone)

  • Category Name

  • Channel Type

  • Contacts (Name, Primary Address, Primary Email, Primary Phone, Registry ID)

  • Created By

  • Creation Date

  • Critical

  • Date Closed

  • Date Reported

  • Language Code

  • Last Updated By

  • Last Updated Date

  • Messages (Channel Type, Message Content)

  • Outcome

  • Owner Type

  • Primary Contact (Name, Primary Address, Primary Email, Primary Phone, Registry ID)

  • Problem Description

  • Product (Name)

  • Product Group (Name)

  • Queue (Queue Name)

  • Record Set

  • Reference Number

  • Reported By (Name, Primary Email, Primary Phone)

  • Resolution Code

  • Resolution Date

  • Resolved By

  • Severity

  • Solution Description

  • Status

  • Stripe Code

  • Team Members (Name, Primary Email, Primary Phone)

  • Title

  • Account (Name, Primary Address)

  • Consumer (Name, Primary Address, Primary Email, Primary Phone)

  • Primary Contact (Name, Primary Address, Primary Email, Primary Phone)

  • Reference Number

Territory

  • Coverage

    • Account Name

    • Account Type

    • Coverage Type

    • Geography

    • Coverage Model

    • Aux1

    • Aux2

    • Aux3

    • Customer Size

    • City

    • Country

    • State

    • Province

    • County

    • Postal Code

    • Additional Attribute 1

    • Additional Attribute 2

    • Additional Attribute 3

    • Additional Attribute 4

    • Additional Attribute 5

    • Product Group

    • Item

    • Inventory Organization

    • Industry

    • Organization Type

    • Sales Channel

    • Sales Subchannel

    • Business Unit

  • Coverage Model

  • Created By

  • Creation Date

  • Description

  • Eligible for Quota

  • Forecast Participation Code

  • Function

  • Last Updated By

  • Last Updated Date

  • Leaf Territory

  • Line of Business

  • Name

  • Owner

  • Parent Territory

  • Parent Territory Number

  • Parent Territory Unique Number

  • Partner (Name, Partner Number, Primary Address, Public Address ID, Public Email ID, Public Fax ID, Public Phone ID)

  • Partner ID

  • Team Members (Name, Primary Email, Primary Phone)

  • Territory ID

  • Territory Number

  • Type

  • Unique Territory Number

  • Description

  • Function

  • Name

  • Owner

  • Parent Territory

  • Parent Territory Number

  • Parent Territory Unique Number

  • Partner ID

  • Territory ID

  • Territory Number

  • Type

  • Coverage

    • Account Name

    • Account Type

    • Coverage Type

    • Geography

    • Coverage Model

    • Aux1

    • Aux2

    • Aux3

    • Customer Size

    • City

    • Country

    • State

    • Province

    • County

    • Postal Code

    • Additional Attribute 1

    • Additional Attribute 2

    • Additional Attribute 3

    • Additional Attribute 4

    • Additional Attribute 5

    • Product Group

    • Item

    • Inventory Organization

    • Industry

    • Organization Type

    • Sales Channel

    • Sales Subchannel

    • Business Unit

Work Order

  • Assignee Party Name (Name, Primary Email, Primary Phone)

  • Case Category ID

  • Case Message

  • Case Number

  • Case Opportunity (Name)

  • Case Resource (Name, Primary Email, Primary Phone)

  • Closed Date

  • Contacts (Name, Primary Address, Primary Email, Primary Phone)

  • Created By

  • Creation Date

  • Description

  • Favorite

  • Last Updated By

  • Last Updated Date

  • Open Date

  • Primary Contact Party ID

  • Queue ID

  • Reported by Party Name (Name, Primary Email, Primary Phone)

  • Title

  • Case Number

This topic lists the standalone data security predicates predefined for each of the business objects supported by Adaptive Search. Data security predicates provide access to object data, the access type, and the data to be accessed. The data to be accessed can be All, a specific record, or a subset of the data.

Note: Adaptive Search doesn't support the use of custom data security policies. Customers must use Access Groups instead as described in the Securing CX Sales and B2B Service guide.

The instance set defines the subset of data that limits the condition part of the data resource. For more information, see the Manage Database Resources section of the Securing CX Sales and B2B Service guide.

ACCOUNT

This table lists the instance set name and associated description for the Account business object:

Instance Set Name Instance Set Description

HZPARTIESHZ197

Access the trading community organization for table HZ_PARTIES for a trading community organization that's a partner and the user is a member of the partner organization.

HZPARTIESZBS100105

Access the sales party for table HZ_PARTIES where they're in the management chain of the account owner.

HZPARTIESZBS100106

Access the sales party for table HZ_PARTIES where they're the account owner.

HZPARTIESZCM1

Access the sales party for table HZ_PARTIES where user is in the sales account team.

HZPARTIESZCM133

Access the sales party for table HZ_PARTIES for all prospects in the enterprise.

HZPARTIESZCM134

Access the sales party for table HZ_PARTIES for all customers in the enterprise.

HZPARTIESZCM3

Access the sales party for table HZ_PARTIES where user is in the management chain of a resource who's on the sales account team.

HZPARTIESZCM39

Access the sales party for table HZ_PARTIES where user is a member of the territory associated with the sales account.

HZPARTIESZCM4

Access the sales party for table HZ_PARTIES where user is in the sales account team with edit access.

HZPARTIESZCM40

Access the sales party for table HZ_PARTIES where user is a member of the territory that's an ancestor of the territory associated with the sales account.

HZPARTIESZCM44

Access the sales party for table HZ_PARTIES where user is in the management chain of a resource who's on the sales account team with edit access.

HZPARTIESZCM45

Access the sales party for table HZ_PARTIES where user is in the sales account team with full access.

HZPARTIESZCM46

Access the sales party for table HZ_PARTIES where user is in the management chain of a resource who's on the sales account team with full access.

HZPARTIESZCM51

Access the sales party for table HZ_PARTIES where user is the owner of the territory associated with the sales account.

HZPARTIESZCM52

Access the sales party for table HZ_PARTIES where user is the owner of the territory that's an ancestor of the territory associated with the sales account.

HZPARTIESZCA99968

Access the accounts where they're in access groups.

ACTIVITY

This table lists the instance set name and associated description for the Activity business object:

Instance Set Name Instance Set Description

ZMMACTYACTIVITIESZMM1398

Access the activity for table ZMM_ACTY_ACTIVITIES where they're only an owner of an activity (1=1).

ZMMACTYACTIVITIESZMM1399

Access the activity for table ZMM_ACTY_ACTIVITIES where they're only a delegator of an activity (1=1).

ZMMACTYACTIVITIESZMM1400

Access the activity for table ZMM_ACTY_ACTIVITIES where they're in the management chain of an owner only of an activity.

ZMMACTYACTIVITIESZMM1401

Access the activity for table ZMM_ACTY_ACTIVITIES where they're in the management chain of a delegator only of an activity.

ZMMACTYACTIVITIESZMM1402

Access the activity for table ZMM_ACTY_ACTIVITIES where they're only a resource of an activity.

ZMMACTYACTIVITIESZMM1403

Access the activity for table ZMM_ACTY_ACTIVITIES where they're in the management chain of a resource only of an activity.

ZMMACTYACTIVITIESZMM1404

Access the activity for table ZMM_ACTY_ACTIVITIES where they're the owner of an account associated with an activity.

ZMMACTYACTIVITIESZMM1405

Access the activity for table ZMM_ACTY_ACTIVITIES where they're on the sales account team and the sales account activity that's in their management hierarchy.

ZMMACTYACTIVITIESZMM1406

Access the activity for table ZMM_ACTY_ACTIVITIES where they're on the sales account territory and the sales account activity that's in their territory hierarchy.

ZMMACTYACTIVITIESZMM1408

Access the activity for table ZMM_ACTY_ACTIVITIES where they're on the opportunity team and the opportunity activity that's in their management hierarchy.

ZMMACTYACTIVITIESZMM1409

Access the activity for table ZMM_ACTY_ACTIVITIES where they're on the opportunity territory and the opportunity activity that's in their territory hierarchy.

ZMMACTYACTIVITIESZMM1410

Access the activity for table ZMM_ACTY_ACTIVITIES where they're on the lead team and the lead activity that's in their management hierarchy.

ZMMACTYACTIVITIESZMM1411

Access the activity for table ZMM_ACTY_ACTIVITIES where they're on the lead territory and the lead activity that's in their territory hierarchy.

ZMMACTYACTIVITIESZMM47

Access the activity for table ZMM_ACTY_ACTIVITIES for all template activities in the enterprise.

ZMMACTYACTIVITIESZMM48

Access the activity for table ZMM_ACTY_ACTIVITIES where they're either a resource or a delegator of an activity.

ZMMACTYACTIVITIESZMM49

Access the activity for table ZMM_ACTY_ACTIVITIES where they're either a resource or a delegator of a task or an owner or a delegator of an appointment or an owner or a delegator of a call report activity.

ZMMACTYACTIVITIESZMM50

Access the activity for table ZMM_ACTY_ACTIVITIES where they're either the owner or a delegator of an activity.

ZMMACTYACTIVITIESZMM51

Access the activity for table ZMM_ACTY_ACTIVITIES where they're in the management chain of an activity resource.

ZMMACTYACTIVITIESZMM52

Access the activity for table ZMM_ACTY_ACTIVITIES where they're in the management chain for a task activity or they're an owner for an appointment activity.

ZMMACTYACTIVITIESZMM53

Access the activity for table ZMM_ACTY_ACTIVITIES where they're in the management chain of the activity owner.

ZMMACTYACTIVITIESZMM54

Access the activity for table ZMM_ACTY_ACTIVITIES for all activities in the enterprise.

ZMMACTYACTIVITIESZMM74

Access the activity for table ZMM_ACTY_ACTIVITIES where they're a participant on the activity.

ZMMACTYACTIVITIESZMM75

Access the activity for table ZMM_ACTY_ACTIVITIES where they're either a resource or a delegator of a task or an owner or a delegator of an appointment or a call report activity.

ZMMACTYACTIVITIESZMM76

Access the activity for table ZMM_ACTY_ACTIVITIES where partner users are resources in the activity.

ZMMACTYACTIVITIESZMM77

Access the activity for table ZMM_ACTY_ACTIVITIES can edit all activities where users from their partner company are participating.

ZMMACTYACTIVITIESZMM1413

Access the activity for table ZMM_ACTY_ACTIVITIES where they're in the management chain of a resource for the primary contact of an activity.

ZMMACTYACTIVITIESZMM1414

Access the activity for table ZMM_ACTY_ACTIVITIES where they're member of a partner territory.

ASSET

This table lists the instance set name and associated description for the Asset business object:

Instance Set Name Instance Set Description

ZCAASSETZCM213

Access the Asset for table ZCA_ASSET where user is a sales party team member of the asset owner party.

ZCAASSETZCM214

Access the Asset for table ZCA_ASSET where user is in the management chain of a resource who's a sales party team member of the asset owner party.

ZCAASSETZCM215

Access the Asset for table ZCA_ASSET where user is a member of the territory associated with the asset owner party.

ZCAASSETZCM216

Access the Asset for table ZCA_ASSET where user is a member of the territory that's an ancestor of the territory associated with the asset owner party.

ZCAASSETZCM224

Access the Asset for table ZCA_ASSET where user is in the management chain of a resource who's a sales party team member of the asset owner party with edit access.

ZCAASSETZCM228

Access the Asset for table ZCA_ASSET where user is in the management chain of a resource who's a sales party team member of the asset owner party with full access.

ZCAASSETZCM252

Access the Asset for table ZCA_ASSET where user is owner of the territory associated with the asset owner party.

ZCAASSETZCM253

Access the Asset for table ZCA_ASSET where user is a owner of the territory that's an ancestor of the territory associated with the asset owner party.

ZCAASSETZCM254

Access the Asset for table ZCA_ASSET where user is a sales party team member of the asset owner party with edit access.

ZCAASSETZCM255

Access the Asset for table ZCA_ASSET where user is a sales party team member of the asset owner party with full access.

ZCAASSETZCM266

Access the Asset for table ZCA_ASSET all assets in the enterprise where asset owner party is a prospect.

ZCAASSETZCM268

Access the Asset for table ZCA_ASSET all assets in the enterprise where asset owner party is a customer.

CASE

This table lists the instance set name and associated description for the Case business object:

Instance Set Name Instance Set Description

SVCCASESSVC330

Access the cases for table SVC_CASES where the case is assigned to them or their subordinate.

SVCCASEMESSAGESSVC322

Access the case messages for table SVC_CASE_MESSAGES where they're the creator of a message.

CONTACT

This table lists the instance set name and associated description for the Contact business object:

Instance Set Name Instance Set Description

HZPARTIESHZ196

Access the trading community person for table HZ_PARTIES for all people in the enterprise (1=1).

HZPARTIESHZ198

Access the trading community person for table HZ_PARTIES for their trading community person record.

HZPARTIESHZ199

Access the trading community person for table HZ_PARTIES for all persons who are a member of their partner organization.

HZPARTIESZBS100105

Access the sales party for table HZ_PARTIES where they're in the management chain of the account owner.

HZPARTIESZBS100106

Access the sales party for table HZ_PARTIES where they're the account owner.

HZPARTIESZBS100108

Access the sales party for table HZ_PARTIES for all customer contacts where they're in the management chain of a resource who's on the account team of at least one related account.

HZPARTIESZBS100116

Access the sales party for table HZ_PARTIES for all customer contacts where they're a member of a territory associated with at least one related account.

HZPARTIESZBS100118

Access the sales party for table HZ_PARTIES for all customer contacts where they're a member of an ancestor territory to a territory associated with at least one related account.

HZPARTIESZBS100119

Access the sales party for table HZ_PARTIES for all customer contacts where they're in the management chain of a resource who's on the account team of at least one related account with full access.

HZPARTIESZBS100120

Access the sales party for table HZ_PARTIES for all customer contacts where they're in the management chain of a resource who's on the account team of at least one related account with edit access.

HZPARTIESZCM1

Access the sales party for table HZ_PARTIES where user is in the sales account team.

HZPARTIESZCM133

Access the sales party for table HZ_PARTIES for all prospects in the enterprise.

HZPARTIESZCM134

Access the sales party for table HZ_PARTIES for all customers in the enterprise.

HZPARTIESZCM169

Access the sales party for table HZ_PARTIES for all customer contacts where they're in the account team of at least one related account with edit access.

HZPARTIESZCM170

Access the sales party for table HZ_PARTIES for all customer contacts where they're in the account team of at least one related account with full access.

HZPARTIESZCM173

Access the sales party for table HZ_PARTIES for all customer contacts where they're in the account team of at least one related account.

HZPARTIESZCM3

Access the sales party for table HZ_PARTIES where user is in the management chain of a resource who's on the sales account team.

HZPARTIESZCM39

Access the sales party for table HZ_PARTIES where user is a member of the territory associated with the sales account.

HZPARTIESZCM4

Access the sales party for table HZ_PARTIES where user is in the sales account team with edit access.

HZPARTIESZCM40

Access the sales party for table HZ_PARTIES where user is a member of the territory that's an ancestor of the territory associated with the sales account.

HZPARTIESZCM44

Access the sales party for table HZ_PARTIES where user is in the management chain of a resource who's on the sales account team with edit access.

HZPARTIESZCM45

Access the sales party for table HZ_PARTIES where user is in the sales account team with full access.

HZPARTIESZCM46

Access the sales party for table HZ_PARTIES where user is in the management chain of a resource who's on the sales account team with full access.

HZPARTIESZCM51

Access the sales party for table HZ_PARTIES where user is the owner of the territory associated with the sales account.

HZPARTIESZCM52

Access the sales party for table HZ_PARTIES where user is the owner of the territory that's an ancestor of the territory associated with the sales account.

HZPARTIESZCM158

Access the Contacts with one party usage.

HZPARTIESZCM415

Access the Contacts which aren't created by Partner User.

HZPARTIESZCA99972

Access the Contacts where they're in access groups.

CUSTOM

This table lists the instance set name and associated description for the Custom object business object:

Instance Set Name Instance Set Description

ZCX_OWNER_[OBJECT_NAME]

Access the Custom Object where the user is Owner of the Custom Object.

ZCX_MGR_HIER_[OBJECT_NAME]

Access the Custom Object where the user is in management chain of the Owner of the Custom Object

DEAL REGISTRATION

This table lists the instance set name and associated description for the Deal Registration business object:

Instance Set Name Instance Set Description

MKLDMDEALSMKL1500

Access the deal registration summary for table MKL_DM_DEALS for all deal registrations in the enterprise.

MKLDMDEALSMKL4021

Access the deal registration summary for table MKL_DM_DEALS where they're a resource on the deal team with view, edit or full access.

MKLDMDEALSMKL5049

Access the deal registration summary for table MKL_DM_DEALS where they're in the partner organization.

MKLDMDEALSZCA100002

Access the deal registration summary for table MKL_DM_DEALS a member of an access group associated with the deal registration.

HR HELP DESK REQUEST

This table lists the instance set name and associated description for the HR Help Desk Request business object:

Instance Set Name Instance Set Description

SVCSERVICEREQUESTSSVC460

Access the service request header for table SVC_SERVICE_REQUESTS for all HRHD service requests(1=1).

SVCSERVICEREQUESTSSVC489

Access the service request header for table SVC_SERVICE_REQUESTS where they're the primary contact of the HRHD service request.

SVCSERVICEREQUESTSSVC514

Access the service request header for table SVC_SERVICE_REQUESTS where the HRHD service request is assigned to them.

SVCSERVICEREQUESTSSVC486

Access the service request header for table SVC_SERVICE_REQUESTS where they created the HRHD service request.

SVCSERVICEREQUESTSSVC515

Access the service request header for table SVC_SERVICE_REQUESTS where they're a member of HRHD service request team.

SVCSERVICEREQUESTSSVC519

Access the service request header for table SVC_SERVICE_REQUESTS where the HRHD service request is assigned to them or their subordinate.

SVCSERVICEREQUESTSSVC520

Access the service request header for table SVC_SERVICE_REQUESTS where they or their subordinate is a member of HRHD service request team.

SVCSERVICEREQUESTSSVC516

Access the service request header for table SVC_SERVICE_REQUESTS where the HRHD service request is assigned to a queue that they're a member.

SVCSERVICEREQUESTSSVC476

Access the service request header for table SVC_SERVICE_REQUESTS where the HRHD service request is assigned to a queue that they or their subordinate is a member.

INTERNAL SERVICE REQUEST

This table lists the instance set name and associated description for the Internal Service Request business object:

Instance Set Name Instance Set Description

SVCSERVICEREQUESTSSVC273

Access the service request header for table SVC_SERVICE_REQUESTS for all internal help desk service requests (1=1).

SVCSERVICEREQUESTSSVC289

Access the service request header for table SVC_SERVICE_REQUESTS where the internal help desk service request is assigned to them or their subordinate.

SVCSERVICEREQUESTSSVC290

Access the service request header for table SVC_SERVICE_REQUESTS where they're the primary contact of the internal help desk service request.

SVCSERVICEREQUESTSSVC311

Access the service request header for table SVC_SERVICE_REQUESTS where the internal help desk service request is assigned to them.

SVCSERVICEREQUESTSSVC291

Access the service request header for table SVC_SERVICE_REQUESTS where they created the internal help desk service request.

SVCSERVICEREQUESTSSVC312

Access the service request header for table SVC_SERVICE_REQUESTS where they're a member of internal help desk service request team.

SVCSERVICEREQUESTSSVC292

Access the service request header for table SVC_SERVICE_REQUESTS where they or their subordinate is a member of internal help desk service request team.

SVCSERVICEREQUESTSSVC310

Access the service request header for table SVC_SERVICE_REQUESTS where the internal help desk service request is assigned to a queue that they're a member.

SVCSERVICEREQUESTSSVC288

Access the service request header for table SVC_SERVICE_REQUESTS where the internal help desk service request is assigned to a queue that they or their subordinate is a member of HRHD Service Request.

LEAD

This table lists the instance set name and associated description for the Lead business object:

Instance Set Name Instance Set Description

MKLLMLEADSMKL1

Access the sales lead for table MKL_LM_LEADS where they're a resource in the lead sales team.

MKLLMLEADSMKL10

Access the sales lead for table MKL_LM_LEADS where they're a resource in the territory assigned to the sales lead.

MKLLMLEADSMKL104

Access the sales lead for table MKL_LM_LEADS where they're the owner of the sales lead.

MKLLMLEADSMKL114

Access the sales lead for table MKL_LM_LEADS where they're a resource in the lead sales team with full access.

MKLLMLEADSMKL129

Access the sales lead for table MKL_LM_LEADS where they're a territory resource in the sales lead territory team or a territory resource with a descendant territory in the sales lead territory team.

MKLLMLEADSMKL138

Access the sales lead for table MKL_LM_LEADS for all retired leads in the enterprise.

MKLLMLEADSMKL148

Access the sales lead for table MKL_LM_LEADS for all partner leads in the enterprise.

MKLLMLEADSMKL15

Access the sales lead for table MKL_LM_LEADS where they're a manager in the management hierarchy of a resource in the lead sales team with full access.

MKLLMLEADSMKL152

Access the sales lead for table MKL_LM_LEADS for all sales leads in the business units that they're authorized.

MKLLMLEADSMKL16

Access the sales lead for table MKL_LM_LEADS where they're a manager in the management hierarchy of the owner of the sales lead.

MKLLMLEADSMKL22

Access the sales lead for table MKL_LM_LEADS where they're a manager in the management hierarchy of a resource in the lead sales team.

MKLLMLEADSMKL310

Access the sales lead for table MKL_LM_LEADS where they're in the management hierarchy of the owner of the lead.

MKLLMLEADSZBS902

Access the sales lead for table MKL_LM_LEADS where they're member or in management chain of lead sales team, member of territory team or upward territory hierarchy.

MKLLMLEADSZCA99964

User can view lead for their access groups.

OPPORTUNITY

This table lists the instance set name and associated description for the Opportunity business object:

Instance Set Name Instance Set Description

MOOOPTYMOO119

Access the opportunity for table MOO_OPTY for the selected records where I am on the team on the sales UI.

MOOOPTYMOO120

Access the opportunity for table MOO_OPTY for the selected records I own on the sales UI.

MOOOPTYMOO121

Access the opportunity for table MOO_OPTY for the selected records my subordinates own on the sales UI.

MOOOPTYMOO122

Access the opportunity for table MOO_OPTY for the selected records where my subordinates are on the team on the sales U1.

MOOOPTYMOO123

Access the opportunity for table MOO_OPTY for the selected records in my territory on the sales UI.

MOOOPTYMOO124

Access the opportunity for table MOO_OPTY for the selected records in my territory hierarchy on the sales UI.

MOOOPTYMOO88

Access the opportunity for table MOO_OPTY for all opportunities in the enterprise (1=1).

MOOOPTYZBS99903

Access the opportunity for table MOO_OPTY where they're a member or in a management chain of opportunity sales team with view, edit or full access, member of territory team or upward territory hierarchy.

MOOOPTYZBS99904

Access the opportunity for table MOO_OPTY where they're a member or in management chain of opportunity account team, account territory team or upward territory hierarchy.

MOO_OPTYACCTERR_HIER_RES

Access the opportunity for table MOO_OPTY where they're a territory resource in the opportunity sales account territory team or a territory resource with a descendant territory in the opportunity sales account territory team.

MOO_OPTY_ADMIN_SALES_ADMIN

Access the opportunity for table MOO_OPTY for all opportunities in the business units that they're authorized within.

MOO_OPTY_EDIT_OPTYTEAM_MGR

Access the opportunity for table MOO_OPTY where they're in the management chain of an opportunity sales team member with edit or full access.

MOO_OPTY_EDIT_OPTYTEAM_REPS

Access the opportunity for table MOO_OPTY where they're an opportunity sales team member with edit or full access.

MOO_OPTY_FULL_OPTYTEAM_MGR

Access the opportunity for table MOO_OPTY where they're in the management chain of an opportunity sales team member with full access.

MOO_OPTY_FULL_OPTYTEAM_REPS

Access the opportunity for table MOO_OPTY where they're an opportunity sales team member with full access.

MOO_OPTY_TERR_HIER_RES

Access the opportunity for table MOO_OPTY where they're a territory resource in the opportunity territory team or a territory resource with a descendant territory in the opportunity territory team.

MOO_OPTY_VIEW_ACCTTEAM_MGR

Access the opportunity for table MOO_OPTY where they're in the management chain of an opportunity sales account team member.

MOO_OPTY_VIEW_ACCTTEAM_REPS

Access the opportunity for table MOO_OPTY where they're a member of the opportunity sales account team.

MOO_OPTY_VIEW_OPTYTEAM_MGR

Access the opportunity for table MOO_OPTY where they're in the management chain of an opportunity sales team member with view, edit, or full access.

MOO_OPTY_VIEW_OPTYTEAM_REPS

Access the opportunity for table MOO_OPTY where they're an opportunity sales team member with view, edit, or full access.

MOOOPTYZCA99962

User can view Opportunities where they're in access groups.

PARTNER

This table lists the instance set name and associated description for the Partner business object:

Instance Set Name Instance Set Description

HZPARTIESHZ521

Access the Partner where the user is the owner of the Partner Account.

HZPARTIESHZ522

Access the Partner where the user is in management chain of the owner of the Partner Account.

HZPARTIESHZ523

Access the Partner where the user is a member of the Partner Account team.

HZPARTIESHZ524

Access the Partner where the user is in management chain of the member of the Partner Account team.

HZPARTIESHZ525

Access the Partner where the user is an owner or member of the Territory assigned to the Partner Account.

HZPARTIESHZ526

Access the Partner where the user is a member of the territory and a descendant territory is assigned to the Partner Account.

HZPARTIESHZ197

Access the Partner where user is a member of partner organization.

HZPARTIESZCA99978

User can view Partner where they're in access groups.

PARTNER CONTACT

This table lists the instance set name and associated description for the Partner Contact business object:

Instance Set Name Instance Set Description

HZPARTIESHZ530

Access the Partner Contact where the user is a member of the Partner Account team.

HZPARTIESHZ531

Access the Partner Contact where the user is in management chain of the member of the Partner Account team.

HZPARTIESHZ532

Access the Partner Contact where the user is Owner of the Partner Account.

HZPARTIESHZ533

Access the Partner Contact where the user is in management chain of the Owner of Partner Account.

HZPARTIESHZ534

Access the Partner Contact where the user is a member of the Territory assigned to the Partner Account.

HZPARTIESHZ535

Access the Partner Contact where the user is a member of the territory and a descendant territory is assigned to the Partner Account.

QUOTES AND ORDERS

This table lists the instance set name and associated description for the Quotes and Orders business object:

Instance Set Name Instance Set Description

ZCASALESORDERHEADERSZBS999939

Access the sales order for table ZCA_SALES_ORDER_HEADERS where they're a member or in management chain of associated opportunity sales team with view, edit or full access, member of territory team or upward territory hierarchy.

ZCASALESORDERHEADERSZBS999941

Access the sales order for table ZCA_SALES_ORDER_HEADERS where they're member or in management chain of associated opportunity account team, account territory team or upward territory hierarchy.

ZCASALESORDERHEADERSZBS999948

Access the sales order for table ZCA_SALES_ORDER_HEADERS for all associated opportunities in the business units that they're authorized within 1=1.

ZCASALESORDERHEADERSZPM5322

Access the sales order for table ZCA_SALES_ORDER_HEADERS for all associated opportunities having a partner organization.

ZCASALESORDERHEADERSZPM5325

Access the sales order for table ZCA_SALES_ORDER_HEADERS where they're in the management chain of an associated opportunity sales team member with view, edit, or full access.

ZCASALESORDERHEADERSZPM5326

Access the sales order for table ZCA_SALES_ORDER_HEADERS where they're an associated opportunity sales team member with view, edit, or full access.

ZCASALESORDERHEADERSZPM5329

Access the sales order for table ZCA_SALES_ORDER_HEADERS where they're a member of a partner resource organization whose partner organization is on the associated opportunity.

QUOTE AND ORDER LINE

The Quote and Order Line object follows the same security requirements as the Quote and Order Line business object.

SERVICE REQUEST

This table lists the instance set name and associated description for the Service Request business object:

Instance Set Name Instance Set Description

SVCSERVICEREQUESTSSVC1

Access the service request header for table SVC_SERVICE_REQUESTS for all customer relationship management service requests (1=1).

SVCSERVICEREQUESTSSVC12

Access the service request header for table SVC_SERVICE_REQUESTS where the customer relationship management service request is assigned to them or their subordinate.

SVCSERVICEREQUESTSSVC13

Access the service request header for table SVC_SERVICE_REQUESTS where they or their subordinate is a member of customer relationship management service request team.

SVCSERVICEREQUESTSSVC14

Access the service request header for table SVC_SERVICE_REQUESTS where they or their subordinate is a member of customer relationship management service request account team.

SVCSERVICEREQUESTSSVC242

Access the service request header for table SVC_SERVICE_REQUESTS where the customer relationship management service request is assigned to a queue that they're a member.

SVCSERVICEREQUESTSSVC32

Access the service request header for table SVC_SERVICE_REQUESTS where the customer relationship management service request is for a partner.

SVCSERVICEREQUESTSSVC35

Access the service request header for table SVC_SERVICE_REQUESTS where their partner account is on the customer relationship management service request.

SVCSERVICEREQUESTSSVC70

Access the service request header for table SVC_SERVICE_REQUESTS where they created the customer relationship management service request or are a member of customer relationship management service request contact list.

TERRITORY

This table lists the instance set name and associated description for the Territory business object:

Instance Set Name Instance Set Description

MOTTERRITORIESMOT1

Access the sales territory for table MOT_TERRITORIES where they're the territory owner.

MOTTERRITORIESMOT2

Access the sales territory for table MOT_TERRITORIES where they're the owner of a parent territory in the territory hierarchy.

MOTTERRITORIESMOT4

Access the sales territory for table MOT_TERRITORIES where they're an administrator of the territory.

MOTTERRITORIESMOT5

Access the sales territory for table MOT_TERRITORIES where they're an administrator of a parent territory in the territory hierarchy.

MOTTERRITORIESMOT26

Access the sales territory for table MOT_TERRITORIES where they're a member of the territory team.

MOTTERRITORIESZCA100084

Access the sales territory for table MOT_TERRITORIES where they're a member of an access group associated to the sales territory with read access.

WORK ORDER

This table lists the instance set name and associated description for the Work Order business object:

Instance Set Name Instance Set Description

SVCWORKORDERSSVC214

Access the field service work order for table SVC_WORK_ORDERS where the field service work order is standalone or associated with a service request.

SVCWORKORDERSSVC216

Access the field service work order for table SVC_WORK_ORDERS where they or their subordinate is a member of the field service work order account team.

SVCWORKORDERSSVC217

Access the field service work order for table SVC_WORK_ORDERS where they or their subordinate is a member of the field service work order contact team.

SVCWORKORDERSSVC219

Access the field service work order for table SVC_WORK_ORDERS where they or their subordinate is a member of the service request team associated with the field.

SVCWORKORDERSSVC220

Access the field service work order for table SVC_WORK_ORDERS where they or their subordinate created the service request associated with the field service work order.

SVCWORKORDERSSVC221

Access the field service work order for table SVC_WORK_ORDERS where they or their subordinate created the field service work order.

SVCWORKORDERSSVC222

Access the field service work order for table SVC_WORK_ORDERS where they or their subordinate is assigned to a field service work order.

SVCWORKORDERSSVC223

Access the field service work order for table SVC_WORK_ORDERS where their partner account is on the field service work order.

SVCWORKORDERSSVC224

Access the field service work order for table SVC_WORK_ORDERS where the field service work order is for a partner account.

SVCWORKORDERSSVC246

Access the field service work order for table SVC_WORK_ORDERS where they or their subordinate is the technician assigned to a field service work order.

SVCWORKORDERSSVC455

Access the field service work order for table SVC_WORK_ORDERS where they or their subordinate is the technician assigned to a field service work order.

Compare Active Adaptive Search Configuration to the Default Configuration

You can generate a spreadsheet that compares any changes made to the current active adaptive search configuration against the last published default configuration. For example, you select the business objects you want to enable in Adaptive Search on the Quick subtab and click Publish to enable the adaptive search configuration provided by Oracle. For custom objects, the default configuration won't have any custom object configuration details.

You can modify how search operates on the Setup Advanced tab of the Configure Adaptive Search page. For example, you can specify which fields of an object and its related objects can be used in searches and displayed as search filters. Because Oracle configures the fields for you, setup is optional unless you want to enable search on custom child objects and fields, or to change Oracle's default search configuration. You must run the Publish process for your changes to take effect.

Generate Adaptive Search Comparison Report

Before you run the Publish process, you can view and compare all the attributes for the custom objects in addition to any entities enabled or disabled in the unpublished configuration.

You must have the ZCA_ADAPTIVE_SEARCH_CONFIG_PUBLISH privilege to generate a comparison spreadsheet for your currently active Adaptive Search configuration against your default configuration.

  1. From Setup, click Advanced.

    From here you can change which objects and fields are enabled for search, how they are searched on, and other search configurations. You can also enable and disable objects for searching.

  2. From the Actions menu, select Compare with Previous Configuration.

  3. From the Compare with Previous Configuration dialog, under Records, select either Modified or All options.

  4. Next, select one of these Adaptive Search configurations options:

    • Unpublished Configuration

    • Active Configuration

      to compare against one of these configurations:

    • Active Configuration

    • Default Configuration

  5. Click Export to download the comparison data from Adaptive Search as a CSV file. You can then use this file to view or analyze your data offline.

The spreadsheet contains a separate tab for each object and displays a list of attributes for each object in the current configuration. The first column displays the name of the Attribute, the next four columns shows the Boolean values for the current configuration and the next four columns shows the Boolean values of the default configuration.

Advanced Setup

Search Attribute Setup

During Adaptive Search setup, you can decide which fields of a business object and its related objects can be used in searches and displayed as search filters. For example, you can make it possible for salespeople to search for accounts using the account's primary contact name in the Workspace UI. You can also enable the account primary contact name for use in opportunity searches. When a salesperson searches on the account primary contact name in the opportunity Search box, the application lists all of the opportunities belonging to the accounts that have the individual listed as the primary contact.

Note: By entering precise search criteria for your saved search, you can greatly decrease the number of records returned and decrease the load time.

Adaptive Search supports relationships between the ready-to-use standard business objects. It also supports one-to-one and one-to-many custom relationships between standard and custom objects. Setup is done on the Advanced setup tab of the Configure Adaptive Search page. You select the business object you want to set up in the left pane of the tab, and set the object's search properties in the right pane.

Note: To be able to search on a particular attribute in Global Search, you must select the Include in Keyword Search option for that attribute.

Here's a screen capture of the Advanced setup tab of the Configure Adaptive Search page, highlighting the two panes.

Advanced tab of the Configure Adaptive Search page
with the two panes highlighted.

Left Pane - Select Objects and Related Objects

In the left pane of the tab, you can:

  • Enable and disable each business object for the Workspace UI by selecting its check box. (This is the equivalent of enabling the objects on the Quick Setup tab.)

  • Expand each object to view the hierarchy of related objects.

  • Select an object or a related object in the hierarchy to display its fields in the right pane.

As an example, here's a diagram of a portion of the related object hierarchy for opportunities and some of the fields each level of the hierarchy includes.

Object hierarchy and the fields at each level of
the hierarchy described in the text which follows.

Here's an explanation:

Hierarchy Level Object Name Description

1

Opportunity

Selecting the Opportunity top-level object in the left pane lets you specify the search operation for opportunity fields.

The list includes opportunity fields, such as name, asset, creation date, sales method, and sales stage and fields created by Workspace representing the related objects. These concatenated fields include all of the configuration settings for each related object.

For example, the Account field includes your configuration of search terms and settings for the Account object, the Contacts field includes the configuration for the Contacts object, and so on.

2

Account

An opportunity includes a field called Account where you enter the name of the account related to the opportunity. When you select Account in the left pane, the right pane only displays one field: Account.

The Account field in the right pane displays the identifying attribute name for the respective objects as follows:

Entity - Identifying Attribute Name

  • Account - Name

  • Activity - Subject

  • Asset - Asset Number

  • Contact - Name

  • Lead - Lead Name

  • Opportunity - Name

  • Partner - Name

  • Partner Contact - Name

3

Account

Selecting the Account object in the hierarchy displays the list of fields you can enable and configure for accounts. Configuring the Account object is the same as configuring the Account top-level object: the list of fields is the same and your selections affect all objects that include Account as a related object.

Right Pane - Configure Search Action for Your Selection

The right pane of the tab, Configure Fields, is where you control the search properties for fields of the object or related object you selected. Depending on the field, there are up to four options you can select:

Option What It Does

Enable

Enables the field for search. After you publish your setup and the indexing process completes successfully, you can:

  • Search using the field and include it in filters

  • Display it as a column in the Workspace table

Analyzed Text Search

This option is available for text fields only. Workspace can search text fields either as a single string or as individual indexed words. Selecting this option indexes individual words and enables fuzzy match and additional operators that you can use when searching the field. Fuzzy match makes it possible to search for similar spellings.

Selecting the Analyzed Text Search option, enables these operators:

  • All of the words

  • Any of the words

  • Contains

  • Ends with

  • Equals

  • Fuzzy match

  • None of the words

  • Not equal to

  • Starts with

Leaving the Analyzed Text Search option deselected, restricts you to these operators:

  • Equals

  • Exists

  • Is missing

  • Not equal to

Include in Keyword Search

Makes it possible to search on the field using the Search box at the top of the Workspace UI and enables keyword search on fields in Adaptive Search REST API. To be able to search on a particular attribute in Global Search, you must select the Include in Keyword Search option for that attribute.

The Adaptive Search application copies all the fields marked as Include in Keyword Search to a concatenated field that's made available for the search. If you select this option for five account fields, then the five are concatenated in a field and all five can be used in searching accounts. If you include too many fields as Include in Keyword Search, the accuracy of the search may diminish.

Note: Date fields aren't supported for Include in Keyword Search.

Include in Object Reference

Enables the field for use in searches of related objects. For example, if you select this option for the Chief Executive Name on the Account object, you can enable this field also for searching opportunities.

Note: Formula fields can't be configured in Adaptive Search because they aren't searchable and can't be indexed.

By default, Workspace and Global Search include all of the key fields you need for search. (See the topic Adaptive Search Configuration Provided by Oracle for a list.) However, you can enable additional fields for search, including custom ones, using the steps in this topic. And you can remove existing fields from use.

This example shows you how to enable the Chief Executive Name field, a standard application text field, but the same procedure applies to any field, even a custom field on a standard application object. When you're done with this configuration and publish it, a salesperson can enter the CEO name, in either Global Search or in the Workspace search box, to find the account where the person is the CEO. The search also returns all of the opportunities for that account when you enable opportunities to be searched by account fields.

Suppose that you added the CEO name field to the Account UI and want to make entries in this field searchable. Here's a screenshot of the Edit Account page highlighting the location of the field.

Edit Account page with the Chief Executive Name
field. The field appears in the Account region.

To make the field searchable in Workspace and Global Search involves these steps:

  1. You must make the field searchable for its business object.

  2. Optionally, you can enable the field for search of a related object.

  3. You must publish your configuration.

Note: If you want the field to be displayed in the UI, either as a filter or as a column in search results, then you must enable it for display on the Configure UI tab of the Configure Adaptive Search page.
Make the Field Searchable in Its Business Object

Here's how you make the field available for searching its business object. For example, making the account searchable by the CEO name.

  1. Navigate to the Setup and Maintenance work area, and use the following:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Show: All Tasks

    • Task: Configure Adaptive Search

  2. On the Configure Adaptive Search page, Setup tab (callout 1 in the screenshot), click Advanced (callout 2).

  3. In the left pane, click the name link for the object where the custom field appears (callout 3). The CEO name field is an account field, so you click Account.

    The field is listed in the Configure Fields section.

    Screenshot of a portion of the Configure Adaptive
Search page, highlighting the location of the Chief Executive Name
field. The Enable, Analyzed Text Search, Include in Keyword Search,
and Include in Object Reference options are selected.
  4. Select the Enable option to index the field for Workspace and Global Search (callout 4).

  5. For a text field, including Chief Executive Officer, select the Analyzed Text Search option to index individual words in the field. Your selection also enables fuzzy search (search that retrieves results with similar spellings). And you enable other search operators, including All of the words and Any of the words.

  6. Select the Include in Keyword Search option to enable the field for both Global Search and search using the Workspace Search box.

    If you leave this check box deselected, users can't search for accounts using the CEO name. But in Workspace, they can still add the Chief Executive Name field as a filter for accounts and search the field there. Global Search doesn't permit you to add filters, only to search by keyword.

  7. Select the Include in Object Reference option to enable the field for search in related objects. Make the selection if you want to use the CEO name when searching for opportunities, for example.

    If you didn't select the Include in Keyword Search option, but select Include in Object Reference, then users searching opportunities can use the field only as a filter in Workspace.

Make the Field Available for Searching a Related Object

You can only make the field available for search in a related business object if you selected the Include in Object Reference option for the field.

  1. In the left pane of the window, open the object where you want to enable the search. For this example, Opportunity (callout 1 in the screenshot).

    Sample screenshot of the Advanced tab of the objects
enabled in Adaptive Search
  2. Select the field in the left pane, in this example, Account (Callout 2).

  3. In the right pane, select Enable (callout 3).

  4. If you want to use the field for searches in Global Search and in the Workspace Search box, you must select the Include in Keyword Search option (callout 4).

    If you don't select this option, but selected Enable, then the field remains available as a filter in Workspace, but can't be searched in Global Search.

    The Include in Object Reference option isn't relevant here. Here's a summary of the two use cases:

    Use Case Enable Include in Keyword Search

    Users can search on the field using Global Search and in the Workspace Search box. For example, entering the CEO name, they get results containing, not only the account where the person is a CEO, but the opportunities for that account as well. In Workspace, they can also select the fields as a filter when searching for the object. For example, when searching for opportunities in Workspace, they can filter by CEO name.

    Selected

    Selected

    Users can add the field as a filter in Workspace, but can't search on it using the Search box or using Global Search.

    Selected

    Deselected

Publish Your Configuration

After making your option selections, click Publish.

Publishing triggers an indexing process that you can monitor on the Monitor tab, Publish subtab. Your new configuration becomes available after the indexing process completes. If the process completes with errors for some reason, contact your help desk.

Enable the Field for Use As a Filter in the Workspace UI

For the field to be used as a filter and added as a column in search results, you must enable it for display on the UI:

  1. In the Configure Adaptive Search page, click Configure UI.

  2. To enable the field for use as a filter on its object (for example, to enable the account field to be used as a filter when searching accounts), do the following:

    1. Select the object in the left pane of the Configure UI tab.

    2. Select the Display in UI option for the field.

  3. To enable the field for use in the UI of other related objects (for example, to enable the account field as a filter in opportunity searches), do the following:

    1. Display the related object hierarchy for the object where you want to enable the filter in the left pane of the Configure UI tab. For example, select Opportunity (callout 1 in the following screenshot).

    2. Locate and select the field's object in the object hierarchy. For example, select Account (callout 2).

    3. Select Display in UI option for the field (callout 3).

      Screenshot of the Configure UI tab with callouts
highlighting the Opportunity object, the Account field and the Display
in UI option.
  4. Click Save and Close.

By default, Workspace makes it possible for you to use the fields in the primary address in searching accounts using the Search box. For example, if you enter the word "main" as a search term when searching for accounts, the application returns accounts with the word "main" in their names as well as accounts with primary addresses on "Main Street", "Main Avenue" and so on. If your accounts have multiple addresses, you can broaden the search to include all of the addresses. To be able to search on a particular attribute in Global Search, you must select the Include in Keyword Search option for that attribute.

To broaden account searches to include all addresses for searching accounts:

  1. Navigate to the Setup and Maintenance work area, and use the following:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Configure Adaptive Search

    The Configure Adaptive Search page appears.

  2. Click Advanced.

  3. In the left pane of the tab, open the Account object to reveal its related objects.

  4. Select the Addresses related object.

    The right pane, Configure Fields: Account displays the concatenated Addresses field.

  5. Make sure the Enable option is selected for the Addresses field.

  6. Select the Include in Keyword Search option.

    Here's a screen capture of the Advanced tab of the Configure Adaptive Search page highlighting the selection of the Account Addresses in the left pane and the Addresses field with the selected Include in Keyword Search option in the right pane.

    Screen capture of the Advanced tab of the Configure
Adaptive Search page. The highlighted fields are described in the
text.
  7. Now that all addresses are included in account searches, you can exclude the primary addresses to avoid duplication. Primary addresses are already included in addresses.

    1. Select Primary Address in the left pane.

    2. Deselect the Include in Keyword Search option in the right pane.

      Here's a screen capture of the Advanced tab of the Configure Adaptive Search page highlighting the selection of the Primary Address in the left pane and the Primary Address field with the Include in Keyword Search option deselected in the right pane.

      Screen capture of the Advanced tab of the Configure
Adaptive Search page. The highlighted fields are described in the
text.
  8. After making your selections, click Publish.

    Publishing triggers an indexing process that you can monitor on the Monitor tab. Your new configuration becomes available after the indexing process completes. If the process completes with errors for some reason, contact your help desk.

Set Up Searches on Related Object Attributes

Sometimes you want to enable the search on the attributes of a related business object. For example, you may want to find opportunities using the account owner or primary contact. Enabling this kind of search involves two steps:

  1. Specifying which object attributes are searchable.

  2. Enabling the related object for search.

For example, to make opportunities searchable by account attributes, you first make sure that the attributes you need are searchable for the Account object. You then open the Opportunity object and enable the Account related object for searching opportunities.

Specify Which Object Attributes Are Searchable

  1. Navigate to the Setup and Maintenance work area, and use the following:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Show: All Tasks

    • Task: Configure Adaptive Search

  2. On the Configure Adaptive Search page, click Advanced.

  3. In the left pane of the tab, select the top-level object. For example, to specify which account attributes are searchable, you select the top-level Account object.

  4. In the right pane, do the following for each field you want include in the search:

    1. Select the Enable option.

    2. Select the Include in Keyword Search option.

      All of the fields with the Include in Keyword Search option selected are included in the concatenated field and can be used in search. It is this field, with the same name as the object, that you enable for the related object.

      Here's a screenshot of the Advanced tab of the Configure Adaptive Search page. It highlights the location of the Account object and Include in Keyword Search option.

      Screenshot of the Advanced tab of the Configure
Adaptive Search page. The highlighted fields are described in the
text.
Make the Related Object Available for Search in the Object

Here's how to make the related object available for search.

  1. In the left pane of the Advanced tab, open the object to reveal its related objects. For example, open the Opportunity object.

  2. Select the related object. For example, select Account underneath the Opportunity object.

    The right pane displays the concatenated field. For Account, the name of the concatenated field is Account.

  3. Make sure the Enable option is selected for the field.

  4. Select the Include in Keyword Search option.

    Your action enables search on the attributes you enabled for this object.

    Here's a screenshot of the Advanced tab of the Configure Adaptive Search page. It shows the selection of the Opportunity object and its Account related object in the left pane. In the right pane, the Include in Keyword Search option is selected for the Account field.

    Screenshot of the Advanced tab of the Configure
Adaptive Search page. The highlighted fields are described in the
text.
  5. Click Publish.

    Publishing triggers an indexing process that you can monitor on the Monitor tab. Your new configuration becomes available after the indexing process completes. If the process completes with errors for some reason, contact Oracle support.

Groovy Support to Count the Number of Search Attributes Enabled for Adaptive Search

Adaptive Search displays the list of records matching the saved search criteria and provides you with a record count. Sometimes, the amount of attributes enabled for a business object may exceed the recommended amount of 500 for each object, so you may not find the field attribute you were searching for. You can reduce the count of fields by deselecting the Include in Object Reference check box for child entities that you may not require. For more details, see the topic Example of How to Make a Field Searchable in Workspace.

Number of Search Attributes Enabled

You can use Groovy scripts to count the total number of search attributes you have enabled in Adaptive Search. Here's sample of the query trigger code that will display a count for the total number of search attributes you have enabled in your Adaptive Search test environment.

Note: If you want to count the enabled search attributes in your active production environment, edit the script and replace Sandbox with Active.
SELECT
ea.ATTRIBUTE_UUID,
ltrim(sys_connect_by_path(CASE WHEN (ea.max_occurs is null and
ea.ATTRIBUTE_TYPE_NAME < > `Enum ) THEN ea.ATTRIBUTE_NAME||'[]' ELSE
ea.ATTRIBUTE_NAME END,`. ),`. ) AS DOC_ATTRIBUTE_PATH,
ad.AGGREGATION_UUID,
ad.SEARCHABLE_FLAG
FROM FUSION.ZCA_ES_ATTRIBUTES ea, FUSION.ZCA_ES_ATTRIBUTE_DEFAULTS ad
WHERE ( (level > 1
AND ea.INCLUDE_IN_REFERENCE_FLAG = `Y  )
OR ( level = 1)
OR (ea.RECORD_ENTITY_UUID IS NOT NULL
AND (SELECT COUNT(*)
     FROM FUSION.ZCA_ES_ATTRIBUTES iea
     WHERE iea.ENTITY_UUID = ea.RECORD_ENTITY_UUID
     AND iea.INCLUDE_IN_REFERENCE_FLAG = `Y ) > 0 ) )
AND ea.META_MODEL_VERSION_UUID = (select meta_model_version_uuid from
FUSION.zca_es_meta_model_versions where workflow_state_type_name = `Sandbox )
AND ea.INDEXED_FLAG=`Y 
AND ea.ENABLED_FLAG=`Y 
AND ea.SEARCHABLE_FLAG = `Y 
AND ea.ATTRIBUTE_UUID = ad.ATTRIBUTE_UUID
AND ad.SEARCHABLE_FLAG = `Y 
START WITH ea.ENTITY_UUID = `d8c3af80-bc97-4ff6-a37c-cf9e8e1775c9  AND
ea.META_MODEL_VERSION_UUID = (select meta_model_version_uuid from
FUSION.zca_es_meta_model_versions where workflow_state_type_name = `Sandbox )
CONNECT BY (ea.ENTITY_UUID = PRIOR ea.RECORD_ENTITY_UUID AND
ea.META_MODEL_VERSION_UUID = (select meta_model_version_uuid from
FUSION.zca_es_meta_model_versions where workflow_state_type_name =
`Sandbox ))
AND PRIOR ea.ENABLED_FLAG=`Y  AND PRIOR ad.SEARCHABLE_FLAG = `Y  AND ((PRIOR
ea.ATTRIBUTE_TYPE_NAME!=`ForeignKey ) OR (PRIOR
ea.ATTRIBUTE_TYPE_NAME=`ForeignKey  AND ea.INCLUDE_IN_REFERENCE_FLAG=`Y ));

For more information on Groovy scripting, see the related links.

Enable Merge Requests for Accounts and Contacts

The Merge Request Enabled (ZCA_MERGE_REQUEST) profile option specifies whether or not to allow salespeople to perform a merge request action for account and contact records in Workspace. Merging and resolving duplicate records ensures that clean customer data is available.

The predefined value is set to N, which means that salespeople can't create a merge request if they have duplicate records pointing to the same customer. You must set the profile option value to Y if you want salespeople to be able to consolidate those records into one.

Here's how to edit the Merge Request Enabled profile option.

  1. In the Setup and Maintenance work area, go to:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Administrator Profile Values

  2. From the search region of the Manage Administrator Profile Values page, enter the profile option code name ZCA_MERGE_REQUEST in the Profile Option Code field.

  3. Click Search.

  4. In the list that's returned, click the profile option code link.

  5. Select Y in the Profile Value field to turn on the merge request feature.

  6. Click Save and Close.

Search Filter Setup

You can create different groupings of values for numeric, corporate currency, percent, and date fields. These groupings display when the field is used as a filter in a search. Users get an overview of the number of records in each value grouping and they can select the groupings to narrow down their search results even more. For example, you can break down opportunity revenue into different ranges: 0 to 10,000, 10,000 to 100,000, 100,000 to 500,000, and 500,000 and up. When users use opportunity revenue as a filter, they see how many opportunities fall in each range. Selecting a range automatically displays a list of opportunities in that range.

You can also place related records displayed together as a group based on account, country, rank and so on. This provides an overview of the records in each value and you can select a group list to narrow down your search results even more. You can also perform search based on the fiscal quarters.

Note: By entering precise search criteria for your saved search, you can greatly decrease the number of search records returned and decrease the load time.

Before you start to create a value group field, ensure that the field is enabled for Workspace and enabled for UI display before creating its value groupings. See the Enable Fields for Display as Filters and Search Result Columns topic for details.

Note: You can set up to a maximum of six filters. If you try to add more than six filters, you're prompted to remove filters to meet the maximum threshold of six.

Here's how to create a grouping of values for display as a filter in your search.

  1. Sign in as a setup user.

  2. Navigate to the Setup and Maintenance work area, and use:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Show: All Tasks

    • Task: Configure Adaptive Search

    The Configure Adaptive Search page appears.

  3. Click the Configure UI tab.

  4. Select the object where you want to set up filter value groupings in the left pane of the tab. You may have to open up the object hierarchy. The fields for the object display in the Configure Fields tab on the right.

    Note: You can create filter value groupings only for fields that display a name of an existing grouping in the Define Groupings column. The Defined Groupings (checked) indicator (a check mark) in this column indicates filter groupings are created automatically. You can't create your own groupings for these fields.
  5. If a filter grouping supplied by Oracle already exists for the field you want to set up, then remove the filter from the field. You can't edit filter value groupings provided by Oracle.

  6. If no filter value groupings exist for the field, then click Search (the down arrow) to display the list of existing groupings and either select an existing grouping or click the Create link to create a new one.

    Here's a screenshot of a portion of the Configure UI page. Callouts identify the relevant features.

    Callout Number Description

    1

    Selecting an object on the left displays its fields on the right.

    2

    A name in the Define Groupings column tells you that you can create filter groupings of your own. You must remove the existing filter groupings before selecting or creating a new one. You can edit groupings by clicking the name, but not those groups provided by Oracle.

    3

    A check mark in the Define Groupings column indicates filter groupings are created automatically. You can't create your own groupings for these fields.

    4

    Clicking Search (the down arrow icon) in the Define Groupings column displays a list of existing filters. Search is only available after you remove an existing grouping for the fields.

    5

    Location of the Create link

    6

    Selecting the Display in UI option makes the field available in the Workspace UI.

    Configure UI page with the Opportunity object selected
  7. If you're creating a filter for a date field, then do the this:

    1. Enter a unique filter name and description. The filter name appears in the list of existing filters whenever you're adding a new filter.

    2. In the Manage Date Filters region, use the Move buttons (arrows) to select the date ranges you want to use in the filter and change their order. You can't create additional date ranges.

      The image shows a screen capture of the Create Filter page for a date field.

      Create Filter window for a date field
    3. Click OK when you're done.

      Note: In Workspace, a filter Date type such as Last Week is considered to be from Monday to Sunday and displays all records from Monday to Sunday of the previous week. Selecting a filter of Last Year, for example in 2021, would return all records from January 01 2020 to December 31 2020 for the selected search object.
  8. If you're creating a filter for a numeric, corporate currency, or percent field, then do this:

    1. Enter a unique filter name and description. The filter name appears in the list of existing filters whenever you're adding a new filter.

    2. Create the filter value groupings. You can create up to 10 groupings. No gaps or overlaps are allowed between groupings. To create the groupings:

      1. Click Add (the plus icon).

      2. For the first grouping, you can select either the Less than or the Between operator and enter the low and high values as appropriate.

        Results with the high value you enter aren't included in the filter value range. If you enter a range of 0 to 10,000 then the filter value grouping displays records between 0 and 9,999.

      3. Subsequent groupings copy the high value from the previous grouping as the low value for the new grouping.

        The low value is inclusive. If the low value is 10,000, then the grouping displays results with 10,000.

        You can use the Between, Greater than and equal to and Equal to operators.

      This table lists the filter value groupings for a sample filter called Revenue Ranges.

      Function Low Value High Value

      Between

      0

      10,000

      Between

      10,000

      100,000

      Between

      100,000

      500,000

      Greater than or equal to

      500,000

      Not applicable. There's no high value for the Greater than or equal to function.

      This image shows a screen capture of the Create Filter page for the sample Revenue Ranges numeric filter.

      Screen capture of the Create Filter window for
a sample numeric field filter. The filter, called Revenue Ranges,
includes filter value groupings described in the text.
    3. Click OK when you're done.

  9. Ensure that the Display in UI option is selected for the fields you want to enable for use as filters in the UI. The fields are also available for display as columns in the search results.

  10. Click Save and Close.

The changes you made are reflected in the Workspace UI. No publishing is required for the filter changes.

You can specify which fields are available for selection as Workspace filters and can be displayed as columns in search results and saved searches. The fields you enable by selecting the Display in UI option from the Configure UI tab in the Configure Adaptive Search page are available for selection in the Edit Columns and Edit Filters windows.

To enable the fields for selection:

  1. Sign in as a setup user.

  2. Navigate to the Setup and Maintenance work area, and use the following:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Configure Adaptive Search

    The Configure Adaptive Search page appears.

  3. Click Configure UI.

  4. Select the object you want to set up in the left pane of the tab. You must open the hierarchy of related objects to get to some of the fields.

  5. Ensure that the Display in UI option is selected for the fields you want enabled as filters and for display in search results.

    Note: The default layout specifies that a minimum of four fields must be displayed for your Workspace UI configuration. Therefore, when editing Workspace UI columns and specifying fields, always ensure that you have at least four fields selected for both standard and custom objects.
  6. Click Save and Close.

The changes you made are immediately reflected in the Workspace UI. No publishing is required.

You can enable the territory membership and territory membership hierarchy values that appear in the opportunity search filter record sets in the Workspace UI. The My territory membership record set returns records where the signed in user is either the owner or a member of territories assigned to the opportunity. The My territory membership hierarchy returns records where the signed in user is either the owner or a member of a territory assigned to the opportunity, or owner or member of a territory that's ascendant to an assigned territory. These record sets are predefined but they must be enabled before your salespeople can use them in Workspace.

Here are the steps to enable the My territory membership and My territory membership hierarchy values for the opportunity search filter record sets in Workspace.

  1. Navigate to the Setup and Maintenance work area, and use the following:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Standard Lookups

  2. In the Meaning field, enter Opportunity Filter Record Sets for Workspace.

  3. Click Search.

  4. Select the lookup type you want to enable in the ORA_MOO_OPTY_SRCH_RS_WS: Lookup Codes page.

    • Scroll to the ORA_MYASSGMEMBTERROPTIES (My territory membership) lookup code and select Enabled.

    • Scroll to the ORA_MYASSGMEMBDESCTERROPTIES (My territory membership hierarchy) lookup code and select Enabled.

  5. Click Save and Close.

Saved Search Setup

You can create and manage saved searches for different roles and for your own personal use. You can also assign a unique default saved search for each role. A default saved search is the search a user sees when first opening Workspace. Sales users can create their own personal saved searches, manage them, and assign their personal default saved search. These saved searches take precedence over what you, as administrator has assigned to them. You create and manage saved searches from the Workspace UI rather than from the Configure Adaptive Search page.

Note: By entering precise search criteria for your saved search, you can greatly decrease the number of records returned and decrease the load time.
Overview of Manage Saved Searches UI

The Manage Saved Search UI contains the My List tab, Workspace List tab, and Set Defaults tab. These allow administrators to manage their personal list of saved searches, assign saved searches to roles, and assign default saved searches to roles, respectively. These tabs are only exposed to administrators to:

  • Assign saved searches for user roles

  • Assign a default saved search for roles

  • Change a default saved search for roles

  • Perform overall role-based administration

Note: Workspace users can manage their own personal saved searches from the Manage Saved Searches page. However, they won't have access to the My List, Workspace List, or Set Defaults tabs. However, mobile app users can can override these and set their own default searches, too. This feature helps to display the most relevant records in their mobile app with a single tap on the menu.

All sales users can create saved searches for themselves. But sales administrators can create saved searches for the whole sales organization and for specific sales roles. A default saved search is the saved search that's automatically displayed when the user first accesses Workspace. Oracle delivers predefined default saved searches for some user roles and the search results returned depends on what role is assigned. For example, ready-to-use partner roles include Partner Sales Representative, Partner Sales Manager, and Partner Administrator.

From the My List tab, you can manage your own personal saved searches exclusively, separate from the saved searches that are shared with the broader organization. Here is a screenshot of the My List window.

Note: Mobile app users can select the save searches they want from Default for Mobile column.
A screenshot of the My List UI

From the Workspace List tab, you can share and manage saved searches with other roles. You can designate saved searches as shared with everyone, with specific user roles, or with no one. Here's a screenshot of what the Workspace List window looks like.

A screenshot of the Workspace List UI

The Set Defaults tab enables you to define the default saved search for each user role. However, to assign a default saved search, you also must have permission to view that specific default saved search. Otherwise it won't appear in the list of saved searches to assign. Here's a screenshot of the UI.

A screenshot of the Set Defaults UI

If you select Site Level, the following options are displayed:

A screenshot of the Set Defaults UI at the site
level for saved searches for Workspace

If you select a specific role, the following options are displayed:

A screenshot of the Set Defaults UI at the role
level for saved searches for Workspace

Create a Saved Search

Here's how you can create a saved search either for yourself or for others in the organization. The saved searches you create are available for selection in Workspace and also appear as filters in the actionable infolets and Workspace infolets. The saved searches are listed in alphabetic order.

  1. In Workspace, select a saved search as your starting point. For example, the All Accounts saved search provided by Oracle lets you create your saved search for all the accounts you can see.

  2. Enter your search terms. You can enter search terms in the Search box, add filters, select filter values, or any combination of these.

  3. You can add or change the columns displayed in the search results by clicking Edit Columns (the pencil icon highlighted by callout 2 in the following screenshot).

  4. Click Save As (highlighted by callout 1).

    Workspace with callouts highlighting the Edit Columns
and Save As iconsCreate Saved Search window
  5. Enter the name for your saved search. Remember that the saved searches are listed in alphabetic order.

  6. To make this saved search the default saved search for you personally, select the Set as my default saved search option. The default saved search is what you see whenever you navigate to Workspace.

  7. Specify how you want to share the saved search you're creating. There are three options:

    • Only Me

    • Everyone

    • Specific Roles

  8. If you selected Specific Roles, click Search (the people icon) and select the job roles.

  9. Click Create.

From the My List tab of the Workspace UI, you can manage your own personal saved searches exclusively, separate from the saved searches that are shared with the broader organization.

Here are the steps to help you manage your own personal saved searches for a business object:

  1. Select the business object.

  2. From the same menu select Manage Saved Searches, then select the My List tab.

    Here's a screenshot of the list of items that appears when you click the selector. The image highlights the Manage Saved Searches task, the last selection on the list.

    List of business objects that appears when you
click the business object selector. The image highlights the location
of the Manage Saved Searches task.

    This screenshot shows the My List tab as seen by administrators. The table describes the columns highlighted in the screenshot by callouts.

    Callout Number Column Name Description

    1

    My Default Saved Search

    This is the signed in user's personal default saved search. The user can keep the default saved search assigned by the administrator, or change the saved search to a different one contained in the drop-down list.

    2

    Manage List

    The business object containing the saved searches you're managing. For example, by selecting Accounts for Manage List, saved searches based on the Account business object will appear.

    3

    Default for Mobile

    The saved search appears in the list of saved searches for mobile users when this option is selected. While you can't delete lists provided by Oracle, you can hide them from mobile users by deselecting the Default for Mobile option.

    Screenshot of the My List tab on the Manage Saved
Searches window
  3. Update your personal saved searches. You can:

    • Rename saved searches you created

    • Hide any of the shared searches from the shared group by deselecting Show in List.

    • Specify searches for the whole organization by selecting Everyone from the Shared With list.

    • Specify searches for users with one or more specific job roles, by selecting Specific Roles from the Shared With list. The saved search can then be managed from the Workspace List tab, where you assign the specific roles permission to view the saved search. You must click Save before proceeding to the Workspace List tab.

    • Delete saved searches you created from the application by clicking Delete.

  4. Click Save and Close when you're done.

    If you're sharing a saved search with other user roles, click Save to proceed and manage those saved searches in the appropriate Workspace List or Set Defaults tabs.

From the Workspace List tab, you can share and manage saved searches with other roles. You can designate saved searches as shared with everyone, with specific user roles, or with no one. The Set Defaults tab lets you define the default saved search for each user role.

Share and Manage Saved Searches with Other Roles

Here are the steps to help you manage and share saved searches with other roles:

  1. Select the business object.

  2. From the same menu select Manage Saved Searches, then select the Workspace List tab.

    This screenshot shows the Workspace List tab as seen by administrators. The table describes the columns highlighted in the screenshot by callouts.

    Callout Number Column Name Description

    1

    Manage List

    The business object containing the saved searches that are shared across roles. For example, by selecting Accounts for Manage List, saved searches based on the Account business object will appear.

    2

    Shared With

    You can share a saved search with Everyone (all job roles) in the organization or with Specific roles, (specific job roles). You can also select Not shared if you don't want to share with other job roles.

    3

    Delete

    Deletes the saved search from the application. You can't delete saved searches provided by Oracle.

    Screenshot of the Workspace List tab
  3. Click the Workspace List tab to update the saved searches. You can:

    • Specify searches for the whole organization by selecting Everyone from the Shared With list.

    • Specify searches for users with one or more specific job roles, by selecting Specific roles from the Shared With list and then selecting the job roles by clicking Search (the people icon).

    • Delete saved searches you created from the application by clicking Delete.

  4. Click Save and Close when you're done.

    If you want to define the saved search as the default saved search for a user role in the Set Defaults tab, or if you want to navigate to the My List tab, first click Save before you leave the Workspace List tab.

Define the Default Saved Search for Each User Role

The default saved search is the saved search that will automatically display when the user first accesses Workspace. With the Set Defaults tab, you can define or change a default saved search for any user role.

Here are the steps to help you define or change a default saved search for any user role:

  1. Select the business object.

  2. From the same menu select Manage Saved Searches, then select the Set Defaults tab.

    This screenshot shows the Set Defaults screen as seen by administrators when they select the set defaults at the site level.

     Screenshot that shows the Set Defaults options
available at the Site Level
  3. Click the Set Defaults tab to define or change a default saved search for any user role.

    Note: Saved searches that you don't have permission to access, don't appear in the Default Saved Search drop-down list. To see the assigned default saved search in the drop-down list, and to assign the default saved search to a role, you must have permission to view the object underlying the saved search.
  4. Scroll the page until you see the role name and it's default saved search that you either want define or change for any user role.

  5. From the drop-down list select a new role name for the default saved search or change to a different role contained in the drop-down list.

  6. Click Save and Close when you're done.

    If you want to manage your saved searches in the Workspace List tab, or if you want to navigate to the My List tab, first click Save before exiting the Set Defaults tab.

Saved searches are predefined for Workspace users. In addition, you can set the default saved search per object for mobile app users for either specific roles or for the whole site. Mobile users can override these and set their own default searches, to display the most relevant records in their mobile app with a single tap on the menu.

The Set Defaults tab enables you to define the default saved search for each user role. However, to assign a default saved search, you also must have permission to view that specific default saved search. Otherwise it won't appear in the list of saved searches to assign. Here's a screenshot of the UI.

A screenshot of the Set Defaults UI

If you select Site Level, the following options are displayed:

A screenshot of the Set Defaults UI at the site
level for saved searches for Workspace

If you select a specific role, the following options are displayed:

A screenshot of the Set Defaults UI at the role
level for saved searches for Workspace

To display search results in groups based on the specific fields on the object or related objects, you must set the Enable Group By in Workspace parameter to Y. Once enable, salespeople can view an overview of the number of records in each Grouped By grouping and can search and filter records within these groupings. They can also view aggregates such as count, average, and sum of values on the records of each group.

Enable Group By in Workspace Parameter

Here's how to set the Enable Group By in Workspace parameter.

  1. Click Navigator > My Enterprise > Setup and Maintenance.

  2. In the Setup and Maintenance work area, go to:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Configure Adaptive Search

  3. On the Configure Adaptive Search page, click the Parameters tab.

  4. Highlight the Enable Group By in Workspace and click Edit. This warning is displayed.

    You're about to change parameters that control how Adaptive Search works. 
    Changes should only be carried out by search setup experts. 
    Do you want to continue?

  5. Click Yes.

  6. In the Current Value field, change the value from N to Y and click Save and Close.

Specify Fields to Use for Group By

Here's how to specify field values for display as a filter in your Group By search.

  1. Sign in as a setup user.

  2. Navigate to the Setup and Maintenance work area, and use:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Show: All Tasks

    • Task: Configure Adaptive Search

    The Configure Adaptive Search page appears.

  3. Click the Configure UI tab.

  4. Select the object where you want to set up field values for your Group By search in the left pane of the tab. You may have to open up the object hierarchy. The fields for the object display in the Configure fields pane on the right as highlighted in the sample screenshot.

    Sample screenshot that shows the Enable for Group
By check box
  5. Select the Enable for Group By option for the fields you want to enable for use as a Group By search in the UI.

    Note: Ensure that the Display in UI option is also selected
  6. Click Save and Close.

  7. Sign out and then sign in again to see your changes.

No publishing is required. The changes you made are reflected in the Workspace UI for the Group By field drop down lists for the selected object.

Here are the supported objects and the associated predefined fields that are available for display as filters for your Group By search. This list contains the standard predefined configuration but you can specify field values for display as a filter in your Group By search by going to the Configure Adaptive Search > Configure UI > Enable for Group By.

Fields in parentheses represents the associated Adaptive field attribute.

Business Object Fields Enabled for Group By

Account

  • Industry (PrimaryIndustry)

  • Type (SalesProfileType)

  • State - from the Primary Address (PrimaryAddress.State)

  • Account Score (AccountScore)

Activity

  • Type (ActivityTypeCode)

  • Priority (PriorityCode)

  • Status (StatusCode)

  • Primary Contact (PrimaryContactId)

Contact

  • Account (PrimaryAccount)

Lead

  • Status -Unqualified, Qualified, Converted, Retired (StatusCode)

  • Lead (Score)

  • Lead Rank -Hot, Warm, Cold (Rank)

  • Week - on lead creation date (CreationDate)

Opportunity

  • Win Probability (PrimaryRevenue.WinProb)

  • Month - on close date (EffectiveDate)

  • Account (CustomerAccount)

  • Account (CustomerAccount)

Partner

  • Tier (TierId)

  • Partner Type (ListOfPartnerTypes.AttributePk2)

  • Status (Status)

Service Request

  • Severity (SeverityCd)

  • Status (StatusCd)

  • Queue (Queue)

  • Product (InventoryItemId)

  • Category (srCategoryID)

Lists of Prioritized Recent Items

Smart Lists

Smart lists provide salespeople with lists of recent items they worked on. But there's more. Those items salespeople access the most and those that are most recent appear at the top of each list. For example, the My Smart List for Accounts includes accounts ranked by the number of times a salesperson has opened each account, its contacts, and its opportunities and how recently. So, if today you open or update account information on Acme four times, but only open Pinnacle once, then Acme appears higher on the list than Pinnacle. Each salesperson gets their own set of smart lists, one for each of the following sales objects: accounts, contacts, leads, opportunities, and partners. Each list can display a maximum of 50 items. Items that haven't been touched for 30 days get automatically taken off the list.

Smart lists are included along with saved searches in Workspace, Workspace infolets, and the CX Sales Mobile app. For example, to display the smart list for accounts in Workspace, salespeople select Accounts > My Smart List for Accounts, just like any other saved search:

My Smart List of Accounts in Workspace. The image
shows sample data with the My Smart List for Accounts selected.

The list is created and maintained by two processes:

  • The Generate Relevancy Feed process creates the list. By default, this process runs every three hours.

  • The Age User Context Relevancy process removes items from the list that haven't been touched by the user in the past 30 days. By default, this process runs once a day.

Modify Smart List Behavior

Smart lists are available automatically to salespeople as soon as they start working in the application. No setup is required. However, you can modify smart list behavior in two ways:

  • Change how long untouched items are kept in the list. By default, items are kept 30 days after they're accessed last. If your organization, has long sales cycles, you may want to keep items on the list longer, for example.

  • Change how frequently and when smart lists are refreshed to improve user experience.

Change How Long Items Are Kept in the List

You can change the number of days untouched records are kept in the list by setting the profile option Relevancy Aging Maximum Number of Days (ZCA_UC_AGING_CYCLE). Here's how:

  1. In Setup and Maintenance, open the Manage Administrator Profile Values task:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Manage Administrator Profile Values

  2. In the Manage Administrator Profile Values page, search by the profile option name or code.

  3. Click the profile option name link.

  4. Set the profile option value to the desired number of days.

  5. Save your changes.

Run the Smart List Processes with Different Frequencies and Schedules

You can change how frequently or when you run the two processes that generate the list and remove untouched items from the list:

  • Generate Relevancy Feed

    Generates the smart lists by analyzing all records that have been updated in the last 24 hours. By default, this process runs every three hours.

  • Age User Context Relevancy Feed

    Removes from smart lists all items that haven't been accessed in the past 30 days (the number of days set in the profile option Relevancy Aging Maximum Number of Days). By default, this process runs once a day.

See the User Context section of the Sales and B2B Service Scheduled Processes chapter of Understanding Scheduled Processes guide for details.

Additional Configurations

Set Up Search on Personally Identifiable Information in Workspace

Workspace supports personally identifiable information (PII) attributes and includes them in search criteria and search results. The PII attributes are appropriately secured based on the READ privileges and aren't searchable (masked) if you don't have the necessary READ privilege.

Here are the PII attributes that are masked or are available in Workspace based on the different user privileges:

  • HZ_VIEW_TRADING_COMMUNITY_PERSON_SOCIAL_SECURITY_DATA

    JgzzFiscalCode HomePhone MobilePhone PrimaryPhone, ListOfPhones HomeAddress PrimaryAddress, ListOfAddresses PersonalEmail PrimaryEmail, ListOfEmails

    Don't mask

    Mask

    Mask

    Mask all home and mobile phones

    Mask

    Mask all home addresses

    Mask

    Mask all personal emails

  • HZ_VIEW_TRADING_COMMUNITY_PERSON_CONTACT_DATA

    JgzzFiscalCode HomePhone MobilePhone PrimaryPhone, ListOfPhones HomeAddress PrimaryAddress, ListOfAddresses PersonalEmail PrimaryEmail, ListOfEmails

    Mask

    Don't mask

    Mask

    Mask all mobile phones

    Mask

    Mask all home addresses

    Don't mask

    Don't mask

  • HZ_VIEW_TRADING_COMMUNITY_PERSON_MOBILE_PHONE_DATA

    JgzzFiscalCode HomePhone MobilePhone PrimaryPhone, ListOfPhones HomeAddress PrimaryAddress, ListOfAddresses PersonalEmail PrimaryEmail, ListOfEmails

    Mask

    Mask

    Don't mask

    Mask all home phones

    Mask

    Mask all home addresses

    Mask

    Mask all personal emails

  • HZ_VIEW_TRADING_COMMUNITY_PERSON_CONTACT_DATA and HZ_VIEW_TRADING_COMMUNITY_PERSON_MOBILE_PHONE_DATA

    JgzzFiscalCode HomePhone MobilePhone PrimaryPhone, ListOfPhones HomeAddress PrimaryAddress, ListOfAddresses PersonalEmail PrimaryEmail, ListOfEmails

    Mask

    Don't mask

    Don't mask

    Don't mask

    Mask

    Mask all home addresses

    Don't mask

    Don't mask

  • HZ_VIEW_TRADING_COMMUNITY_PERSON_ADDRESS_DATA

    JgzzFiscalCode HomePhone MobilePhone PrimaryPhone, ListOfPhones HomeAddress PrimaryAddress, ListOfAddresses PersonalEmail PrimaryEmail, ListOfEmails

    Mask

    Mask

    Mask

    Mask all home and mobile phones

    Don't mask

    Don't mask

    Mask

    Mask all personal emails

  • No user privilege

    JgzzFiscalCode HomePhone MobilePhone PrimaryPhone, ListOfPhones HomeAddress PrimaryAddress, ListOfAddresses PersonalEmail PrimaryEmail, ListOfEmails

    Mask

    Mask

    Mask

    Mask all home and mobile phones

    Mask

    Mask all home addresses

    Mask

    Mask all personal emails

About Aggregates in Adaptive Search

Workspace supports a set of predefined aggregated fields. Aggregated fields calculate key record metrics displayed in search results and lets you view calculations that include count, average, and sum of values across fields on a record, related objects, and parent-child objects.

Aggregates are available in the list of available attributes on the corresponding object (callout 1). You can filter or expose the aggregation as a column as shown in this image (callout 2).

Display sample predefined aggregated number of
contacts for an account filter on a search query

Workspace supports two types of aggregates:

  • Real-time aggregates

  • Non-real-time aggregates

Real-Time Aggregates

These aggregations follow computed patterns using the available object data and provide real-time updated values. Here's list of these aggregates:

Object Aggregated Fields

Account

  • Number of Contacts

Opportunity

  • Number of Contacts

  • Number of Revenue Lines

Non-Real-Time Aggregates

These aggregates calculate values across fields on the given record, its related objects, and parent-child objects. For example, the aggregate last interaction on an account is calculated by looking at all the activities (related object) on that account, then sorting (aggregate function) them by date. Such aggregations aren't calculated in real time. Their values are recalculated and updated every time the job "Update Aggregates" is run. See the topic Monitor Adaptive Search Background Processes for more information about this job.

Here's a list of the non-real-time aggregates:

Object Aggregated Fields

Account

  • Last Call Made

  • Number of Calls Made

  • Number of Emails Sent

  • Last Email Sent

  • Last Completed Activity

  • Last Completed Call Activity

  • Last Completed Email Activity

  • Number of Completed Activities

  • Number of Completed Call Activities

  • Number of Completed Email Activities

  • Next Task Due

  • Number of Open Leads

  • Number of Open Opportunities

  • Open Opportunity Revenue

Contact

  • Last Call Made

  • Number of Calls Made

  • Number of Emails Sent

  • Last Email Sent

  • Last Completed Activity

  • Last Completed Call Activity

  • Last Completed Email Activity

  • Number of Completed Activities

  • Number of Completed Call Activities

  • Number of Completed Email Activities

  • Next Task Due

  • Number of Open Leads

  • Number of Open Opportunities

  • Open Opportunity Revenue

Lead

  • Last Call Made

  • Number of Calls Made

  • Number of Emails Sent

  • Last Email Sent

  • Last Completed Activity

  • Last Completed Call Activity

  • Last Completed Email Activity

  • Number of Completed Activities

  • Number of Completed Call Activities

  • Number of Completed Email Activities

  • Next Task Due

Opportunity

  • Last Call Made

  • Last Email Sent

  • Last Completed Activity

  • Last Completed Call Activity

  • Last Completed Email Activity

  • Number of Completed Activities

  • Number of Completed Call Activities

  • Number of Completed Email Activities

  • Next Task Due

  • Number of Assets

  • Number of Competitors

  • Number of Quotes

  • Number of Service Requests

Non-real-time aggregates are categorized based on:

  • Interaction fields:

    • Number of Calls Made

    • Last Call Made

    • Number of Emails Sent

    • Last Email Sent

  • Activity fields:

    • Number of Completed Email Activities

    • Last Completed Email Activity

    • Number of Completed Call Activities

    • Last Completed Call Activity

    • Number of Completed Activities

    • Last Completed Activity

  • Related objects:

    • Number of Open Leads

    • Number of Open Opportunities

    • Open Opportunity Revenue

    • Number of Assets

    • Number of Competitors

    • Number of Quotes

    • Number of Service Requests

Enable Field Aggregates

Here's how to enable aggregated fields.

  1. Navigate to the Setup and Maintenance and go to:

    • Offering: Sales

    • Functional Area: Sales Foundation

    • Task: Configure Adaptive Search

  2. From the Configure Adaptive Search page, click Setup > Advanced.

  3. Enable the aggregate fields you want to see for the objects enabled in Adaptive Search.

  4. After making your selections, click Publish.

From time to time you may want to export data from Workspace for offline viewing and verification. For example, a sales manager might want to export a list of accounts to perform a more in-depth analysis of their sales team or for reporting purposes. Only sales manager and sales administrator roles are granted the predefined security privilege ZCA_WORKSPACE_EXPORT to access the export data feature in Workspace.

The Export List button enables you download data from Workspace as a comma-separated values file. You can then use this file to view or analyze your data offline.

Click Export List to download all data in the result set. The result set is determined by the columns displayed in the Workspace UI. Export doesn't include data for hidden columns. It includes all the rows filtered by the current filter criteria applied.

The default number of rows to export is 2000 and the maximum limit is set at 10000 rows. You can change the default number of rows by changing the Maximum Number of Records for Export parameter from the Parameters tab on the Configure Adaptive Search page. See the related topic Edit Adaptive Search Parameters for more information.

When the maximum limit of rows to export is reached, a warning message is displayed prompting you to click Continue to export the first 2000 rows in the result. This action generates a file containing the first 2000 rows of the result set. If you don't want to export the result set, click Cancel to return to the Workspace UI.

The exported file contains the results set data displayed in the same column headers and in the same order as displayed in Workspace.

Note: You can also export personally identifiable information (PII) if you have the required access to view PII attributes in Workspace.

Workspace Extensions

Users with permission to access a custom object can search on it from the Workspace UI, search on one or more fields within the custom object, retrieve search results, and create saved searches for the custom object. Fields are searchable both in the Search box and in filters. Searching on top-level custom objects and their custom child objects is supported. Custom child objects of standard objects are also supported.

Adaptive Search supports predefined relationships between the ready-to-use standard business objects. It also supports one-to-one and one-to-many custom relationships between standard and custom objects. In addition, one-to-many relationships between objects and custom objects can also have a many-to-many relationship between each other. For example, a service request can have multiple employees working on it. At the same time, a single employee can work on multiple service requests. In this scenario, you would create a many-to-many relationship between the Service Request and Resource objects, where the related records from both objects store their primary identifiers in an intersection object.

Custom fields and custom child objects must be published from the sandbox before you configure Adaptive Search to include them. You can't configure Adaptive Search inside a sandbox. Follow this standard process:

  1. Create the custom fields and custom child objects using Application Composer while working in a sandbox.

  2. Publish the sandbox.

  3. With no sandbox open, configure the search behavior you want in Adaptive Search as described in this chapter and publish the new configuration.

Note: If you have dynamic choice list fields included from a custom object to a standard object, such as an Opportunity, then the standard object attributes that you selected by setting the Include in Object Reference check box are displayed in the custom object list page. However, the custom object attributes won't be available in the standard object list page because dynamic choice list fields aren't supported from standard objects to custom object.

Synchronization of Custom Objects, Custom Child Objects, and Custom Fields to Workspace

When you launch the Workspace search configuration, all custom attributes published using Application Composer and the sandbox are synchronized to the Workspace configuration UIs. It may take a little time to synchronize all custom objects, custom child objects and custom fields to the Workspace search setup. If the searchable attribute is set to true in Application Composer, all custom attributes for standard top level objects and custom objects are enabled for indexing by default. However, if the searchable attribute that you want isn't set to true, then you must explicitly enable it for indexing.

Setup is done on the Advanced setup tab. You select the business object you want to set up in the left pane of the tab, and set the object's search properties in the right pane. See the topic How Search Attribute Behavior is Modified for more information.

Configure Deep Links for Workspace

Deep links are links that point to another page. You can embed default Workspace deep link URL patterns for the supported and custom objects to any web page as a link. By clicking these deep links, your sales and service users can go directly to the details of the corresponding record within the context of Workspace.

Deep Link URL Patterns

Here's an example of the standard direct URL link to for the Account business object:

https://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=
itemNode_workspace_workspace&fndTaskItemNodeId= ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3B
entityName%253DAccount %253BsubTabName%253DOverview%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B 

In some cases, an additional parameter, subTabName, is also included in the URL. For example, this sample URL syntax allows direct links to the specified subtab:

http://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=
itemNode_workspace_workspace&fndTaskItemNodeId=ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3B
entityName%253D<EntityName>%253BsubTabName%253D<SubTabName>%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B

If you want the selected record to open in inline mode, just add &action=EDIT_INLINE to the end of the URL. For example, this sample syntax open your record ID in inline mode:

http://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=
itemNode_workspace_workspace&fndTaskItemNodeId=ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3B
entityName%253D<EntityName>%253BsubTabName%253D<SubTabName>%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B&action=EDIT_INLINE
Note: If you don't specify &action=EDIT_INLINE, records open in inline mode by default.

You can also configure deep links to open selected records in dynamic and nested tabs by adding &action=EDIT_IN_TAB to the end of the URL. For example, this sample syntax opens your record ID for edit in a dynamic tab:

http://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=
itemNode_workspace_workspace&fndTaskItemNodeId=ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3B
entityName%253D<EntityName>%253BsubTabName%253D<SubTabName>%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B&action=EDIT_IN_TAB

In the above sample syntax, you must replace the <RecordID> with the actual value from your environment. To get this value, use the this sample SQL syntax to retrieve a record ID for a service request that has an SR Number value of SR0000000002.

select sr_id from fusion.svc_service_requests where sr_number = 'SR0000000002'
Note: For deep links to Workspace saved searches, the <Saved_Search_UUID> should belong to the same entity as the <RecordID>.

For example,

https://<hostname>:<port>/fscmUI/faces/deeplink?objType=ZCA_WORKSPACE_REQUEST&obj
Key=savedSearchUuid%3D<Saved_Search_UUID>%3entityName%3D<EntityName>%3BrecordId%3D
<RecordId>%3BsubTabName%3D<SubTabName>&action=EDIT_INLINE

A URL example to a default action to a Workspace List page is as follows:

https://<hostname>:<port>/fscmUI/faces/deeplink?objType=ZCA_WORKSPACE_REQUEST&action=NONE

Here's an example deep link URL to a default action for a saved search List page:

https://<hostname>:<port>/fscmUI/faces/deeplink?objType=ZCA_WORKSPACE_REQUESTobjKey=savedSearchUuid%3D<Saved_Search_UUID>&action=NONE

Workspace Deep Link Configuration for Supported Business Objects

For each of the supported business objects, the table lists:

  • The URL pattern syntax

  • Whether or not the URL pattern supports a subtab name for the specific object

Tip: Copy the first part of the URL, https://<hostname>:<port>/, from your instance's actual home page.

Business Object URL Pattern Supported Subtabs

Account

https://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=itemNode_workspace_workspace&fndTaskItemNodeId=
ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3BentityName%253DAccount
%253BsubTabName%253DOverview%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B 
  • Overview

  • Profile

  • Sales Account Team

  • Contacts

  • Assets

  • Opportunities

  • Quotes

  • Leads

  • Relationships

  • Recommendations

  • Notes

Activity

https://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=itemNode_workspace_workspace&fndTaskItemNodeId=
ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3BentityName
%253DActivity%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B

None

Asset

https://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=itemNode_workspace_workspace&fndTaskItemNodeId=
ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3BentityName
%253DAsset%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B 

None

 

 

 

Contact

https://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=itemNode_workspace_workspace&fndTaskItemNodeId=
ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3BentityName
%253DContact%253BsubTabName%253DOverview%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B 
  • Overview

  • Profile

  • Team

  • Opportunities

  • Leads

  • Assets

  • Relationships

  • Recommendations

  • Notes

  • Activities

  • Conversations

Custom Object

http://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=itemNode_workspace_workspace&fndTaskItemNodeId=
ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3BentityName
%253D<XXXX>%253BsubTabName%253DSUMMARY%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B2 56%3B%3B%3B 
Replace XXXX with the custom object's API name

None

Lead

https://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=itemNode_workspace_workspace&fndTaskItemNodeId=
ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3BentityName
%253DLead%253BsubTabName%253DSUMMARY%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B 
  • Summary

  • Contacts

  • Qualifications

  • Sales Team

  • Activities

  • Responses

  • Notes

  • Opportunities

  • Conversations

  • Analytics_1

  • Analytics_2

  • Analytics_3

Opportunity

https://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=itemNode_workspace_workspace&fndTaskItemNodeId=
ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3BentityName
%253DOpportunity%253BsubTabName%253DSummary%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B 
  • Summary

  • Quotes

  • Contacts

  • Opportunity Team

  • Opportunity Partner

  • Activities

  • Notes

  • Assessments

  • Leads

  • Conversations

Partner

https://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=itemNode_workspace_workspace&fndTaskItemNodeId=
ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3BentityName
%253DPartner%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B
  • Overview

  • Profile

  • Partner Account Team

  • Opportunities

  • Contacts

  • Activities

  • Enrollments

  • Notes

  • Deals

  • Leads

  • Conversations

  • Service Requests

  • Business Plans

  • Assets

  • Assessments

Partner Contacts

https://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=itemNode_workspace_workspace&fndTaskItemNodeId=
ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3BentityName
%253DPartnerContact%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B

None

Quotes and Orders

https://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=itemNode_workspace_workspace&fndTaskItemNodeId=
ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3BentityName%253DSalesOrderHeader%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B 

None

 

 

 

Service Requests

https://<hostname>:<port>/crmUI/faces/FuseOverview?fndGlobalItemNodeId=itemNode_workspace_workspace&fndTaskItemNodeId=
ZCA_CC_INTERACTIVE_UI_CRM&fnd=%3BentityName
%253DCRMServiceRequest%253BrecordId%253D<RecordID>%253B%3B%3B%3Bfalse%3B256%3B%3B%3B 
  • Summary (Default)

  • Messages

  • Interaction History

  • Contacts

  • Team

  • Activities

  • Actions and Plans

  • Social

  • Linked Articles

  • Milestone Details

  • Part Details

  • Work Orders

  • Audit History

  • Connected Asset

 

 

 

Manage Workspace Smart Actions

You can manage predefined Workspace actions, such as Create an Appointment, Create a Task, and Create an Opportunity, using the Smart Actions administration tool in Application Composer. Smart actions are actions that are specifically mapped to a client application, such as Workspace, and displayed to users only when specific conditions are met.

You can control which actions are available to Workspace for display at runtime and set the order in which actions are displayed to users. For example, you can use the tool to:

  • Enable or remove an action by selecting or clearing the Enabled check box.

  • Change the runtime display sequence of actions by clicking Reorder. For each set of rows within an object category, drag and drop table rows until you achieve the desired row order.

Here's how.

  1. Create a unified sandbox and navigate to the Smart Actions administration tool in Application Composer, under Common Setup.

  2. Using the Actions search box, look for the action that you want to enable, hide, reorder, modify and so on.

  3. If you make changes to predefined actions be sure to publish the sandbox, sign out of the application, and sign back in.

  4. Verify your changes in Workspace.

FAQs for Adaptive Search and Workspace

This section contains some frequently asked questions (FAQs) when setting up and maintaining Adaptive Search and Workspace functionality. Scroll or search to find answers to common questions.

How can I specify which Adaptive Search objects to display in the Workspace UI?

You can selectively hide or show which Adaptive Search-enabled, top-level objects to expose in the Workspace UI. This feature provides access to an object through the Adaptive Search REST APIs, without making the object available to salespeople in Workspace.

For example, your salespeople might want to use an object solely from their mobile device and no longer want to view it from the Workspace UI. To allow this, you can navigate to the Configure UI tab in the Configure Adaptive Search setup task and deselect the Display in UI check box for that object.

What security configuration changes does Workspace support?

Workspace supports standard, predefined job roles, custom job roles, and standard, predefined data security predicates. Workspace doesn't support custom data security predicates however. If your deployment uses custom data security predicates that impact data used by Workspace, you can either remove these custom predicates and replace them with standard, predefined data security predicates or adopt the Access Groups feature. See the Access Groups chapter in the Securing CX Sales and B2B Service guide for more information.

How can I view and assign a default saved search for a role?

To view and assign a default saved search for a role, you must fulfill all of the following conditions:

  • Have the ZCA_MANAGE_INTERACTIVE_LISTS_SAVED_SEARCH privilege so that you can view the Set Defaults tab

  • Permission to view the object underlying the saved search to be assigned (for example, to assign an account default saved search, you must have permission to view the account)

Note: The search results returned may differ for each user as it depends on the role each user has.

How can I display contact information in the Workspace on a Service Request where no Account exists?

Primary Contact is considered a Contact if an Account exist for a Service Request. If an account doesn't exist for a service request, then the Primary Contact is considered as a Consumer. To display the contact information in the Workspace on a service request where no Account exists, you must expose Consumer fields in the Edit Columns panel of your search results.

The fields to expose are Consumer: Name, Consumer: Primary Address, and Consumer: Primary Phone. You must make sure these fields are enabled for Workspace and enabled for UI display before making them available on your service request search results page. See the Enable Fields for Display as Filters and Search Result Columns topic for details.

You can then add which columns to display and in what order on the Service Request page by clicking the Edit Column (pencil icon on the far right of the Workspace UI). See the topic Change Columns Displayed in Search Results for more information.

Why is my Adaptive Search publish process taking time to complete?

The Publish process publishes the Adaptive Search configuration you set up in the Quick Setup and Advanced Setup UIs. You must click Publish to run the process each time you make changes on the Setup tab. Your changes become effective when the process completes. The variations in the time it takes for the successful completion of the publish process is mainly due to the volume of data, the number of objects enabled, and the number of attributes selected for each object.

For example, if you publish more attributes and more objects, then it takes more time to complete the publish and indexing process. You can improve the performance by removing any attributes that you don't want to be indexed. You can also monitor the progress of the publish process. Your configuration is live when the process completes successfully.

Note: The Publish process should be completed before running the Periodic refresh process.

Can I modify or translate saved searches using the User Interface Text tool?

No. You can't use the User Interface Text tool to modify or translate predefined Workspace saved searches. However, you can select Manage Saved Searches to create a copy of the saved search and rename it to suit your business requirements. If you translate the text, ensure you use the current language of the assigned users of the saved search.

What does the fuzziness level for fuzzy searches mean?

The percent sign (%) is the character used for fuzzy searches. The number of the % indicates how many characters in the search term will be ignored by the Adaptive search engine when it runs the query. The position of the % indicates the number of characters from the beginning of the term that must match exactly with words in the result set. The following search strings illustrate how this character is used in Workspace:

  • app%ly indicates that a matching word must begin with "app", and differ from "apply" by only 1 character.

  • a%%pply indicates that a matching word must begin with "a", and differ from "apply" by only 2 characters.

The default fuzziness level is set as 1 character. See the topic Edit Adaptive Search Parameters for information.