6Analytics on Interfaces

This chapter contains the following:

These are all the areas on the CX sales interface where your users can view analytics. Some of these pages come prebuilt and can be personalized by your users, and some you need to set up.

Type Description Visibility

Sales Pages

Includes five blank pages that administrators configure and add prebuilt or custom analytics for any area.

Not visible until administrators enable the Sales Pages in Set System Options.

Sales Infolet Page

Comes prebuilt with role-based analytics and infolets. One page for each role.

Not visible until administrators enable the Sales Infolets in Set System Options.

Object Pages

Analytics can be added to the following object page work areas:

For Sales:

  • Leads

  • Opportunities

  • Forecasts

  • Accounts

  • Households

  • Contacts

  • Activities

    For Service:

  • Service Requests

  • Work Orders

  • Queues

Analytics can be added to the object landing page or object edit page, such as the Opportunities page, or the Edit Opportunities page.

Analytics Page

This page is where users can add analyses themselves by searching for the analysis and making it a favorite.

Administrators make custom analytics available for users on the Analytics page by adding session variables on the analysis. These variables can show data specific to the user signed in and viewing her Analytics page.


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. So you can test your changes in the sandbox and then publish it. After publishing, your changes become available in the mainline metadata or other sandboxes after they're refreshed. So everyone can then see your changes in the environment. Mainline metadata is the primary branch of metadata a sandbox is published to.

Why You Need Sandboxes

Today's business landscape is quite dynamic. Companies are expected to respond quickly to address both customer and market needs. So multiple teams need to make application changes at the same time while sharing the same data model and configuration starting point. But you may get conflicts between teams working that way. To avoid such conflicts, sandboxes come in handy.

Unified Sandboxes

You can either use Unified Sandboxes, which is the default feature you get, or opt out of it using the Offerings work area to get classic sandboxes.

With unified sandboxes, you can refresh your sandboxes to bring in the latest changes from the mainline metadata to your sandboxes, and do many other new and versatile sandbox activities. You get a consistent sandbox experience across all configuration tools and a more robust user interface with this feature.

With unified sandboxes, you can do these additional sandbox activities:

  • Select the configuration tools to enable for your sandboxes while creating them.

  • Enable all configuration tools in the same way using the Sandboxes UI. So you get a consistent sandbox experience across tools.

  • Restrict access to various sandbox activities for users. For example, you can specify these access rights for your sandboxes:

    • Full access

    • Edit and preview access

    • View only access

  • View just your application changes without having other context layers hide your content.

  • Test your changes in a preview mode that shows you exactly how your application changes would appear in a published sandbox.

  • Refresh and merge sandboxes with latest changes in mainline metadata from other published sandboxes. After merging all changes, you can publish your sandbox.

  • After opting in to the Unified Sandboxes feature, if you register your target environment in your source environment, you can do these additional migration tasks using the Migration UI:

    • Migrate your changes from the test environment to the target environment without manually downloading and uploading the configuration set file.

    • Move only new changes from the source environment to the target environment.

Sandbox Usage

You typically use sandboxes for either of these purposes:

  • Test-Only: You can make application changes using test-only sandboxes, which you don't want to publish to the mainline code.

  • Publish: Once satisfied with the application changes made in the test-only sandbox, you can replicate these changes in a sandbox that you want to publish. And then publish your changes to the mainline code. This sandbox type is also known as the integration sandbox, because teams working in parallel use this sandbox as the final staging point before publication to the mainline code.

Note: Before each patch or upgrade, publish or delete your sandboxes. If you haven't yet completed your work, restart with a new sandbox.

You get to use unified sandboxes by default. But if you want to use classic sandboxes instead of the default ones, opt out of the Unified Sandboxes feature. You can opt back in, whenever you want. But before you opt out of this feature or opt back in to it, make sure you totally understand what impact that would have. You must publish or delete any sandboxes that are open right now. Once you opt out, you can no longer see the published unified sandboxes. Similarly, once you opt back in, you can no longer see the published classic sandboxes.

Here are a few things to know if you're using unified sandboxes:

  • When you use Application Composer in a publishable unified sandbox, an object can only be edited in any one sandbox in the environment at a time.

  • For value sets, key flexfields, and extensible flexfields, you must deploy changes directly to the mainline environment, not to a unified sandbox. But, for descriptive flexfields, you must deploy your changes to a unified sandbox and test the changes before publishing your sandbox.

  • A unified sandbox is set to only one layer. So while working in a sandbox at a specific layer, you may not see some changes that were made at other layers in previously published sandboxes. But before you publish your sandbox, you can see your changes along with previously published changes done at any other layers in preview mode. So it's a good practice to test and validate your changes in preview mode and then publish your sandbox.

Opt Out or Opt Back In

In the Offerings work area, disable or enable the Unified Sandboxes feature:

  • Offering: Any with the Application Extensions functional area

  • Functional Area: Application Extensions

  • Feature: Unified Sandboxes

  • Opt In Task: Click Continue if you're sure about enabling or disabling this feature.

To make changes to the application, you must first store the changes in an active sandbox. You can either create a sandbox or select an existing one, and make it active. You must activate the configuration tools you want to use in your sandbox. If you plan to use Page Composer in your sandbox and edit pages at a layer other than Site, you need to create a sandbox just for that layer, and activate only Page Composer in it.

Note: You can create up to 20 sandboxes. But, you can increase this limit using the Maximum Number of Sandboxes profile option. In the Setup and Maintenance work area, use the Manage Applications Core Administrator Profile Values task in the Application Extensions functional area.

Create and Activate Sandboxes

Follow these steps to create and activate sandboxes for most configuration tools. For flexfields, use the Manage Descriptive Flexfields task or the Manage Extensible Flexfields task instead.

  1. Click Navigator > Configuration > Sandboxes.

  2. On the Sandboxes page, click Create Sandbox.

  3. Enter a name and description for your sandbox.

  4. In the Publishable field, select Yes or No. If you set this option as No, you can just use your sandbox for testing purposes, but can never publish it.

  5. In the All Tools section, select the tools you want to activate for this sandbox. The context layers for all selected tools are set as Site by default. So the changes you make using these tools affect all users.

  6. If you select Page Composer, you can click the Edit Sandbox Context icon and change the context layer from Site to another layer, for example External. You can find the Edit Sandbox Context icon in the Support Context column.

    Note: If you want to use other tools along with Page Composer in your sandbox, don't change the context layer for Page Composer, even though you can. That's because all tools except Page Composer support only a single context layer, Site. So if you change the context layer for Page Composer from Site to any other layer, all other tools that you might have selected earlier will be deselected.
  7. Click Create to just create the sandbox, or Create and Enter to enter or activate the sandbox after creating it.

Here are a few things to know about activating tools in your sandbox.

  • If you try to use a configuration tool in a sandbox without activating the tool in it, you get a message prompting you to activate the tool. You can add more tools to your sandbox later also.

  • To create and manage saved searches and make UI adjustments (for example, change a table's column width) just for yourself, you must leave your sandbox before making these changes. But if you want to make these changes for others too, then make the changes with Page Composer open, in which case you also must be in a sandbox.

Activate Existing Sandboxes

Follow these steps to activate a sandbox.

  1. Click Navigator > Configuration > Sandboxes.

  2. From the list of sandboxes, if available, find the one you want to activate, and click the Enter Sandbox icon for that sandbox. Your sandbox is activated, and you can see its name on the sandbox bar before the global header. You can use the options available on the sandbox bar to quickly do some activities, such as view sandbox details, publish the sandbox, or leave the sandbox.

After you're done making changes to the application, publish the sandbox to make your changes available to all users. You must have the Administer Sandbox (FND_ADMINISTER_SANDBOX_PRIV) privilege to publish sandboxes. Remember, you can't make further changes in the sandbox once you publish it.

Before you start, do these tasks:

  • Test or validate your changes in the sandbox in preview mode before actually publishing it. If you made changes using Page Composer, don't forget to close it before testing. To preview your changes, on the sandbox bar before the global header, click Sandbox Mode, and select Preview as if Published (Context: All).

    Note: You can see the sandbox bar only when you're in an active sandbox.
  • Resolve all conflicts flagged in the merge log of your sandbox.

To publish a sandbox:

  1. Click Navigator > Configuration > Sandboxes.

  2. On the Sandboxes page, click the name of the sandbox you want to publish.

  3. Click Publish.

    Note: The Publish button might be disabled for your sandbox because of various reasons. For example, you haven't yet made any changes in your sandbox, or the Control Publish Sandbox Action in Production Environment profile option (FND_ALLOW_PUBLISH_SANDBOX) is set to No.
  4. Click Continue to Publish. The sandbox is published to the mainline metadata.

  5. Click Done.

Analytics on Sales Pages

Analytic Prerequisites

You need to complete some infolet display setup steps to ensure that your data shows correctly on the infolet pages. The procedures to perform these setup tasks are detailed in "Getting Started with Your Sales Implementation". The Related Links in this topic will take you to the pertinent sections with detailed instructions.

Set up Infolet Display

The following are the tasks that must be done to enable infolet display:

  • Create your company information.

  • Create your resource hierarchy.

  • Create your accounting calendar and schedule BI processes.

  • Create your sales catalog and schedule BI processes.

Set Up the Sales Pages

Administrators enable the sales pages on the Set System Options page. You can enable as many pages as you want, up to a total of five. Once you have enabled the pages, you add analytics by navigating to the sales page from the white page navigation dots on the home page. You can also use the Sales pages to add role based Service analytics.

Enable the Sales Pages

  1. From Navigator select Structure.

  2. Select Set System Options.

  3. On the Set System Options page, select the box next to the pages you want visible.

  4. Click Save and Close.

Add Content to the Sales Pages

  1. Next to your name on the page is an arrow. Click the arrow and select Edit Pages.

  2. Select Job Role and select the role to which your change should apply. Any analytics you add in this context apply only to the role you define here.

  3. Click OK.

  4. Click Change Layout.

  5. Select a layout.

  6. Click Add Content and Open, and navigate to BI and highlight an analytic to add. Select OK.

Set Up Sales Infolet Pages

The Sales and Sales Infolet pages are where your sales team sees key analytics relevant to their job role. Prebuilt analytics are displayed inside portals on the pages called infolets. The infolets come with a set of default analytics for roles in your organization. You can manage which analytics you want your users to see. You can add prebuilt, or your own analytics to the infolets. You can also change the way the infolets appear on the page, by changing the infolet size, the shape, and so on.

Note that if you're in accessibility mode, only non-graphical report views such as Table, Pivot table, and Tile are supported in Infolets. Charts or graphical views such as Pie and Bar aren't supported in accessibility mode.

Sales Infolet Caching

As you make changes to your infolets, remember that infolets are cached by default. Currently the default setting is to be cached one hour before the existing infolet content is invalidated and refreshed with new content. This means that any new updates to your analytics aren't visible in your infolets for an hour, when the cache is refreshed.

You can manually override this action by opening your analytic in BI, then going to the Advanced tab, and checking the Bypass Oracle BI Presentation Services Cache. Once this check box in enabled your infolet analysis is visible immediately.

This image shows the control to bypass the presentation services cache, and make infolet changes immediately available.

Controls to bypass Oracle BI Presentation Cache

Enable the Sales Infolet Pages

Out of the box the sales infolet pages should be enabled for the standard roles by default. But If you add custom roles, you must enable the sales infolet page for each new role.

  1. Click Navigator, then click Structure.

  2. In Structure, select Set System Options.

  3. In Set System Options, select Social Panel and Sales Infolets.

Edit Infolet Tiles and Views

You can change the way the infolet containers appear on the page.

  1. Click the arrow next to your name and select Edit Work Area Pages. You see the Edit Pages dialog. Select Job Role and select a role. All of the changes you make in this sandbox once saved apply only to employees assigned to the job role you choose. Click OK.

  2. Click the arrow in the infolet and select Edit Tile and Views.

  3. The Edit Tiles and Views dialog appears. Select the size and shape of the infolet. Select Save and Close.

Edit Infolet Content

You can change the analytics that show in any of your sales infolets.

  1. Click the arrow next to your name and select Edit Work Area Pages. You see the Edit Pages dialog. Select Job Role and select a role. All of the changes you make in this sandbox once saved apply only to employees assigned to the job role you choose. Click OK.

  2. Select the infolet you want to change and from the list select Edit Content. The Edit Content Dialog appears. Select Add Content.

  3. The reports directories appear. Navigate to Reports and Analytics > BI Presentation Server > Shared Folders > Sales > Embedded Content. Select the report to add to that infolet and select Add. Publish your sandbox when you're finished with your changes.

Add an Infolet

You can add infolets to your Sales and Sales Infolet pages.

  1. In your sandbox, click the arrow next to your name and select Edit Work Area Pages. You see the Edit Pages dialog. Select Job Role and select a role. All of the changes you make in this sandbox once saved apply only to employees assigned to the job role you choose. Click OK.

  2. On the page where you want to add the infolet, select the documents icon.

  3. Select Create Infolet.

  4. Name your infolet and click Save.

Your new infolet appears on your Sales Infolet Page. You still must add content by following the steps in Editing Infolet Content.

Delete an Infolet

  1. In your sandbox, click the arrow next to your name and select Edit Work Area Pages. You see the Edit Pages dialog. Select Job Role and select a role. All of the changes you make in this sandbox once saved apply only to employees assigned to the job role you choose. Click OK.

  2. Select the menu on the infolet you're deleting and click Delete.

Analytics on Object Pages

Analytics on Object Pages

Administrators can add analytics to object landing and edit pages. The object landing pages are the pages sales teams interact with every day like the Opportunities, Accounts, or Contacts pages. When you add analytics to the tabs in these pages users can see analytics specific to the record they select.

For the object landing pages there are two steps:

  1. Enable the Analytics tab.

  2. Add an analytic to the enabled tab.

For the edit object pages, there are three steps:

  1. Set the "Is "Prompted" filter on the analytic in BI.

  2. Enable the Analytics tab.

  3. Add the analytic to the enabled tab.

Note: The Service Request and Work Order landing pages don't have the option for adding analytics.

Enable Analytics Tabs for Object Landing Pages

The analytics tabs on your object pages don't show by default. Administrators must enable the tabs before they can add analytics to object pages.

Enable Landing Page Analytics Tabs

This uses the Opportunities object landing page as an example. The steps are the same for all of the object landing pages.

  1. In Navigator click Structure.

  2. Choose Opportunities.

  3. On the analytics row, change the value for visible column to "Yes."

  4. Click Save and Close.

Add an Analysis to the Object Landing Page

After the analytics tab is enabled, administrators add the analytic to the landing page tab. This procedure uses the Opportunity landing page as an example. The procedure is the same for all object edit and landing pages.

Add an Analysis to the Opportunity Landing Page Tab

  1. In a specific opportunity, select the Analytics tab. You enabled this tab in the previous section.

  2. At the top of the Home Page click the arrow next to your name and select Edit Pages.

  3. Select Job Role and choose the role to which your change should apply. Any analytics you add in this context apply only to the role you define here.

  4. In Opportunities on the analytics tab click Add Content and navigate to the analysis you want to show on the Opportunity page.

  5. Click Add next to the analysis and close the dialog. The analysis is now added to the Analytics tab.

Enable Sub Tabs and Add Analytics to Object Edit Pages

There are three steps to adding analytics to object edit pages.

  1. Set the "Is Prompted" filter in the analytic in Business Intelligence. This step is used when the requirement is to view contextual data specific to the record selected.

  2. Enable the sub tab on the object page.

  3. Add the analysis to the sub tab on the object page.

All of these steps are done using the Opportunities landing and edit pages. You can use these same steps for any of the object pages listed as analytics work areas in the sub table at the start of this section.

For service, the Service, Work Order, and Queue pages use the same procedures.

Set the "Is Prompted" Filter

For analytics to show on your user Opportunity pages you enable the "Is Prompted" filter on the name or object ID for the analysis. Adding this filter adds an analytic with data that relates only to the opportunity your user is currently viewing.

  1. Open an existing analysis, or create a new analysis in BI.

  2. In the report Criteria sub tab, select the Filter icon for the appropriate column. Under Operator, select is prompted. Leave the other options blank.

  3. Click OK.

Enable Object Edit Page Analytics Sub Tabs

This procedure uses the Opportunity object landing page as an example. The procedure is the same for all object edit pages.

  1. In Navigator click Application Composer.

  2. Select Sales from the Application drop-down list.

  3. Expand Standard Objects and go to Opportunity.

  4. Under Opportunity click Pages.

  5. Under Detail Page Layouts copy the standard layout or select an existing created layout where the Analytics sub tab is added.

  6. Click the Reorder sub tab.

    This shows the Configure sub tab option for the edit object page.

    Configure sub tab dialog for edit object page.
  7. Click OK.

  8. Click Done. The Analytics sub tab now shows on the Edit Opportunity page.

Add Analytics to Edit Object Sub Tabs

The final step is to add an analysis to the Edit Object sub tab you have just enabled. When an analysis is added to the object page, it shows data specific to the signed in user's transaction record. The specific data shows because of the "is prompted" filter being set in the analytic which passes parameters from the transaction record to the analytic. A parameter is visible in the analytic when a filter prompt is added.

  1. At the top of the Home Page click the arrow next to your name and select Edit Pages. The Edit Pages dialog appears.

  2. Select Job Role and choose the role to which your change should apply. Any analytics you add in this context apply only to the role you define here.

  3. In Opportunities on the analytics sub tab click Add Content and navigate to the analysis you want to show on the Opportunity page.

  4. Click Add next to the analysis and close the dialog. The analysis is now added to the Analytics sub tab.

  5. Next step you want to either save the default parameters, or add parameters specific the object your are working with.

    Click Parameters.

    This shows the Parameters button on the Edit Opportunity analytic.

    Parameter button
  6. The parameter used is pageFlowScope variable and is set by default for Opportunity, Leads, Partners and custom object pages. For example, in the case of Opportunity the parameter is #pageFLowScope.biFilterName_OpportunityOpportunityId. To use the default parameter, in the Parameters dialog, click Save. Parameters can be changed by updating the parameter values after clicking Parameter button in the field.

    This shows the parameter value of #pageFLowScope.biFilterName_OpportunityOpportunityId on an Edit Opportunity ID analytic column.

  7. For the objects that aren't pre-populated with the pageFlowScope parameters, you can use one of these sessionScope variables depending on which object page you're on, and the columns available in the analytic.

    • Customer ID: #{sessionScope.zcmAnalyticsCustomerId}

    • Contact ID: #{sessionScope.hzAnalyticsContactPartyId}

    • Contact Name: #{sessionScope.hzAnalyticsContactName}

    • Lead ID: #{sessionScope.mklAnalyticsLeadId}

    • Opportunity ID: #{sessionScope.mooAnalyticsOpportunityId}

    • Partner ID:#{sessionScope.zpmAnalyticsPartnerId}

    For the Service Request detail page, we use pageFlowScope variables not sessionFlowScope variables.

Expose the Refresh, Export, and Print Links on Tabs

When you're working with analytics on tabs on your interface objects, you have the option of exposing the Print, Export, or Refresh links for the analytics you add to the tabs. This provides your users with handy tools for managing analytics on their object pages.

This shows the Refresh, Print, and Export links on an analytic from a tab on the Analytics page.

Action links on the analytics landing page.

How to Expose the Refresh, Export and Print Links

To expose the links for refresh, export, and print on analytics from object tabs, you modify the component properties in Page Composer.

  1. Highlight the analytics tab and click the Edit Component Properties wrench icon.

    This shows the Page Composer option to modify component properties for a analytics tab.

    Analytics tab properties.
  2. In Component Properties dialog, go to View Report Links.

  3. In the View Report Links field,, the following values can be entered:

    • Add "r" to expose the Refresh link.

    • Add "f" to expose the Print link.

    • Add "d" to expose the Export link.

    • Add more than one of these options separated by a comma: r,f,d.

      This shows the View Report Links option.

      View Report Links.

Direct Linking

Direct page linking lets your users drill down on a record without leaving the page. You can add direct page linking for records in most custom objects in CX Sales. When users click the custom object name, or any record with an associated ID value, it opens up a separate window to provide further detail on that record.

There are three parts to direct page linking:

  1. Defining an action link.

  2. Constructing the direct link URL.

  3. Updating the direct link URL and parameters to navigate to a selected record.

Define an Action Link

You can add a direct page URL to any column of an analysis created for a custom object by adding an action link from column properties. Note that the analysis must have a column that holds the identification of the record, such as Record ID in the case of a custom object.

  1. Create or open an analytic that contains a column for the name of the document. Select the gear icon on the column and then from the drop-down list choose Column Properties.

    As an example of this, say there is a custom object called Product Documents. For direct page linking, we want to add the direct URL/deep link to the column that holds the identification of the record. In the following figure, since there is a Product Document column, it would be the Document name that holds the ID of that record.

  2. In Column Properties, select the Interaction tab.

  3. Under Value, for Primary Interaction choose Action Links from the drop-down list.

  4. Click the + icon to add an action link.

    This shows the New Action, Navigate to a Web Page option.

    New action, Navigate to a Web Page link.
  5. Click Create New Action and then from the drop-down list select Navigate to a Web Page.

    This shows the Create New Action for a direct page link.

    Direct page link create new action

Construct the Direct Link URL

You add your specific URL to the action field. These steps show you how to determine the correct URL for your environment. These URLs are examples only.

  1. Add the direct link URL to the Create New Action field. There are direct page links patterns available for objects which can be found by going to Related Topics at the bottom of this section and clicking Direct Page Links: Explained. In this example, you take the direct URL pattern for the Custom Object, which in this case is called Product Docs. To create a direct link to a default summary page tab for a custom object use the direct link URL pattern in the following example:


    Replace XXXX with the custom object's API name, for example, ProductDocs_c. Obtain the API name from the object overview page (click the object's node in the Custom Objects tree in Application Composer).

    Replace the YYYY with the custom object's primary key in the database. In this case, the custom object primary key .comes from the Record_Id column, as shown in the following example:

    https://<hostname>:<port>/<application>/faces/FuseOverview?fndGlobalItemNodeId=CRM_CUSTOM_CARD_ProductDocs_c&fndTaskItemNodeId=CRM_CUSTOM_TAB_ ProductDocs_c&fnd=%3BsubTabName%253DSUMMARY%253BObjectId%253D300100057476089%253B%3B%3B%3Bfalse%3B256%3B%3B%3B

    Note that you can test the URL by replacing the host name with your actual host name and using a valid record value in place of <YYYY>. Put the URL in a browser to see if the record details page appears and the URL is valid.

  2. Once you have determined that the URL is valid, the next step is to embed this URL in the analytic and ensure that the object ID, represented in these instructions as <YYYY> is dynamically retrieved from the analytic whenever the Product Docs name is clicked. When you have added the URL click Define Parameters. The next part of these instructions is to construct the direct link URL.

Update the Direct Link URL and Parameters

The define parameters fields are populated with some prompts and values already. The purpose of these steps is to ensure that the object ID is defined as a parameter.

This shows some Prompt and Value fields on the Create New Action page.

Add parameters and values for direct linking

To update the direct link URL and parameters:

  1. Because you're changing the value of the ID only, delete the default parameters and leave only one parameter mapped to the ID.

  2. Update the first parameter by renaming the Prompt value to ObjectId and set the value to a column value by selecting the record ID from the drop-down list. For example ProductDocs_c.Id.

  3. Paste the URL again in the URL field and replace the ID of <YYYY> value with @{1} as shown in the following example:

    https://<hostname>:<port>/<application>/faces/FuseOverview?fndGlobalItemNodeId=CRM_CUSTOM_CARD_ProductDocs_c&fndTaskItemNodeId=CRM_CUSTOM_TAB_ ProductDocs_c&fnd=%3BsubTabName%253DSUMMARY%253BObjectId%253D@{1}%253B%3B%3B%3Bfalse%3B256%

    This shows the result of the Edit Action page when the correct values are added.

    Edit action dialog with direct page link
  4. Check Hidden.

  5. Click Ok.

  6. Click OK to edit the Action Link window. The Column Properties window appears.

  7. Click the Data Format tab.

  8. Check the Override Default Data Format and select Number for Treat Number As.

  9. Click OK and save.

  10. Select the Results tab. Now the document name column shows the link. When users click the link, they're taken to that record detail in simplified page.

    This shows an analysis with direct links from the document name column. This analysis with links to drill-down detail can be viewed on the Analytics page or any analytics tab.

    Direct links in an analytic

These same steps can be performed for any of the standard objects for sales and service using the direct link format and embedding links in the BI analyses.

Paths and Links to Analytics

Your analytics are stored in BI. You are expressing that analytic that's stored in BI in a different location. So when you add an analytic to an infolet, you need to define that path to the analytic. Navigating away from the page takes you out of editing mode, so it makes sense to get the pathway before you add it to the infolet.

Find Analytic Pathways

  1. From the Navigator, click Reports and Analytics.

  2. Click the directory icon on the Reports and Analytics page.

  3. Go to Sales, Embedded Content, and navigate to the analytic.

  4. Highlight the analytic you want, right-click and click More.

  5. Under your analytic name, click More, then Properties.

  6. From the General area, go to Location and copy the path.

    The path is your report location for your sales infolets.

  7. Click OK.

    Repeat the steps 1 through 6 to find your tile analytics.

ADF Contextual Event Action

Administrators can set the ADF Contextual Event action on the object name or other attribute columns of an object to enable drilling down. When this action is set, the drilling down feature works on the analytics you add to the object tabs, Sales Infolet pages, sales pages, or Analytic page. Users click the column name to see the details for that particular record.

These are the available objects:

  • Opportunity

  • Contact

  • Account

  • Activity

  • Partner

  • Deal

  • MDF Budget

  • MDF Request

  • MDF Claim

  • Business Plan

  • Business Plan Objective

  • Leads

  • Queues

  • Work Orders

  • Service Requests

  • Assets

Set the ADF Contextual Event

You can add this event to any analytic you build as long as it has an identifier for the record. In this case the identifier is Customer ID. For this example you build an analytic that shows Account and Opportunity details.

  1. Create a new analysis from the subject area Sales-CRM Pipeline.

  2. From the Subject Area pane, drag the following columns onto the Selected Columns editing palette:

    • From the Customer dimension, select "Name".

    • From the Customer dimension, select "Customer Row ID".

    • From the Opportunity dimension select "Name".

    • From the Opportunity dimension select "Opportunity ID".

    • From the Facts folder, under Pipeline Facts, select "Opportunity Revenue".

  3. Click the settings gear icon for Customer Name.

  4. Choose Column Properties.

  5. Choose the Interaction tab.

  6. Under Value, Primary Interaction, choose Action Links.

  7. Click the + icon to add a new action.

  8. Click the running man action icon with the + on it. A list of actions comes up.

  9. Choose ADF Contextual Event. Click OK.

    This figure shows the ADF Contextual Event option.

    ADF Contextual Event
  10. In the Column Properties dialog, check Do not display in a dialog if only one action link is available at runtime.

    This figure shows the ADF Contextual Event action link dialog.

    ADF Contextual Event.
  11. Click OK.

  12. Repeat steps 3 through 9 for the Opportunity Name column.

Viewing the ADF Contextual Event Action

The analytic to which you added the ADF Contextual Event can be added on the interface. Using the ADF Contextual Event action, users now have the option to view the additional details of a particular object, or make changes to details on an object pages.

To set your analytic an edit object page, do the following:

  1. Enable the analytic tab on the Accounts page and add the newly created analytic.

  2. Click the Customer Name from the BI report and it opens up the detail page for a particular customer as a dialog box. You can close the dialog box and open up any customer name or opportunity name to get a detail page dialog box.

This shows the drill-down detail for the Edit Account object when the ADF Contextual Event action is added.

Edit account with ADF contextual event

USER_PARTY_ID Session Variable

You can configure analyses to show user-specific analytic data on user Analytics pages. This is done by adding session variables to the analytic. Adding a session variable, such as USER_PARTY_ID tells the application to show only the data that's specific to the signed in user. The variables exist for each user for the duration of a browsing session and expire when the user closes the browser or signs out. There are two types of session variable: system and non-system. Session variables are primarily used when authenticating users against external sources such as database tables or LDAP servers. If a user is authenticated successfully, session variables can be used to set filters and permissions for that session.


To add session variables you select the gear icon on the column name. Then you select New Filter. The USER_PARTY_ID is used on the Employee Login ID column since it tells the application to only show data in this analytic specific to the logged in employee. There are several other session variables and you can choose from the options available when you click in that field.

This shows the New Filter option for adding a session variable that shows an analysis for a signed in user.

Add session variable to analytic.

Embed Analyses and Dashboards

Whitelist Safe Domains

You whitelist safe domains to approve access to specific content. For security reasons, external content can't be added to reports and reports can't be embedded in other applications unless it's safe to do so. Only administrators can add safe domains to the white list.

Only authorized users may access the content. Except in cases where Single Sign On (SSO) is enabled, users are prompted to sign in when they access content on safe domains. After you have added a safe domain to the white list, users need to sign out and sign back in to access content from that source.

  1. Click Navigator > Reports and Analytics.

  2. Click Browse Catalog.

  3. Click the Administration link on the BI Home page.

  4. Click the Manage Safe Domains link.

  5. To allow users to embed their analyses in content located on other domains, enter the name of the safe domain as well as the port. Here are a few formats you can use for port names:

    • www.example.com:<port number>

    • *.example.com:<port number>

    • https:

  6. Select the types of resources you want to allow and block any resource types you think aren't safe. For example, to allow embedding, select Embedding.

Embed Your Content in Other Applications

You can embed your reports in other non-Oracle applications and portals. This is a good way to share content and data among multiple systems. When other users click on embedded content, if you don't have single sign-on, they might have to sign in again to see the content.

Before you can embed a report in other applications or portals, your administrator must add the URL for the target applications or portal to the domain whitelist.

  1. Obtain the URL of the analysis or dashboard you want to embed.

    1. Go to the catalog and open the analysis or dashboard.

    2. In the URL displayed in the browser's address bar, delete "Portal", so that your URL resembles this example, then copy the URL.

      Content Example URL


      http://example.com:<port number>/analytics/saw.dll?Go&Action=prompt&path=%2Fshared%2F<folder>%20<analysis name>

  2. Sign in to the target application or portal, then embed the content inside an iFrame and use the copied URL.