46Configuring, Extending, and Integrating Sales

This chapter contains the following:

Overview of Extending the CX Sales Applications

Oracle CX applications offer many different ways to configure, extend, and integrate its services, components, and modules.

Here are just a few of the capabilities:

  • Modify objects and user interfaces (UIs).

  • Change the appearance and theme of the UIs.

  • Configure the Home page by adding announcements and changing navigation.

  • Change the structure of the springboard and modify the Navigator.

  • Modify the help configuration.

  • Create interactive guides to help your users learn about the applications.

  • Access a rich set of subject areas around which to build your own reports.

  • Configure reporting dashboards by adding new reports or changing the layout.

  • Create copy maps to map fields or add information between copied business objects.

  • Configure security components.

  • Use web services to integrate the services.

  • Export data, modify it, and then import it back into the services.

  • Integrate with other applications to enhance the functionality, including synchronizing Financials Accounts to the sales applications.

Note: For more information about configuring online help, see the Common Components chapter.

Modify Pages and Change Text

Use Oracle's configuration tools, Application Composer and Page Composer, to modify application pages. Use the strings editor to modify text in the application pages.

For example:

  • Create a new object and related fields, then create new pages where that object and its fields are exposed to users.

  • Add tabs hidden by default to application pages.

  • Edit the UI at runtime by showing or hiding fields and tables.

  • Change the order of regions, or change a dashboard page layout.

  • Change the default text in the UI, for example, by replacing a term with another term throughout the applications.

Map Fields Between Applications

Copy maps are default mappings of fields between objects. For example, when you convert a lead to an opportunity, the application uses the copy map defined for the Lead and Opportunity objects to determine what to name the leads fields that are carried over to the newly created opportunity. Using Oracle Application Composer, you can create copy maps for several sales business objects, thus allowing you to control the mapping.

Here are some use cases:

  • Create maps to change the default mapping between fields when:

    • Leads and opportunities are copied from responses

    • Opportunities are created from leads

    • Opportunities are created from partner deal registrations

    • Opportunities are copied from existing opportunities

  • Use Groovy scripting to include information about the lead on a new opportunity converted from a lead.

Integrate Applications with Web Services and Use Import and Export

You can use web services to integrate with your external applications. You can also use import management to import and export large amounts of data into and out of the applications.

Example web service integrations include:

  • Integrate sales applications with back-office applications.

  • Create web-based portal applications that access sales applications through a web services interface.

Example import use cases include:

  • Import products into the product catalog

  • Import users

  • Import sales accounts

Configure Security Components

If the predefined security configuration doesn't meet your business needs, then you can make changes. For example, the predefined Sales Representative job role includes sales forecasting duties. If some business groups in your organization have the sales managers perform forecasting tasks instead of the sales representatives, then you can create a company-defined Sales Representative role without those duties. Alternatively, if a predefined job role is too narrowly defined, then you can create a job role with a greater range of duties than its predefined equivalent. See the Securing CX Sales and B2B Service guide for more information.

Synchronize Financials Accounts to Sales Applications

After users create accounts and contacts in Oracle Financials, use the scheduled process, Synchronize Financials Cloud Accounts and Contacts, to synchronize the data into the sales applications. See the related link in this topic for more information.

Integrate Sales Applications with Other Products

For additional functionality, you can integrate your sales applications with other products, including, Oracle E-Business Suite, JD Edwards EnterpriseOne, Siebel CRM, Oracle Eloqua, and Oracle Configure, Price, and Quotes (Oracle CPQ).

Summary of This Topic and Where to Find More Information

To find out where to get more information about the extensions and configurations discussed in this topic, see this table:

Functionality or Configuration Where to Find More Information

Configure the help system

See:

  • Common Components chapter in this guide

  • Oracle Applications Cloud Configuring and Extending Applications

Create interactive guides to help your users learn about the applications

See the related topic, below: Manage Guided Learning

Configure the Home page, the Navigator, and the springboard

See:

  • Common Components chapter in this guide

  • Oracle Applications Cloud Configuring and Extending Applications

Change the UI

See:

  • Oracle Applications Cloud Configuring Applications Using Application Composer guide

  • Oracle Applications Cloud Configuring and Extending Applications

  • The chapters on extending sales business objects in this guide

Use Copy Maps

The Leads, Opportunities, and Extend Leads and Campaigns chapters in this guide

Use Oracle Business Intelligence reports and analytics

Oracle CX Creating and Administering Analytics guide

Synchronize Financials Accounts to the Sales Applications

See the related topic, below: Synchronize Financials Accounts

Integrate Applications Using Web Services and Use Import/Export

The chapter in this guide on import and export, as well as the article on sales web services (1354841.1) available on My Oracle Support.

Integrate the Sales Applications with Other Products

See the article on sales integrations (1962226.1) available on My Oracle Support.

Application Composer is a browser-based configuration tool that enables business analysts and administrators, not just application developers, to extend their applications. Make the type of data model changes which, in the past, could only be made by application developers. For example, easily create a new object and related fields, then create new user interface pages where that object and its fields are exposed to users.

Application Composer is a design time at runtime tool, which means that you can navigate to Application Composer directly from any application, make your changes, and see most changes take immediate effect in real time, without having to sign out and sign back in.

Note: To see your changes in real time, always use the Navigator to navigate to the runtime page that you changed. Then navigate back to Application Composer to continue making changes. In other words, when making application changes (and testing them), restrict your usage to a single tab. Don't work across multiple browser tabs, because Application Composer doesn't support this type of usage.

You can use Application Composer to configure Oracle's Sales and B2B Service, Supply Chain Management, and Project Management applications.

Application Composer is supported for use only in English. Additionally, Application Composer isn't supported for use with iPad devices.

Application Changes for Nondevelopers

Application Composer hides the complexity of modifying applications by leveraging a set of standard design patterns and wizards. You focus on the application changes that your business requires (object model extensions and layout changes, for example), and Application Composer creates the underlying object artifacts for you.

Using Application Composer, you can make application changes such as the following:

  • Modify objects by adding new fields, or create entirely new objects.

  • Create foreign key-based relationships between two objects.

  • Modify user interface pages by exposing your newly created fields for an object, or create an entirely new work area for your custom objects.

    Expose object relationships in the form of subtabs on pages.

  • Write application logic, such as triggers, validation rules, and workflows, for an object, or for use across multiple objects.

  • Implement functional and data-level security for custom objects.

  • Enable objects for custom reporting.

Working in a Sandbox

To make most application changes, you should work in a sandbox. In fact, many functions in Application Composer aren't available until you enter into an active sandbox. You use sandboxes to make application changes and test them without impacting other users in the environment. Wherever possible, make changes to the application in a sandbox rather than making direct changes in the mainline environment.

Sandboxes set apart untested configuration changes from the mainline environment. This lets you test your changes in a sandbox first, before publishing it. After publishing, your changes become available in the mainline metadata, or other sandboxes after they're refreshed, so that everyone can see your changes. Mainline metadata is the primary branch of metadata a sandbox is published to.

To learn more about sandboxes, see the related topic Overview of Sandboxes.

Accessing Application Composer

Access Application Composer at runtime by using the Navigator menu, and selecting Application Composer under the Configuration category.

The first view of Application Composer is the main Overview page, which is the entry point into all your task options.

Getting Started

From the main Overview page:

  • Use the object tree to select the object you want to modify. Or, click the New icon to create a new object.

  • Use the links in main Overview page, also known as the local area, to select a task. Or, use the links in the Common Setup pane.

Use Page Composer to Extend Pages

Overview of Configuring Sales Pages Using Page Composer

Configure the look and feel of user interface (UI) pages using Page Composer:

  • Make changes on a single page for all users or only a subset. For example, you can enable a field that's hidden or make a field required.

  • Create saved searches (lists) in the different work areas. These can be used as filters in actionable infolets.

  • Specify which columns display in the summary tables in the work area lading pages.

  • Create new infolets and create different default views of infolets for different sets of users.

This chapter covers:

  • Points to consider before you configure pages

  • How to configure standard desktop pages, landing pages, and dashboards

  • How to configure application pages

  • How to use Direct Selection mode to make user interface changes

  • How to work with components for configure pages

Note: Page Composer supports two editing modes: Add Content and Select. Use the Add Content mode to navigate to different tabs and windows on a page and to add content on the Partner Relationship Management's Partner Portal UI Shell. You can make enable fields and make other configurations only in the Select mode.

Differences Between Using Page Composer and Application Composer

You can use multiple tools to configure the UI. This topic highlights the differences between the types of configurations you can do using Application Composer and Page Composer.

Key Differences

Basis of Comparison Page Composer Application Composer

Configuring the page you're viewing

Configure a UI page you're viewing and see your changes reflected immediately on that page.

You can use Page Composer to make changes to one page at a time. For example, if you make a field required on the Edit Infolets page, the field isn't automatically required on the Create Infolets page.

You make your configurations in Application Composer. You can then test your work by navigating to the appropriate page.

Because you use Application Composer to configure application objects, if you make a field required, it affects all interfaces where that field appears.

Supported interfaces

Application UI

  • Application UI

  • Mobile

  • Microsoft Outlook

Creating your own fields and application objects

Not supported.

You can add custom fields and entirely new objects.

Creating saved searches

Create and edit saved searches for users. The saved searches provide saved search criteria to speed up common searches. You can also use them as filters in actionable infolets.

Not supported.

Tailoring your configurations for users with different job roles

Supports different levels of configurations for application pages.

Supports configurations by job role or for all users.

Configuring external-facing partner pages

You must use Page Composer to configure all external-facing partner pages, such as the partner registration page and the partner portal landing page.

You must use Application Composer to configure only for partner pages internal to your organization, such as the partner Overview page.

What You Can't Do in Page Composer

Using Page Composer, you can't do these tasks:

  • Change either the data or functional security for a page. While you can hide some components, you must change the security setup to control access.

  • Filter or reorder lists of values.

  • Add any code, validation logic, or scripting to the buttons or fields.

  • Add call outs to other APIs to populate fields with values.

  • Change the selections that appear in the Navigator menu.

  • Configure the Search region inside Search and Select dialog box.

Configure Sales Pages Using Page Composer

You can use Oracle Page Composer to configure Sales pages in a sandbox while you're working in the application. You can make your UI configurations available to all users or to a subset of users, for example, only to partners or to users with a specific job role.

Oracle Page Composer is a page editor, developed as part of Oracle WebCenter, for revising the layout and content of application pages. Its full capabilities are described in the Oracle Fusion Middleware User's Guide for Oracle WebCenter and in the Oracle Fusion Applications Extensibility Guide.

You can use Page Composer, also known as Oracle Composer, for performing the following types of configurations in your sales application pages:

  • Simple UI editing functions, such as showing and hiding fields, changing field labels, and making fields read-only or required

  • Changing page layout and adding Oracle BI Publisher reports and other content to dashboard pages

  • Creating new infolets

  • Creating saved searches (also called saved lists) for others in the organization

  • Configuring the display of search results in tables

Note: If you're planning to configure the UI for a specific job role, then you must have that job role assigned to you so that you can test the configuration in the sandbox.

How to Open Page Composer

To open Page composer, create and enter a sandbox with Page Composer as one of the tools and select Page Composer from the Tools menu. If you're planning to use Page Composer to make changes for specific job roles, then you must create a separate sandbox just for Page Composer. The other tools don't support making changes by job role.

  1. Activate a sandbox.

    The active sandbox name appears at the top of the page.

  2. Click the user image or name and select Edit Pages from the Settings and Actions menu.

Page Composer Modes

When configuring sales pages, you can use Page Composer in one of two modes: the Add Content mode and the Select mode. The following figure shows a partial screen capture of the Page Composer toolbar with the two modes highlighted by callouts.

  • Use the Add Content mode (highlighted by callout 1 in the following figure) to move, add, and edit regions on dashboards and external-facing partner pagers. You also use this mode to create saved searches, specify search result content, and to navigate in the UI when you're in Page Composer.

    You're in the Add Content mode when you first open Page Composer. You can also select this mode by clicking Add Content on the top left corner of a page.

  • Use the Select mode (callout 2), which you can activate by clicking Select, to configure the properties of different UI elements such as fields and table columns.

    Page Composer toolbar with callouts highlighting
the Add Content and Select modes

Add Content Mode

Use the Add Content mode to do the following:

  • Configure the content on dashboard pages, including the Welcome page in the desktop UI.

    Dashboards pages are the pages that users land on when they navigate to work areas using the Navigator. Dashboard pages display analytics, notifications and other information.

  • Configure all of the external-facing landing and transactional partner management pages.

  • Configure the table display of search results.

  • Create saved searches (saved lists).

  • Navigate to other pages while working in Page Composer.

When you open Page Composer, the application opens in the Add Content mode automatically. On pages that support configuration in this mode, such as the sales dashboard in the following image, different regions are highlighted with borders and display configuration controls.

The following screenshot shows a partial screen capture of an application page with the different Add Content features highlighted by callouts.

  • A bar appears at the top of the page indicating that you're in editing the page in Page Composer (callout 1).

  • You can change the column layout of the page by clicking Change Layout (callout 2).

  • You can move a region, by grabbing its toolbar (callout 3) and dragging it to a different position.

  • You can add a new tab (callout 4).

Partial screen capture of an application page showing
the different Page Composer Add Content mode features highlighted
by callouts described previously

You can also make changes in each region:

  • You can remove a region by clicking Close, the icon at the top right-hand corner of the region.

  • You can add content by clicking Add Content.

  • You can add a new region by clicking one of the icons to the right of the Add Content button. These icons specify where in the page the new region is created.

Select Mode

In the Select mode, a border appears around individual fields and other UI elements as you move your cursor over them.

Clicking within a border for a UI element that supports configuration displays a menu with one or both of the following options: Edit Component and Edit Parent Component.

The following screenshot shows the Edit Component menu in the Page Composer Select mode.

Edit Component menu in Page Composer Select mode

Not all UI elements support configuration, so these editing options aren't always enabled.

You use the Component Properties window to make your configurations. Not all the configurations are available on all the UI elements, so the content of this window varies. The following screenshot highlights the different components with callouts.

  • To make a field read-only, you select the Read Only option (callout 1).

  • To make a field required, you select the Required option (callout 2).

    Note: Before making a field required, the field must display a value. If it doesn't, then cancel out of this window and enter the value first.
  • To hide the field, you deselect the Show Component option (callout 3).

Screen capture of the Component Properties window
with callouts highlighting functions described previously
Note: Some UI components are protected from updates to preserve the product business logic. For example, if a field is read-only because of a security privilege defined in the application, you can't make it editable in Page Composer.

How to Edit the Partner Portal UI Shell Using the Page Composer Source View

Channel partner portal administrators can use Page Composer's Source View to configure the header and footer areas of the pages partners use to register themselves and sign in after they're registered. This is the only sales page which supports this mode. You can use this mode to add a company logo, copyright information or links, for example.

To configure the partner portal UI shell, you must activate a sandbox and select the Update Partner Portal UI Shell task in the Channel dashboard.

To learn more about working in the Source view, see the Oracle Fusion Middleware User's Guide for Oracle WebCenter.

How to Make Configurations Available to Different User Groups

You can make your configurations available to different subsets of users.

When you launch Page Composer, you must select one of the following configuration layers:

  • Site: Your configurations are visible to all users.

  • External or Internal: Depending on your selection, your configurations are visible to either internal users (your employees) or to external users (your partners or anonymous users).

  • Job Role: Your configurations are visible to users with the job role you select. The list of available job roles includes all the job roles assigned to you directly and any job roles that are inherited by those job roles.

    Note: If you created your own job roles, then you must run the Retrieve Latest LDAP Changes process from the Scheduled Processes work area before the job roles are available for selection.

By default, configurations you made at a higher level are propagated to lower-level layers, unless you deselect these layers in the Include column.

Note: The Welcome page in the desktop UI doesn't support different configuration layers. You must configure this page at the site level.

FAQs for Page Composer

What do I do if Page Composer closes while I am navigating in the UI?

If you're using Page Composer in Design mode and trying to navigate between different objects in the application, the Page Composer sometimes closes. That's because it's designed to configure one object at a time. When you no longer see the Page Composer bar at the top of your screen, simply restart Page Composer. Your previous work is preserved in the active sandbox, so you don't have any data loss.

Your end users can personalize a page explicitly (like creating a saved search) or implicitly (like changing table column width). You can revert all such changes made by a specific user using the Personalization page in Application Composer. In the Common Setup region, click Personalization. Search for a user and then click Reset Personalization. All changes made by that user are removed and all pages are restored to the default content and layout as originally delivered. Changes implemented by an administrator using Application Composer and Page Composer are retained, if they exist.

End users can also revert their changes themselves, but only on a page-by-page basis.

Can I edit Expression Language (EL) expressions using Page Composer?

No, Page Composer doesn't allow editing EL expressions to protect the business logic implemented through EL expressions.

Can I use Page Composer to configure all elements on a page?

No, you can't use Page Composer to configure all UI elements on a page. Some UI elements are protected from updates to preserve the product business logic. For example, if a field is read-only because of a security privilege defined in the application, you can't edit the field.

You can't select some page elements in the Select mode of Page Composer. For others, the Edit Component option is disabled or only a subset of the properties are available in the Component Properties dialog box.

Caution: Don't edit the Taskflow Id parameter in Page Composer Task List properties. This may damage page metadata.

In general, you can configure at least some of the properties of the following page components:

  • af:activeOutputText

  • af:inputComboboxListOfValues

  • af:inputDate

  • af:inputFile

  • af:inputListOfValues

  • af:inputNumberSlider

  • af:inputNumberSpinbox

  • af:inputRangeSlider

  • af:goLink

  • af:query

  • af:inputText

  • af:outputFormatted

  • af:outputText

  • af:panelLabelAndMessage

  • af:panelFormLayout

  • af:panelHeader

  • af:richTextEditor

  • af:selectBooleanCheckbox

  • af:selectBooleanRadio

  • af:selectManyCheckbox

  • af:selectManyChoice

  • af:selectManyListbox

  • af:selectManyShuttle

  • af:selectOneChoice

  • af:selectOneListbox

  • af:selectOneRadio

  • af:selectOrderShuttle

  • af:showDetailHeader

  • af:table

  • af:column

  • fnd:applicationsTable

  • af:commandMenuItem

  • af:menu

  • af:panelGroupLayout

  • af:panelTabbed

  • af:group

  • af:commandButton