X

It's All About the Platform.

Querying and Adding Supplementary Data As Tabs In Oracle Sales Cloud

Richard Bingham
Senior Development Manager

A few times we seen the question of how to display supplementary applications data on a new page. Without invasive design-time ADF development, the most common solution is to add a BI report and create an extra link, tab or frame to expose it. This works just fine in most cases, however if you are using Sales Cloud and would like to interact with the supplementary data also (e.g. make immediate edits), then you can use a specific type of tab to your simplified pages.

As shown below, one of the types of tab you can add in Application Composer is called a "Context link" and the inline help text describes this as: 'A context link subtab
displays data from any object. To query for the desired set of data,
apply search criteria including run time values of the current object'.

 

 

So let's look at ways this could this be useful. 

 

 

Snack Buyers

In our illustrative example, our Snacks custom
object has a field to hold the name of the Buyer who is responsible for
purchasing more of a particular type of snack. As shown below this
field is based on the Resource standard object, listing sales
users.

Upon creating the tab a Search Criteria is used to filer the data shown on the tab. In this case it is based on the Resource Name field on the object matching the Buyer field on the current (snack) object. As such the data now becomes dynamic, based on the run-time context.

The result is that we have a second tab on the Snack record user interface, showing more details about the person who is the buyer. This allows users to find them to order more of their favorite snack.

 

 

Note that in the configuration is is possible to enable Create, Edit and Delete options, displaying under the Actions button. As such this allows this inline work in a separate window, but returning to the existing context.

 

Unrelated Data

This example shows how to use the relationship created by the Dynamic Choice List lookup to the Resource Object, and therefore could have been done using the Related Object type of sub-tab. The definition of the Context link however states "any object". As such it does not
limit you to related objects at all, but can show data
from any Custom or Standard Object records in the system (across Application containers).

Shown below, the new tab will display all the Resource object records that have a custom field that flags them as Buyers, allowing you to find alternative people to source your favorite snack.

 

 

 

Although probably rarely realistic, the query may include data from the Snack object record that just happens to match values in a field on the tab target object, again without needing any a formal relationship between them. A simplified example might be a list of Lead records where the buyer name is the same.

As such this simple, but flexible tab creation allows you to provide supplementary information to users to support their work.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.