5Extending Simplified Pages

This chapter contains the following:

Overview

Modify Oracle Sales Cloud simplified pages and create page layouts that some or all users can see, depending on the conditions you set. Simplified pages are available for custom objects as well as most standard objects.

This chapter covers:

  • Which simplified pages are extensible, what you can do, and how to modify simplified pages using Application Composer

  • How to modify the springboard and the look and feel of the simplified pages

  • Adding, enabling, or disabling drill down fields

  • What dynamic page layouts are and how you use them

Tip: You can also modify simplified pages using Page Composer. Refer to the Page Composer chapter in this guide to learn more.

To modify simplified pages using Application Composer, select an object that offers a set of simplified pages, such as Opportunity, then select the Pages node. Select the Simplified Pages tab to access that object's configuration pages, where you can modify the simplified page regions that are extensible.

Modifying Oracle Sales Cloud Simplified Pages: Explained

After creating custom objects and updating standard objects in Application Composer, you must create or update user interface pages so your changes are visible to your end users. To work with simplified pages, select the Simplified Pages tab after expanding the object's Pages node. This tab lets you create new pages for a custom object and modify existing pages for standard objects. You can modify these simplified pages (if they are extensible) using Application Composer and also Page Composer. For example, you can show or hide fields, rearrange fields, and add custom fields to simplified pages.

In this topic, you will learn which objects have simplified pages that are extensible, and how to modify simplified pages using Application Composer.

Extensible Content

You can create a set of simplified pages for all custom objects. Many standard objects offer a set of simplified pages, most of which you can modify.

Objects whose simplified pages are extensible have a tab called Simplified Pages when the Pages node is selected. You can modify the pages listed under this Simplified Pages tab.

For example, the following standard objects have a set of simplified pages which you can modify:

  • Account

  • Activity

  • Asset

  • Contact

  • Customer Contact Profile

  • Forecast Territory Details

  • Household

  • Lead

  • Note

  • Opportunity

  • Partner

  • Program Enrollments

  • Relationship

  • Resource

  • Sales Campaign

  • Sales Lead

Modify Content

Use either Application Composer or Page Composer to modify a set of simplified pages, if they are extensible.

Use Application Composer to:

  • Hide or show custom fields

    Tip: When creating custom fields, set a maximum width of 15-20 characters for optimum display on Oracle Sales Cloud simplified pages.
  • Hide or show standard fields

  • Extend form regions

  • Extend table regions

  • Reorder fields (tables and pages)

  • Change field labels

  • Add subtabs

Use Page Composer to:

  • Make application changes that are role-based

  • Hide or show fields

  • Change field labels

  • Reorder subtabs

Modifying Simplified Pages Using Application Composer

To modify simplified pages using Application Composer:

  1. On the main Overview page in Application Composer, select an object that offers a set of simplified pages, such as Opportunity in the object tree.

  2. Select the Pages node.

  3. Select the Simplified Pages tab.

  4. Use the links on the tab to navigate to the object's configuration pages, where you can modify the simplified pages that are available for the selected object.

    For example, show or hide fields, rearrange fields, and add custom fields.

    Tip: Changes that you make to a simplified page aren't automatically replicated on the object's corresponding desktop page.

You can also modify simplified pages using Page Composer. Refer to the Page Composer chapter in this guide to learn more.

Modifying Simplified Pages Using Page Composer: Procedure

On a simplified page, you can modify user interface (UI) components by updating their properties, for example to change field labels, hide the component, or make a check box required.

When you start modifying simplified pages, by default, you can use the Design view. In the Design view, you can add content and make layout changes only in some pages. For other pages, you must use the Source view to make such changes.

Note: Any changes you make apply:
  • Only to the page you're on.

  • To all or specific groups of users, depending on the customization layer you select before making changes.

Prerequisites

Activate a sandbox.

Modifying a UI Component

To update component properties:

  1. Click your user image or name in the global header and select Customize Pages.

  2. Select a customization layer, for example to make changes only for users with a specific job role.

    Note: When you modify a UI component for a specific job role, that job role must be assigned to you for you to test the application change in the sandbox. Your security administrator can either assign the job role to you directly, or make the job role self-requestable for you to add it yourself from the resource directory.
  3. By default, you start in the Design view, which lets you navigate to the component you want to modify.

    You can tell you're in this view when the Design button on top of the page is highlighted. To use the Source view, you must select Source from the View menu. This menu isn't displayed by default. To display the View menu, and then select Source, set the Source View for Page Composer Enabled profile option (FND_PAGE_COMPOSER_SOURCE_VIEW) to Yes.

  4. When you have found your UI component, click the Select button on top of the page.

  5. Hover over the UI component until a border appears around the component, and click.

  6. Select Edit Component.

  7. Update the component's properties to make the application change you want.

    Each component has its own set of properties, which may include some of the properties in this table. In Design view, you get the main properties only; but in Source view, you get all properties.

    Property Description

    Description

    Text used by screen readers, for information in addition to what is provided in the Short Desc property.

    Label

    Display text for the component, for example the field prompt or the single prompt for a group of check boxes.

    Read only

    Whether users can edit the component, for example if a check box can be selected or not.

    Rendered

    Whether the component is visible or hidden to users on the page.

    Required

    Whether users must enter something for the component before saving the page.

    Short Desc

    Text that appears when users hover or focus on the component, for example hover over a field label or click in the text box.

    Show Component

    Whether the component is visible or hidden to users.

    Show Required

    Whether an asterisk is displayed to indicate that the component is required.

  8. To modify more components, click Add Content to return to the Design mode and repeat steps 4 to 7.

  9. Click Close to save.

    If available, click Save and Label instead to also label your changes so that you can later revert to the application changes you're saving. Labels are saved with a prefix of composer_. For example, if you enter myLabel, then the label is composer_myLabel.

Creating a Set of Simplified Pages for Custom Objects: Explained

When you create a custom object, you can optionally create a set of simplified pages with a click of a button. When you click that button, Application Composer automatically creates default custom layouts for the object's landing page (list page), creation page, and details page (edit page). A default custom layout for the search and select dialog is also created. Working with these page layouts is exactly the same as working with the page layouts for standard objects.

Creating Simplified Pages for Custom Objects

To create a set of simplified pages for a custom object:

  1. Ensure that you're working in an active sandbox.

  2. In Application Composer, navigate to the object that you want to create page layouts for.

  3. Expand the object in the object tree, and select the Pages node.

  4. Select the Simplified Pages tab.

  5. Click the Create Default Pages button.

    This is a screenshot of the Create Default Pages
button, which you click to create a set of simplified pages for a
custom object.

    Application Composer automatically creates a set of simplified pages for the custom object:

    • A default custom layout for the landing page

    • A default custom layout for the creation page

    • A default custom layout for the details page

    • A default custom layout for the search and select dialog, also known as a picker

  6. Working with the default custom layouts created for custom objects is the same as working with the standard layouts for standard objects.

    See Working With Page Layouts: Explained.

Selecting the Display Icon for Custom Objects

The simplified pages for objects are associated with a display icon. Application Composer creates custom objects with a default icon, but you can change it. The icon you select will display to your end users in a variety of locations, such as on the Navigator, subtabs, mobile pages, and the springboard strip on simplified pages.

Select the display icon for objects on the object's Overview page. See: "Defining Objects" for instructions.

This is a screenshot of the Object Overview page,
where you can select the display icon for the object.

Viewing Custom Object Simplified Pages at Run Time

After configuring the simplified pages for your custom object, you can test the run time pages by clicking the Home icon. Depending on which application you created your custom object in, you might have to wait a few minutes for the new display icon to appear on the Home page.

Tip: Navigate quickly and easily between Oracle Sales Cloud run time pages and Application Composer design time pages using the Favorites and Recent Items menu.

Configuring a Search and Select Dialog Box: Explained

Read this topic to learn about how to configure custom object Search and Select dialog boxes that users launch from simplified pages. A Search and Select dialog box, also known as a picker, lets your end users search for and select object records when assigning one record to another, such as a salesperson to an account or a solution to a service request. Search and Select dialog boxes are automatically provided for standard objects, and they're not extensible. However, you must configure the Search and Select dialog boxes for the custom objects you create.

Search and Select Dialog Boxes

A Search and Select dialog lets your end users search for and select object records at runtime. For example, your users might need to assign solutions to service requests, but what if your company's knowledge base includes over 1,000 solutions? Your users don't want to scroll down a list of 1,000 solution records. In such cases, the Search and Select dialog box lets users provide search criteria in advance (for example, all solutions relating to a particular product) to more easily find what they're looking for.

You can launch Search and Select dialog boxes from two areas:

  • From a dynamic choice list field, commonly referred to as a list of values.

  • From a subtab.

Configuring a Search and Select Dialog Box for Custom Objects

When you create a set of simplified pages for a custom object, Application Composer automatically creates a Search and Select dialog box, which you must then configure. Custom objects don't have Search and Select dialog boxes until you create and configure them. When you create the dialog boxes, they are reused wherever you want to associate that custom object with any other object.

Note: Standard objects already have their own Search and Select dialog boxes, which are not extensible.

To configure a Search and Select dialog box for a custom object:

  1. On the Simplified Pages tab for a custom object, click Create Default Pages if you haven't yet created the set of simplified pages for a custom object.

    See "Creating a Set of Simplified Pages for Custom Objects: Explained."

  2. On the Simplified Pages tab for the object, navigate to the Reusable Regions region, and edit the Default custom layout. You could also duplicate the Default custom layout to create and edit a new custom layout.

  3. On the Edit Search and Select Dialog Layout page, configure both the search and table regions of the Search and Select dialog.

Using Custom Object Search and Select Dialog Boxes: Examples

After you create and configure a Search and Select dialog for a custom object, you will then automatically use that dialog whenever you want your users to associate that custom object with any other object. Let's look at some examples.

For example, maybe your users want to assign a solution to a service request. In this case, they will assign a solution to a service request using a dynamic choice list field.

  1. Create a custom object for the Solution.

    1. Create the set of default simplified pages for the object.

    2. Configure a Search and Select dialog box for the Solution object.

  2. Create a custom object for the Service Request object.

    1. Create a dynamic choice list field, Solution, that is populated with records from the Solution object.

      This field will automatically use the Search and Select dialog that you configured in step 1.a.

      When you create the dynamic choice list field, Application Composer creates a one-to-many relationship between the Solution and Service Request objects. In other words, one solution can be associated with multiple service requests, but a service request can have only one solution.

    2. Add the new Solution field to the Create Service Request and Edit Service Request pages.

At runtime, your users will use the Solution's Search and Select dialog box, available from the Solution dynamic choice list field, to search for and select a solution to assign to a service request record.

Tip: You could optionally add a Service Requests related object subtab to the Edit Solution page, if you want users to view all service requests associated with a solution. To do this task, however, you must create a Search and Select dialog for the Service Request object.

In this next example, let's assign solution records to the company employee who authored the solutions. To accomplish this, you would use the same Search and Select dialog box that you configured for the Solution object on a subtab.

  1. Create a one-to-many relationship between the Resource and Solution objects, using the Relationships page, available under the Common Setup pane in Application Composer.

    In this case, one resource can author multiple solutions, but a solution can have only one author.

  2. On the Edit Resource page, create a related object subtab called Solutions that is populated with records from the Solution object.

At runtime, your users can search for and select one or more solutions to assign to a resource. They can also create a new solution record to assign to the resource, right from the Search and Select: Solutions dialog.

Working with Dynamic Page Layouts

Dynamic Page Layouts: Explained

Using Application Composer, you can present the same Sales Cloud page to your users, but display different page layouts depending on the conditions you define. For example, a sales executive might see certain privileged fields on an opportunity record, which other sales team members can't see. Similarly, an open opportunity might have certain fields related to it being in progress, which won't display on a closed opportunity.

Read this topic to learn about using dynamic page layouts:

  • Where can you use dynamic page layouts?

  • Examples of dynamically controlling the display of page layouts, based on:

    • Role/privileges of the user

    • Groovy expression

    • Type of record

To learn how to create page layouts, see "Working With Page Layouts: Explained."

Where Can You Use Dynamic Page Layouts?

The page layouts you create are restricted to simplified pages only. Page layouts are not available for desktop pages.

You can create page layouts for these types of simplified pages:

  • Landing page (list page)

  • Creation page

  • Details page (edit page)

  • Search and select dialog

Create page layouts for certain standard objects, such as the following objects:

  • Account

  • Activity

  • Contact

  • Forecast Territory Details

  • Household

  • Note

  • Opportunity

  • Partner

  • Relationship

  • Sales Campaign

  • Sales Lead

For a complete list of the standard objects that have simplified pages, see "Modifying Oracle Sales Cloud Simplified Pages: Explained."

You can also create page layouts for custom objects.

Controlling When Page Layouts Are Displayed

When you create a page layout, you set one or more conditions to control when that layout will be displayed.

The conditions you can attach to a layout include:

  • Type of record

    Not supported for landing page (list page) custom layouts.

  • Role

  • Advanced expression

    Not supported for landing page (list page) custom layouts.

The record type and role conditions are convenient, declarative ways of attaching conditions to a layout. Supply an expression to control the display of a layout, only if the record type and role conditions don't meet your needs.

Examples of layout conditions include:

  • Type of record

    • Display a qualification subtab with a questionnaire, when an opportunity is in the Qualification sales stage. But, display a close plan subtab with a checklist capturing critical data, when an opportunity is in the Close sales stage.

    • Only display the Closed Reason field on an opportunity, when the opportunity is closed.

    • Large organizations have multiple divisions, and each division might have different business process requirements. For example, Division 1 allows sales representatives to create orders from an opportunity, while Division 2 does not allow this.

    • Display different page layouts depending on the product category. For example, display different fields if the product category is a physical item, or if it's a service pack.

    • Display different page layouts depending on type of activity, such as a telephone call, task, or appointment.

  • Role

    • A sales manager might see fields related to approving an opportunity, whereas the sales representative would not see those fields.

    • A channel manager typically needs to see a different opportunity layout from a sales representative. For example, the channel manager might see a region on a page with fields related to the partner, program, and partner registration.

    • Some opportunity fields might apply only to field sales representatives, some fields to inside sales representatives, and some fields to follow-up sales representatives.

  • Expression

    • Do not allow users to add a revenue item or a product to an opportunity, after a quote has been generated and approved, or while an opportunity is in approval.

    • Control the display of page layouts based on the user's location, language, or device.

    • Control the display of page layouts based on the values of other choice list fields, not just the Record Type field.

    • Write an expression to combine multiple conditions.

Field Groups: Explained

A page layout is a page design that you create by selecting which fields to display on a page. When you design a page layout, you can use field groups to organize your pages and make them look more readable. A field group lets you group fields into collapsible regions, each with its own header that you can modify.

Which Fields Are You Grouping?

The fields that you can select for a field group are attributes of the top-level object that you're creating the page layout for, such as the opportunity object.

Why Use Field Groups?

Field groups are useful for managing your page layouts:

  • Group related fields so they always appear together on a page.

    Perhaps you want a group of fields, such as Home Ownership and Purchase Date of Home, to always appear together. Create a field group and add those two fields to the group.

  • Group secondary fields in a region that your end users can optionally expand, if they need to.

    Maybe some fields on a page are useful, but not critical for your end users. Define the field group so that the region is always collapsed by default at run time.

  • Manage page layouts with fewer clicks.

    Once you add a group of fields into a field group, you can easily move that group of fields up or down the page layout, with a single click.

    Multiple field groups always appear together at run time within a larger field group "container". When designing a page layout, you can move a field group up or down, but only within this larger container.

    In most cases, field groups appear at run time as regions right below the page's top summary region.

Field Group Validation

Application Composer validates the contents of field groups: once you add a field to a group, you can't add the same field to another group. This validation applies only across the field groups created for one page type (creation page or details page).

Tip: Although you can't add the same field to multiple field groups, you can easily move a field between groups. This makes it easy to manage fields within groups, if you later change your mind about field placement.

Creating a Field Group

You create field groups as part of either a creation page layout, or a details page layout.

To learn how to create field groups, see Working With Page Layouts: Explained.

Working With Page Layouts: Explained

A page layout is a design of a page which you create, and then attach conditions to. Using conditions, you can present the same Sales Cloud page differently to various users. For example, a sales manager can see one version of the page, while the sales representative sees another version. Page layouts are available only for simplified pages.

Read this topic to learn how to create page layouts. This topic explains how to:

  • Work with page layouts for standard objects

  • Create a set of page layouts for custom objects

  • Understand the difference between standard vs. custom layouts

  • Duplicate and edit page layouts

  • Add field groups

  • Add conditions

Working with Page Layouts for Standard Objects

Standard objects that have simplified pages are delivered with default page layouts, called standard layouts. Standard layouts are the pristine model layouts that you can't edit. However, you can duplicate the standard layout to create a new custom layout. You can edit custom layouts and add display conditions to them. When a custom layout is no longer of use, you can inactivate, or deprecate, that layout.

You can:

  • Duplicate page layouts

    To create a new page layout, duplicate an existing layout and then make your edits.

    All supported objects are delivered with a standard layout for their simplified user interface pages. Duplicate the standard layout to create custom layouts, which you can edit.

    The first custom layout for a page type is automatically named the default custom layout, but you can change the name.

  • Edit custom layouts

    You can edit only custom layouts. Custom layouts are duplicated from an existing layout.

  • Inactivate, or deprecate, custom layouts

    You can't delete page layouts, but you can inactivate custom layouts by deselecting the Active check box for a page layout on the Simplified Pages tab.

    You can't inactivate the standard layouts that are automatically delivered for an object.

Working with Page Layouts for Custom Objects

Working with page layouts for custom objects is exactly the same as working with page layouts for standard objects. The only difference is that after you create a custom object, you must manually create its set of custom layouts before you can start to work with them. Custom objects do not have a set of standard layouts.

Create a set of simplified page layouts for a custom object with a click of a button. Clicking that button tells Application Composer to automatically create the following:

  • Page layouts for the object's set of user interface pages, such as the creation and details pages.

    To learn how to create a set of simplified pages for a custom object, see Creating a Set of Simplified Pages for Custom Objects: Explained.

  • A Search and Select dialog, which you can configure by clicking the Edit Picker link.

    To learn how to configure the Search and Select dialog for custom objects, see Configuring a Search and Select Dialog: Explained.

Standard vs. Custom Layouts

Standard layouts are the pristine model layouts that you can't edit. Custom layouts are copies of standard layouts that you make, which you can edit.

Standard layouts exist to make your upgrades seamless. When you upgrade to a new release of Oracle Sales Cloud, Oracle upgrades only the standard layouts for each object. Your custom layouts aren't touched. This makes it easy for your users to continue working immediately after an upgrade. In the meantime, you can take your time to review the changes that happened to standard layouts as part of an upgrade, and manually incorporate those changes as and when needed.

After an upgrade, you can easily review the newly upgraded standard layouts by deactivating all existing custom layouts for a page type, such as the creation page. Then, log in as a user to view the standard layout at run time. Observe the changes for the creation page and, if desired, navigate back to Application Composer to incorporate those changes into your creation page custom layouts and reactivate them.

If an object has one or more custom layouts for some page types, but not for others, then Oracle considers the whole set of pages for that object to be modified. As part of the upgrade, Oracle:

  1. Doesn't touch the custom layouts that already exist, as usual.

  2. Creates custom layouts for those pages that don't have any custom layouts. These new custom layouts preserve what users experienced before the upgrade.

  3. Upgrades all standard layouts, as usual.

Since standard layouts are model layouts that you can't edit, this means that you can't make changes to the page using Page Composer if the standard layout displays at run time. However, customers can still personalize the page.

Editing Page Layouts

When you edit a custom layout, you can interact with items inside regions, or interact with the regions themselves. You can:

  • Add fields, actions, links, buttons, and subtabs.

  • Hide and show, reorder, and relabel regions, including subtabs.

To edit a custom layout:

  1. In Application Composer, navigate to the object that you want to create custom layouts for.

  2. Expand the object in the object tree, and select the Pages node.

  3. Select the Simplified Pages tab.

  4. Find the type of page that you want to modify, such as a creation page layout or a details page layout. Click the Duplicate Layout icon to duplicate and edit an existing layout.

  5. Next, design the page layout. Depending on how the page is designed, you can add fields, actions, links, and buttons.

    You can also hide and show, reorder, and relabel regions.

    If the page layout is for a details page, then you can also add and reorder subtabs, and add the Attachments field.

    This is a screen shot of the page where you can
edit a creation page layout for an object.

Adding Field Groups to a Page Layout

When selecting the fields to include in a page layout, you can select the fields one by one, or add multiple fields as a single unit, called a field group.

To create a field group:

  1. When editing a custom layout, click the New icon in the Field Groups region.

    This is a screenshot of the page where you can
edit a creation page layout for an object.
  2. On the Create Field Group: Configure Field Group Details page:

    1. Enter the name of the field group. At run time, the name is displayed as the name of this collapsible region.

    2. Indicate if the region is automatically expanded, or collapsed by default.

    3. You can also set the position of the field group in relation to other field groups, if other field groups already exist.

    4. Click Next.

    This is a screenshot of the Create Field Group
page.
  3. Next, add fields to the group.

    Tip: You can multi-select and double click fields in the Available Fields list to move them to the Selected Fields list.
    This is a screenshot of the Create Field Group
page, where you add fields to the field group.
  4. If additional custom layouts exist, then you can click Next to add this field group to other custom layouts.

    For example, in the screenshot above, we are creating a field group as part of a layout for a creation page. But, you could also add this field group to the Sales Manager layout, if it existed.

  5. Click Save. Your new field group now appears in the Field Groups region.

    This is a screenshot of a page layout for a creation
page, with two field groups defined.
  6. Once your field groups are defined, you can optionally hide field groups, or reorder field groups within the larger field groups "container" on the custom layout.

    This is a screenshot of the icon you click to reorder
field groups on the page.
  7. You can also move fields between groups, since a field can appear within only one field group for a particular custom layout.

    This is a screenshot of the icon you click to move
a field between field groups on the page.
  8. When you are finished making changes to your custom layout, click Done.

Assigning Conditions to Page Layouts

After you edit the custom layout, you can assign one or more conditions that control when the layout is displayed. You assign conditions to custom layouts when viewing them on the Simplified Pages tab. You can't assign conditions to the standard layout.

This is a snapshot of the Creation Page Layouts
region, which shows multiple page layouts in the table.
Note: The layouts you create are displayed in a table, and the order of layouts in each table is significant. At run time, Application Composer evaluates the condition or conditions specified in each layout, starting with the first layout listed in the table. The first layout that matches all Type, Role, and Expression conditions is selected for display at run time. The standard layout is always the last layout in the table, and it can't be deleted or inactivated.

Assign one or more of these conditions to a custom layout.

  • Type

    1. Select the custom layout you want to add conditions to.

    2. Select a record type field value, if a record type field has been created for the object. At run time, if the value is selected, then this custom layout displays.

      The default value for this condition is ANY, so if you do not specify a Type condition for a layout, then Application Composer views this condition as satisfied when evaluating a layout for display at run time.

    You can't assign this condition to landing page (list page) custom layouts.

  • Role

    1. Select the custom layout you want to add conditions to.

    2. Select the role; this is the audience that can view this page layout. For example, perhaps only the sales representative can see this custom layout at run time. Custom roles, which are copies of the predefined roles that Oracle provides for all customers, are displayed by default for you to select. However, you can optionally choose to display predefined roles, as well.

      The default value for this condition is ANY, so if you do not specify a Role condition for a layout, then Application Composer views this condition as satisfied when evaluating a layout for display at run time.

  • Advanced Expression

    1. Select the custom layout you want to add conditions to.

    2. Click the Calculator icon.

    3. Enter a Groovy expression that controls when this custom layout is displayed.

    You can't assign this condition to landing page (list page) custom layouts.

Tip: In general, it's best to keep a single custom layout, for each page type, condition-free. This way, if no conditions apply at run time, then at least your users see a generic custom layout. Otherwise, if no conditions apply at run time, then the standard layout displays.

Controlling the Display of a Page Based on a Field Value: Explained

Using Application Composer, you can optionally present a different page layout to your users, depending on the conditions you define. One condition that you can set for a layout is based on the type of record, which your end users indicate by selecting a value from a field at run time. For example, if an opportunity is open, then certain fields might display. However, if the opportunity is closed, then other fields might display. Controlling the display of page layouts in this manner requires a special kind of choice list field, called a record type field.

Controlling the Display of a Page Layout

To control the display of page layouts based on a choice list value, you must:

  1. Create a record type field for an object.

  2. Add the field to the desired simplified page where you want the field to appear, such as the object's creation page or details page (edit page).

  3. Assign each choice list value to a layout.

    Landing page (list page) custom layouts do not support record type conditions.

At run time, when an end user selects a value from the field, the page display changes to match the simplified page layout that you associated with the field value.

Creating a Record Type Field

A record type field is a choice list field with a list of values that you specify.

Note: You can create only one record type field per object.

To create a record type field:

  1. In Application Composer, navigate to the object that you want to create page layouts for.

  2. Select the object itself to further expand the tree hierarchy.

  3. Select the Fields node to navigate to the Fields page.

  4. On the Fields page, click the Create a custom field icon on the Custom tab.

  5. Select Record Type and click OK.

  6. Enter basic field attributes, such as the field display name and whether or not the field is required and updatable.

  7. Configure the list of values to display in the choice list. You can either select a predefined lookup type, or create a new one.

  8. Configure which roles have which access to particular choice list values. In other words, you can restrict the list of values displayed at run time by role.

    This screenshot illustrates how you can control
which record type field values display at run time, to each role.

    For example, perhaps the sales representative can see only selected choice list values, but the sales manager can see all the choice list values.

    Custom roles, which are copies of the predefined roles that Oracle provides for all customers, are displayed by default. However, you can optionally choose to display predefined roles, as well.

Next, add the field to the desired simplified page layout, where you want the field to appear. This step is described in the next section.

Creating Page Layouts per Record Type

After creating the record type field, you must then add the field to the desired set of simplified pages, and then assign the choice list values to one or more page layouts. In this way, you control which layout displays at run time, depending on the choice list field value selected. You can't assign this condition to landing page (list page) custom layouts.

To create a page layout for a record type:

  1. In Application Composer, navigate to the object that you want to create page layouts for.

  2. Expand the object in the object tree, and select the Pages node.

  3. Select the Simplified Pages tab.

  4. Find the type of page layout that you want to create for a record type. For example, maybe you want to create a page layout for display if an opportunity is open. In the Details Page Layouts region, select the standard layout and click the Duplicate Layout icon. Once you have a custom layout, you can make changes to it. You can't add a record type condition to landing page (list page) custom layouts.

    Note: The first custom layout that you create from a standard layout is called the default custom layout, but you can optionally change the name. Oracle recommends that you do not add conditions to the default custom layout. You can add record type conditions, and all other conditions, to subsequent custom layouts that you create.
  5. Add the record type field to the selected layout.

  6. After editing and saving the layout, select a choice list value under the Type column.

    This is a snapshot of the Available Record Types
window, where you can assign record type values to a page layout.

    At run time, if an end user selects this value, then this layout displays.

    Caution: Remember that during the creation of the record type field, you can also restrict the list of values by role. If you assign a Role condition to the layout as well, then confirm that both Role conditions are complementary.

Examples of Page Layouts per Record Type

Examples of page layouts that you might want to create for a record type field and its values are:

  • Display a qualification subtab with a questionnaire, when an opportunity is in the Qualification sales stage. But, display a close plan subtab with a checklist capturing critical data, when an opportunity is in the Close sales stage.

  • Only display the Closed Reason field on an opportunity, when the opportunity is closed.

  • Large organizations have multiple divisions, and each division might have different business process requirements. For example, Division 1 allows sales representatives to create orders from an opportunity, while Division 2 does not allow this.

  • Display different page layouts depending on the product category. For example, display different fields if the product category is a physical item, or if it's a service pack.

  • Display different page layouts depending on type of activity, such as a telephone call, task, or appointment.

Controlling the Display of a Page Based on a User's Role: Explained

Using Application Composer, you can optionally present a different page layout to your users, depending on the conditions you define. One condition that you can set for a layout is based on the role of your end users. For example, a sales representative might see one particular layout, while the sales manager might see a different layout.

Creating Page Layouts per Role

Assign a role to one or more page layouts. In this way, you control which layout displays at run time, depending on the role of the user.

To create a page layout for a role:

  1. In Application Composer, navigate to the object that you want to create page layouts for.

  2. Expand the object in the object tree, and select the Pages node.

  3. Select the Simplified Pages tab.

  4. Find the type of page layout that you want to create for a role. For example, maybe you want to create a page layout for the sales manager. In the Creation Page Layouts region, select the standard layout and click the Duplicate Layout icon. Once you have a custom layout, you can make changes to it.

    The first custom layout that you create from a standard layout is called the default custom layout, but you can optionally change the name. Oracle recommends that you do not add conditions to the default custom layout. You can add role conditions, and all other conditions, to subsequent custom layouts that you create.

  5. After editing and saving the custom layout, select a role under the Role column.

    Custom roles, which are copies of the predefined roles that Oracle provides for all customers, are displayed by default. However, you can optionally choose to display predefined roles, as well.

    Ideally, your roles should be stable before you assign roles to page layouts. If you make changes to roles after you create role-specific page layouts, then you will have to come back to these page layouts and update the assigned roles.

    This is a snapshot of the Select: Roles window,
where you can assign roles to page layouts.

    At run time, if the user has the specified role, then this page layout displays.

    Caution: If you assign a Type condition to the layout in addition to a Role condition, then confirm that the Role condition is complementary with any role assignments made at the record type field level.

Examples of Page Layouts per Role

Examples of page layouts that you might want to create for specific enterprise duty roles are:

  • A sales manager might see fields related to approving an opportunity, whereas the sales representative would not see those fields.

  • A channel manager typically needs to see a different opportunity layout from a sales representative. For example, the channel manager might see a region on a page with fields related to the partner, program, and partner registration.

  • Some opportunity fields might apply only to field sales representatives, some fields to inside sales representatives, and some fields to follow-up sales representatives.

Controlling the Display of a Page Based on an Advanced Expression: Explained

Using Application Composer, you can optionally present a different page layout to your users, depending on the conditions you define. One condition that you can set for a layout is based on an expression you write using a Groovy script. For example, you might want to prevent users from updating a particular field based on the value of an opportunity. You write Groovy scripts using Application Composer's expression builder.

Writing Expressions for Displaying Page Layouts

Write an expression for one or more page layouts. In this way, you control which layout displays at run time, depending on the expression. You can't assign this condition to landing page (list page) custom layouts.

Tip: You can also control the display of pages using choice list values (using a record type field) and roles. The record type and role conditions are convenient, declarative ways of attaching conditions to a layout. Thus, supply an expression to control the display of a layout, only if the record type and role conditions don't meet your needs.

To write an expression for a page layout:

  1. In Application Composer, navigate to the object that you want to create page layouts for.

  2. Expand the object in the object tree, and select the Pages node.

  3. Select the Simplified Pages tab.

  4. Find the type of page layout that you want to create. For example, maybe you want to write an expression that controls the display of a creation page. In the Creation Page Layouts region, select the standard layout and click the Duplicate Layout icon. Once you have a custom layout, you can make changes to it. You can't add an expression condition to landing page (list page) custom layouts.

    Note: The first custom layout that you create from a standard layout is called the default custom layout, but you can optionally change the name. Oracle recommends that you do not add conditions to the default custom layout. You can add an expression, and all other conditions, to subsequent custom layouts that you create.
  5. After editing and saving the layout, under the Advanced Expression column, access the expression builder by clicking the calculator icon. Write an expression that describes the conditions required for this layout to display at run time.

    This is a snapshot of the Creation Page Layouts
region, where you can access the expression builder to write an expression
for a page layout.
    • If your script references one or more fields, then select those fields in the Depends On choice list, too. If those field values change at run time, then the expression is reevaluated and the page layout is refreshed if the new condition is met.

      This is a snapshot of the expression builder, where
you can write an expression for a page layout.

      For example, let's say you write this script:

      PartyName == 'abc' || NoteTypeCode == 'GENERAL'

      Your script references two fields. Thus, you must select those fields, Author and Type, in the Depends On choice list, which appears at the top of the expression builder.

      Note that long text fields don't work like other fields. If your script references a long text field, such as Note Text, then you must use the toString() operator in your script. For example:

      If(NoteTxt?.toString() == 'abc')

      Remember to select the Note Text field in the Depends On choice list, too.

    • Your expression should return either a True or False value. At run time, Application Composer interprets a True value to mean that the condition was met.

      For example, let's say you want to display a specific page layout if the Win Probability for an opportunity is 95. In this case, your script could be:

      if (WinProb==95)
      {
      return true;
      }
      else
      {
      return false
      }

Examples of Page Layouts That Display Based on Expressions

Examples of page layouts that display based on expressions include:

  • Do not allow users to add a revenue item or a product to an opportunity, after a quote has been generated and approved, or while an opportunity is in approval.

  • Control the display of page layouts based on the user's location, language, or device.

  • Control the display of page layouts based on the values of other choice list fields, not just the Record Type field.

  • Write an expression to combine multiple conditions.

Configuring the Summary Table on a Landing Page: Worked Example

When you configure an object's landing page, you indicate the overall set of columns that are available for display in the summary table. You can indicate which columns should display by default, and which columns should be available for end users to manually display themselves as part of their own saved searches. After you configure the landing page, optionally assign a role condition to the page layout so that you can display a different set of columns on the page per role. For example, you may want your salespeople to see different landing page information than your partner managers.

At runtime, your end users can optionally create their own saved searches on the landing page summary table, choosing from the set of columns that you selected.

The following example shows you how to configure the summary table on a landing page.

Configuring the Summary Table

  1. In Application Composer, navigate to the object whose landing page you want to configure.

  2. Expand the object in the object tree, and select the Pages node. Confirm that you are on the Simplified Pages tab.

  3. In the Landing Page Layouts region, select the standard layout and click the Duplicate icon. Once you have a custom layout, you can make changes to it. Or, edit an existing custom layout.

  4. Navigate to the summary table region and click the Edit icon. Some standard objects might refer to the summary table as the overview table.

  5. In the Configure Summary Table region, indicate which fields should display as columns in the landing page's summary table.

  6. For each field that you select, the Display in Summary Table check box is automatically selected, but you can deselect it.

    Deselecting the check box means that the column will not automatically display on the landing page at runtime. However, your end users can manually display that column when they create a saved search at runtime.

  7. Click Save and Close.

  8. After editing and saving the custom landing page layout, optionally select a role under the Role column to specify which users should see this landing page at runtime.

  9. If you assigned a role condition, then sign in as that role and test your changes.

    Note: You must have the appropriate job role assigned to you to see the changes.

Enabling or Disabling Drill Down Fields: Explained

This topic covers how you enable or disable drill down fields on simplified pages. These drill down fields enable you to edit an object from the details page of another object.

You must familiarize yourself with the following topics before you configure drill downs:

  • Extending Simplified Pages: Overview

  • Object Relationships: Explained

  • Dynamic Choice Lists: Explained

  • Subtabs: Explained

Overview

The ability to drill down on a field is based on relationships that exist among the objects involved. These relationships could be either implicitly defined through a dynamic choice list type fields or joins, or explicitly defined by creating a relationship using Application Composer.

Note: You can create drill down fields for custom objects, and for standard objects whose task flow has been registered for extensibility. You cannot drill down to a common component or custom object.

You can configure drill down for the following:

  • Details and Summary Pages

  • Child or related object subtab and Context link subtab

Use Application Composer to add drill down fields to the desired pages using the Simplified Pages tab, and then view these pages on your laptop or tablet.

You can also drill down from one edit page to another in a hierarchical manner. For example, drill down from Leads page to an Edit Opportunity page, and then from the Edit Opportunity Page to Edit Primary Contact page.

Adding Drill Down Fields to Pages

This section covers how you add drill down fields to pages. For information on how you create pages, see related topic Defining Pages: Explained.

When configuring a details page, as you move the fields from the Available Fields box to the Selected Fields box, the fields related to the object for which you are modifying the page appear in a table on the right. In the table, the drill down is enabled by default for related fields.

Note: The table appears only if the selected fields are related.

This figure illustrates the table (on the right) using which you enable or disable drill down fields.

This figure illustrates the table using which you
enable or disable drill down fields

You can enable or disable drill downs using the Drill Down Enabled check box in the table. The check box is selected and grayed out for standard fields of type dynamic choice lists that are delivered by default.

For work area pages, you also specify the Drill Down Column. This column lists the field values as links.

Adding Drill Down Fields to Subtabs

This section covers how you add drill down fields on subtabs. For information on creating subtabs, see related topic Subtabs: Explained.

You can add drill down fields to the following types of subtabs:

  • Child or related object subtab

    When creating a Child or related object subtab, in the Drill Down Field list, specify the field whose values should appear as drill down links in a column on the subtab.

    This figure illustrates where you select and specify the drill down column and fields.

    This figure shows the page where you select and
specify the drill down column and fields

    The Selected Fields table (on the right) displays the fields available for drill down. Specify the fields that you want to display as drill down links on the subtab.

  • Context link subtab

    When creating a Context link subtab, in the Drill Down Field list, specify the field whose values should appear as links in a column on the subtab.

    This figure shows the page where you select and specify the drill down column and fields.

    This figure shows the page where you select and
specify the drill down column and fields

    You can also limit the fields you want to display on the subtab by specifying the filters under Search Criteria.

    For more information on using filters, see related topic Subtabs: Explained.

Specifying Drill-Down Fields for Custom Dynamic Choice List Fields: Example

This example shows how you specify drill-down fields for custom dynamic choice list fields in simplified pages.

Specifying Drill-Down Fields

To specify a drill-down field for a custom dynamic choice list field:

  1. Select a sandbox to work in and make it active.

  2. Navigate to Application Composer.

  3. Expand Standard Objects and click Sales Lead.

  4. Click the Actions and Links link.

  5. Click the Simplified Pages tab.

  6. Edit the desired custom layout in the Details Page Layouts region.

  7. Select the Summary tab, and click the edit icon.

  8. Select a dynamic choice list item from the Available Fields column.

    This figure shows the drill down status column for the selected dynamic choice list fields.

    Drill Down Column

    You have now specified the drill-down fields.

Creating and Adding Custom Action Links to Simplified Pages: Worked Example

This worked example illustrates how to create and add custom action links to simplified pages.

This example covers:

  1. Creating a custom link that launches Google homepage.

  2. Adding the custom link to the Leads page in the Simplified UI.

  3. Verifying that the link appears on the Simplified UI.

Creating a Custom Link

In this step, you are creating an action link called Test.

Note: You must have a sandbox active before you begin your tasks.
  1. Navigate to Application Composer.

  2. Expand Standard Objects, and then expand Sales Lead.

  3. Click Actions and Links.

  4. In the Sales Lead: Actions and Links page, select Actions > Create

  5. Enter or select the following:

    Field or Region Value

    Display Label field

    Enter Test.

    After you enter Test, the Name field Automatically displays Test.

    Type field

    Select Link.

    After you select Link, the Source field automatically shows the URL option selected, and displays it as disabled.

    URL Definition region

    Enter 'http://www.google.com' (along with single quotes)

    Note: In your script that builds the URL, do not use create, update, or delete statements that manipulate another object's data. Your script should only read data and then generate the URL.

    This figure shows the Create Action or Link page for the Sales Leads object.

    Create Action or Link Simplified page for Sales
Leads object

  6. In the script region, enter 'http://www.google.com'.

  7. Click the Validate icon. A success message appears.

    This figure shows the URL definition region and the validation message.

    URL definition region of the Edit Action or Link
page

  8. Click the Save button to save the new link.

    You must add this new link called Test to the Leads page.

Adding the Link to the Leads Page

In this step, you add the Test link to the Leads page:

  1. Expand Standard Objects, and then expand Sales Lead.

  2. Click Pages under Sales Lead.

  3. Select the Simplified Pages tab.

  4. In the Details Page Layouts region, duplicate the standard layout to create a new layout to edit, or edit another existing layout.

  5. In the Edit Simplified Details Page, select the vertical tab to which you want to add the custom link. In this example, select the Summary tab.

    This figure shows the Summary tab and the Edit icon.

    Edit Simplified Details page, Summary tab

  6. Click Edit icon in the Summary region. The Edit Lead page opens.

  7. In the Available Fields column, locate Test - Link field and move it to the Selected Fields column.

    This figure shows Test - Link on the Edit Leads page.

    Edit Lead Test - Link

  8. Click Save and Close.

Testing the Link in Simplified Pages

In this step, you verify the addition of the field.

To test whether the Test link you created appears in Simplified Pages:

  1. Open the Simplified Pages for Leads.

  2. Edit a lead and note the newly created Test link in the Edit Lead: <Name> Summary page.

    This figure shows the Test link.

    This figure shows the Test link

  3. Click the Test link. The Google homepage appears.

Working with Subtabs

Adding and Hiding Subtabs Using Application Composer: Explained

Every top-level Oracle Sales Cloud object (such as an opportunity, account, or contact) has an edit page, also known as a details page. The details page is where users go to view record details, and make changes. You can use Application Composer to modify the details page. For example, you can show and hide fields, and you can also show and hide subtabs. Subtabs are useful because they display details that are related to the current record but derived from another record, or even from another source outside Oracle Sales Cloud. For example, when editing a trouble ticket record, your users might want to view the list of products that are reported on the trouble ticket. You create that subtab using Application Composer. Read this topic to learn more about subtabs in the simplified set of pages.

What's a Subtab?

A subtab lets you display details that are related to the current object but derived from another object, or from another source outside the current Oracle Sales Cloud application altogether. You do this by adding subtabs to the details page, and specifying the source of subtab data. At run time, your users can click each subtab to review data that is related in some way to the current object's record.

A subtab displays data in a list. Users can click any record in the list to drill down to view more details about that record.

Note: When viewing a subtab on an iPad or other iOS device, advise your users to scroll to the right directly on the subtab data rows. Scrolling to the right on the subtab area outside the data rows is not supported by iOS devices.

Let's look at the subtabs that are available from the Edit Opportunity page. For example:

  • Contacts

    This subtab lists records from the Opportunity Contact object, which is a child of the Opportunity object. Your users would click this subtab to review contacts that are related to the current opportunity record.

    Tip: Child objects have a cascade delete relationship with parent objects. This means that if the parent record is deleted, then child records are also deleted.
  • Opportunity Team

    This subtab lists records from the Opportunity Team Member object, which is a child of the Opportunity object. Your users would click this subtab to review team members that are related to the current opportunity record.

  • Leads

    This subtab lists records from the Sales Lead object. This is a context link type of subtab, which displays data from any object. There is no cascade delete relationship between the Opportunity and Sales Lead objects. Your users would click this subtab to review leads that are related to the current opportunity record.

This is a screenshot of the Edit Opportunity page,
including the available subtabs.

Where Do Subtabs Appear?

Subtabs display on an object's details page. Every top-level Oracle Sales Cloud object has a details page, also known as the edit page, as part of its work area.

The details page is the page where users can view more details about an object. Depending on the security setup, users access the details page by clicking the Edit icon or by selecting the Edit menu item from the Actions menu on the summary table's toolbar. Users can also access the details page by clicking the object record name itself in the summary table.

The details page can also display information related to the object record in subtabs. For example, the details page for an opportunity could include a subtab that lists customer contacts or previous orders.

Standard objects in Oracle Sales Cloud are delivered with a details page that has a set number of subtabs. You can add more if required.

For the custom objects you create, you can add subtabs once you create the work area for the object.

Adding Subtabs

Let's say you want to add a new subtab to the Edit Opportunity page. In this example, let's show the customer's address. (For the sake of this example, let's assume that you previously created a custom field, Customer Address (CustomerAddress_c), on the Opportunity object to capture this information.)

Use this procedure to add a new subtab to the Edit Opportunity page.

  1. Navigate to Application Composer.

  2. Under the Objects navigation tree, expand Standard Objects, then expand the Opportunity object.

  3. Click the Pages node.

  4. Click the Simplified Pages tab.

  5. In the Details Page Layouts region, select a layout. You can select the standard layout and click the Duplicate Layout icon to duplicate it, or select another layout. Click the Edit icon.

  6. On the Edit Simplified Details Page, scroll down through the Subtabs Region and, at the end of the subtabs, click the Add icon.

    This is a screenshot of the region on the Edit
Simplified Details Page where you can add a subtab.

    You can add one of five types of subtabs:

    • Related object subtab

    • Child object subtab

    • Context link subtab

    • Notes subtab

    • Web content subtab

    These subtab types are described in "Subtab Types: Explained". Read that topic to learn how to add each specific type of subtab.

    In this example, select the option for Web content and click Next.

  7. In the Display Label field, enter Customer Map Location.

  8. Under URL Definition, click the Expand Show Palette button, if it's not already expanded.

  9. Enter this groovy script:

    def myfinalURL = "http://www.bing.com/maps/?v2&where1="
    def myURL1 = CustomerAddress_c != null ? CustomerAddress_c : ''
    myfinalURL += myURL1
    return(myfinalURL)
    
  10. (Simplified UI only) If more than one details page layout exists, then click Next to optionally select other details page layouts that will display this subtab.

  11. Click Save and Close, and then click Done.

  12. When you navigate to the Edit Opportunity page at run time, a new subtab, Customer Map Location, is now available.

    If your end users entered an address in the Customer Address field while editing an opportunity record, then the map Web site should appear on the subtab, displaying the location of the customer's address.

    This is a screenshot of a Web content subtab at
run time.

Hiding Subtabs

Let's say you want to hide the Appointments subtab on the Edit Opportunity page.

Use this procedure to hide subtabs.

  1. Return to the Edit Simplified Details Page page for the Opportunity object.

  2. Click the Configure Subtabs icon (green arrows).

  3. In the Configure Subtabs dialog, in the Selected Subtabs list, double-click the Appointments subtab.

    This is a screenshot of the Configure Subtabs dialog,
where you can hide and show subtabs.
  4. Click OK.

  5. Click Done.

  6. When you navigate to the Edit Opportunity page at run time, the Appointments subtab is no longer available.

Subtab Types: Explained

Subtabs display details that are related to the current record but derived from another object entirely, or even from another source outside Oracle Sales Cloud. Subtabs display on a top-level object's details page. The details pages for standard objects are delivered with a set number of subtabs, but you can add more if required. You can add subtabs to the details pages for custom objects. Using Application Composer, you can create five types of subtabs.

Read this topic to learn about the different types of subtabs that you can create:

  • Related object subtab

  • Child object subtab

  • Context link subtab

  • Notes subtab

  • Web content subtab

Related Object Subtabs

A related object subtab lists records from one object that is related to another object.

What does it mean when an object is related to another? A relationship is a foreign key association between two objects. Using Application Composer, you can create a one-to-many or many-to-many relationship between two objects. This is helpful because if a relationship exists, then you can expose the "many" object records on a subtab that is displayed on the "one" object's details page. This is useful for your users.

For example, your users might want to associate an account with a list of service requests that have been logged for that account. To enable this, you must first create a one-to-many relationship between the account and service request objects. (An account can have multiple service requests associated to it, and a given service request can have one and only one account associated with it.) Then, you can add the Service Requests subtab to the Account details page. At run time, when your users review a particular account record, they can see all the service requests that have been logged for that account. And, depending on how you configure the subtab, they can also create new service requests, add existing service requests, or remove service requests from the subtab.

For custom related object subtabs that you create, your users can create or edit records inline in each related object subtab. But, you can also configure the subtab so that your users can create or edit records in a full-sized dialog window, in addition to inline editing. This is more usable if there are a large number of fields for users to fill out. This setup is described as follows.

To add a related object subtab to an existing details page:

  1. Click the Create Subtab icon from either the Pages Overview page (for desktop pages) or from any details page layout (for simplified pages).

  2. Select Related object.

    This is a screen shot of the Create Subtab page,
where you configure a new subtab for a related object
  3. On the Create Subtab page:

    1. Select the related object that is to be exposed on the subtab, and enter the subtab display label.

      The list of related objects includes those objects that:

      • Are already related to the current object, with any type of one-to-many or many-to-many relationship, either custom or standard.

        For example, if you previously created a one-to-many reference relationship, then you will see the "many" object in the data object list when creating the subtab for the "one" object's details page.

      • Don't yet have a subtab.

      After the subtab is created, you won't be able to create a second subtab for that same "many" object again.

    2. (Simplified UI only) Specify the drill down column. The drill down column is the field that you want your end users to click to drill down to more details about the related object record.

      If you're creating a subtab for a custom object, then the Drill Down Column field might not appear if you haven't yet created the custom object's simplified UI pages. To display the Drill Down Column field, you must first create the simplified UI pages for the custom object, sign out, and then sign back in.

    3. Specify a display icon for the subtab.

    4. Select which fields and links you want to display on the subtab summary table at run time.

      When selecting the fields for display on a related object subtab, join fields are not available for selection if the relationship is a many-to-many relationship.

    5. Optionally hide the Create, Add, and Remove buttons that appear on the subtab at run time.

      In a related object subtab, your users can use these buttons at run time to:

      • Create a related object record and associate it to the current record at the same time.

        Note: This button is available only for subtabs in simplified pages.
      • Add an existing related object record to the current record.

      • Remove a related object record from the subtab. This removes the association between the related object record and the current record.

    6. (Simplified UI only) If more than one details page layout exists, then click Next to optionally select other details page layouts that will display this subtab.

    7. (Simplified UI only) If you want your users to create or edit new records in a full-sized dialog window, in addition to inline editing, then complete these additional steps. This is more usable if there are a large number of fields for users to fill out.

      1. On the details page layout where the related object subtab appears, click the subtab that you want to configure.

      2. Click the Edit pencil icon.

      3. Click the Enable Separate Create and Edit Pages check box.

      4. Click Save and Close.

      Once completed, your users can create related object records in a separate full-sized dialog window. To edit existing records, they can click the record name to drill into a full-sized edit page.

      Even after you enable this full-sized record creation and editing capability, your users can still opt to do their record creation and editing inline, if they choose to. Both options are now available to them.

      This feature is available for related object subtabs based on custom top-level objects that are the "many" object in a one-to-many relationship with a standard Oracle Sales Cloud object. This feature is also available for child object subtabs based on custom child objects.

    8. Click Save and Close.

Child Object Subtabs

A child object subtab lists records from a child object that are related to its parent.

A parent child relationship is a one-to-many relationship: one parent record can have many children records. When you create a child record, it's created specifically in the context of its parent. The child object's records are deleted if the parent object record is deleted. A child object doesn't have its own work area, and exists only as a subtab on the parent object's details page.

An example of a parent child relationship is the relationship between the Opportunity object, and its children, such as Opportunity Contact and Opportunity Partner. In this example, contacts and partners are created in the context of the parent opportunity record. At run time, when your users review a particular opportunity record, they can see all the contacts and partners that have been created for that opportunity. They can edit or add new contacts and partners directly inline, in each subtab.

For custom child object subtabs that you create, your users can create or edit records inline in each child object subtab. But, you can also configure the subtab so that your users can create or edit records in a full-sized dialog window, in addition to inline editing. This is more usable if there are a large number of fields for users to fill out. This setup is described below.

To add a child object subtab to an existing details page:

  1. Click the Create Subtab icon from either the Pages Overview page (for desktop pages) or from the details page layout (for simplified pages).

  2. Select Child object.

  3. On the Create Subtab page:

    1. Select the child object that is to be exposed on the subtab, and enter the subtab display label.

      The list of child objects includes those objects that:

      • Are already related to the current object in a parent child relationship.

      • Don't yet have a subtab.

        After the subtab is created, you won't be able to create a second subtab for that same child object again.

    2. Specify a display icon for the subtab.

    3. Select which fields and links you want to display on the subtab summary table at run time.

    4. Optionally hide the Create, Edit, and Remove actions on the subtab at run time.

      In a child object subtab, you can hide these actions, or keep them available. If you keep these check boxes selected, then your users can:

      • Create a child object record inline.

      • Edit an existing child object record inline.

      • Delete a child object record inline.

    5. (Simplified UI only) If more than one details page layout exists, then click Next to optionally select other details page layouts that will display this subtab.

    6. Click Save and Close.

    7. (Simplified UI only) If you want your users to create or edit new records in a full-sized dialog window, in addition to inline editing, then complete these additional steps. This is more usable if there are a large number of fields for users to fill out.

      1. On the details page layout where the child object subtab appears, click the subtab that you want to configure.

      2. Click the Edit pencil icon.

      3. Click the Enable Separate Create and Edit Pages check box.

        The Drill Down Column appears, but you can't change it. It's always the child object's record name.

      4. Click Save and Close.

      Once completed, your users can create child records in a separate full-sized dialog window. To edit existing child records, they can click the record name to drill into a full-sized edit page.

      Even after you enable this full-sized record creation and editing capability, your users can still opt to do their record creation and editing inline, if they choose to. Both options are now available to them.

      This feature is available for child object subtabs based on custom child objects. This feature is also available for related object subtabs based on custom top-level objects that are the "many" object in a one-to-many relationship with a standard Oracle Sales Cloud object.

Context Link Subtabs

A context link subtab displays a filtered list of records from any top-level object, where the filter is often based on the run time values from the current object. The object does not have to be related to the current object. Context link subtabs are read only.

To add a context link subtab to an existing details page:

  1. Click the Create Subtab icon from either the Pages Overview page (for desktop pages) or from the details page layout (for simplified pages).

  2. Select Context link.

    This is a screenshot of the Create Subtab page,
where you configure a new context link subtab.
  3. On the Context Link subtab configuration page:

    1. Select the object that is to be exposed on the subtab, and choose the subtab display label.

    2. Optionally constrain the list of records displayed at run time using a set of search criteria for the selected object, whose run time values must match the current object record's run time values.

      Values can be literal values, or derived from the run time values in the current object record, or from the run time values in the current object's parent record.

      Note: If your search criteria includes a fixed choice list field, then you must specify the fixed choice list's run time value using the lookup code, not the lookup meaning.
    3. Select which fields you want to display on the subtab's read-only summary table at run time.

      You can configure fields for the main summary table which lists the child object records or related object records.

    4. Select which fields you want to display on the subtab's read-only detail form at run time.

      You can configure fields for the detail form that appears under the summary table.

    5. (Simplified UI only) If more than one details page layout exists, then click Next to optionally select other details page layouts that will display this subtab.

    6. Click Save and Close.

Notes Common Component Subtabs

A common component subtab adds a Notes subtab to show a list of notes related to a custom, top-level object. The Note object has a standard user interface (UI) that is shared across all Oracle Sales Cloud applications. To modify this UI, select the Note object, then select the Pages node on the object's navigation tree to access the work area configuration pages.

At run time, end users can access the Note subtab and create a common component record that is tied to the object record. For example, a user can record a note on an service request record.

To add a Note subtab to an existing details page:

  1. Click the Create Subtab icon from either the Pages Overview page (for desktop pages) or from the details page layout (for simplified pages).

  2. Select Notes.

  3. On the Common Component subtab configuration page, select Note.

Web Content Subtabs

A Web content subtab exposes an external Web site right on an object's details page. The Web content is a result of the expression that you define which builds the intended URL.

For example, on the Contact details page, perhaps you want to add a map using Bing maps that shows the location of the contact. The Bing Maps API expects the URL to be formatted in a certain manner. In this example, write an expression using the fields: Contact Address, Contact City and Contact State. Then, pass the URL to the Bing Maps API.

To add a Web content subtab to an existing details page:

  1. Click the Create Subtab icon from either the Pages Overview page (for desktop pages) or from the details page layout (for simplified pages).

  2. Select Web content.

    This is a screenshot of the Create Subtab page,
where you configure a new Web content subtab.
  3. On the Web Content subtab configuration page, enter the display label for the subtab, and then define the URL to retrieve the subtab's Web content.

    Optionally use the expression builder to build the URL expression that you need.

  4. (Simplified UI only) If more than one details page layout exists, then click Next to optionally select other details page layouts that will display this subtab.

  5. Click Save and Close.

The expression you build should include the following:

  • Use the HTTP protocol.

  • Optionally include field values from the current object as parameters, or user variables.

  • Enclose static strings in double quotation marks.

    For example, "http://www.abc.com/".

For example:

def myfinalURL = "http://www.bing.com/maps/?v2&where="
def myURL1 = ContactAddress_c != null ? ContactAddress_c : ''
def myURL2 = ContactCity_c != null ? ContactCity_c : ''
def myURL3 = ContactState_c != null ? ContactState_c : ''
myfinalURL += adf.util.GlobalEncodeField(myURL1 + " " + myURL2 + " " +myURL3)
return(myfinalURL)
Note: Before end users can view the contents of your web content subtab at runtime, they must enable the settings in their selected browser to allow mixed content. Refer to the browser documentation for instructions on how to enable this option.

Creating and Reordering Subtabs in Simplified Details Pages: Worked Example

This example illustrates how to add and reorder subtabs that appear on the simplified details pages in Oracle Sales Cloud. In this example, let's look at adding and reordering subtabs for the Account object.

Creating a Subtab

Let's create a related object subtab for the Edit Account simplified page.

Note: Before you begin, you must be in an active sandbox session.

Also, we will assume that you already created a custom child object for the Account object.

To create a subtab:

  1. Navigate to the Account object in Application Composer.

  2. Select the Pages node.

  3. On the Simplified Pages tab, under Details Page Layouts, duplicate the standard layout to create a new layout to edit, or edit another existing layout.

  4. On the Details Layout page, click the + icon at the bottom left of the page. This icon appears at the bottom of all subtabs.

  5. On the Create Subtab page, select Child object, and click Next.

  6. On the Create Subtab: Child Object page, enter details for the child object whose records you want to capture on this custom subtab.

  7. Click Save and Close.

Reordering a Subtab

Next, we can configure the custom subtab so that it appears closer to the top of other subtabs.

  1. On the Details Layout page, click the Reorder Subtabs icon which appears as two green arrows at the top of the subtabs.

  2. In the Configure Subtabs dialog, highlight your custom subtab and then use the up arrow to change the order of your subtab within the existing set of subtabs.

  3. Click OK, and then click Done.

Adding a Related Object Subtab: Worked Example

This example illustrates how you add a related object subtab to a simplified details page.

This example covers the following:

  1. Creating a related object subtab.

  2. Verifying the addition of the subtab.

Creating a Subtab

In this step, you create a related object subtab using the Sales Lead object to display fields from the Opportunity object.

For more information about creating subtabs, see Subtabs: Explained.

To create a subtab:

  1. Navigate to Application Composer.

  2. Under the Standard Objects tree, expand the Sales Lead object.

  3. Click the Pages node.

  4. Select the Simplified Pages tab.

  5. Under the Details Page Layouts region, select the page layout that you want to edit. In this example, select the standard layout and click the Duplicate Layout icon to make a copy of it to edit.

  6. On the Edit Layout page, select the plus icon in the subtabs region.

  7. On the Create Subtab page, select the Related object option.

  8. Click Next.

  9. Specify the values for the fields as follows:

    Field Label Select or Enter Description

    Data Object

    Opportunity

    The object that this subtab is based on. This subtab will display a list of opportunities that are related to a sales lead.

    Display Label

    Opportunity Name

    Name of the subtab.

    Drill Down Column

    Opportunity Name

    Your users will click this column to drill down to view more details about an opportunity record.

    Display Icon

    As applicable

    This icon appears on the simplified page as the subtab icon.

    Selected Fields

    As applicable

    The fields that you want to appear on the subtab.

  10. Save the Opportunity Name subtab.

    You have created a subtab to display opportunities on a subtab which appears on the Sales Lead details page. To view the new subtab, use the Navigator to view the Leads set of pages, and edit a sales lead record.

Verifying the Addition of the Subtab

In this step, verify whether the Opportunity Name subtab has been added to the (Sales) Leads page.

  1. Using the Navigator, select Leads.

  2. Click a lead to open the Edit Lead page.

    The Opportunity Name subtab appears along the left side, with all the other subtabs.

You have now verified the addition of the subtab.

Accessing Parent Data When Creating Subtab Records: Explained

When you add a subtab to any "parent" page, you can also configure the subtab to default parent data into new records. This means that when your users create a new subtab record, one or more fields can be automatically populated with data from the parent record. This capability is available when the subtab is based on either a standard or custom object, and it's available for both related object subtabs and child object subtabs. This topic describes how you set this up.

Relationships and Subtabs

In Oracle Sales Cloud, two objects can be related in either a one-to-many relationship or in a many-to-many relationship. Relationships are useful because they let you associate one object's records with the records of another object. For example, maybe your users want to track the trouble tickets that get created for an account. You enable this association between records first by creating a relationship between the objects, then by creating the subtabs.

Accessing Parent Data from Subtabs

At run time, when a user creates a new record on a subtab, you can choose to have values from the parent record automatically default into a field on the subtab. You must manually enable this capability by writing Groovy to pull data from one field into another field.

To enable this capability, use the Groovy AfterCreate trigger to access parent object data. The trigger will copy parent data to the new record created on the parent object's custom subtab. You must add this Groovy, as follows:

  • If the subtab is based on a one-to-many relationship:

    • Add Groovy to the "many" object.

  • If the subtab is based on a many-to-many relationship:

    • Add Groovy to the intersection object.

Let's look at the following examples in the next section.

Groovy Example for a One-to-Many Relationship

You have a Vehicle subtab on the Account object. At run time, when your users create a new Vehicle record on this subtab, you want to populate the new Vehicle record with the Account's city from the City field of the Account object.

To enable this, create an AfterCreate trigger on the Vehicle object with the following code:

setAttribute('AccountCity_c',Account_AccToVehicle_Src?.PrimaryAddressCity);
  • AccountCity_c is the target field on the Vehicle object that we want to populate with the value from the Account object's City field.

  • Account in Account_AccToVehicle_Src? indicates the source object from which to pull the data.

  • AccToVehicle in Account_AccToVehicle_Src? is the name of the 1:M Account to Vehicle relationship.

  • PrimaryAddressCity is the source data from the Account object that we will use to populate the AccountCity_c target field on the Vehicle object.

Groovy Example for a Many-to-Many Relationship

You have a Country Club Membership subtab on the Account object. At run time, when your users create a new Country Club Membership record on this subtab, you want to populate the new Country Club Membership record with the Account's city from the City field of the Account object.

To enable this, create an AfterCreate trigger on the AccountCountryClub intersection object with the following code:

setAttribute('AccountCity_c',Account_AccToCountryClub_Src?.PrimaryAddressCity

  • AccountCity_c is the target field on the Country Club Membership object that we want to populate with the value from the Account object's City field.

  • Account in Account_AccToCountryClub_Src? indicates the source object from which to pull the data.

  • AccToCountryClub in Account_AccToCountryClub_Src? is the name of the M:M Account to Country Club Membership relationship.

  • PrimaryAddressCity is the source data from the Account object that we will use to populate the AccountCity_c target field on the Country Club Membership object.

Subtabs Based on Self-Referencing Relationships

In the case of self-referencing object relationships, both 1:M and M:M, it's not possible to access parent object data when creating records in custom subtabs. For example, it is possible to have the same object (such as Trouble Ticket) as both the source as well as the target of a 1:M or M:M relationship. However, when creating new records in a subtab for such a relationship, parent record data cannot be accessed.

Modifying Work Area Lists

Creating Work Area Lists for Your Organization

Watch video

Watch: This tutorial shows how sales administrators can create their own work area lists (saved searches) for specific job roles or for the sales organization as a whole. The content of this video is also covered in text topics.

Hiding and Deleting Work Area Lists

Watch video

Watch: This tutorial shows how you can delete administrator-defined lists and hide lists provided by Oracle in the different Oracle Sales Cloud work areas. The content of this video is also covered in text topics.

Procedures

Sales administrators can use the procedures in this topic to create their own work area lists, also called saved searches. You can create lists to replace those supplied by Oracle and make your lists available to all users or target users with specific job roles.

Note: If you are creating lists for a specific job role, then you must first provision yourself with that job role so you can test your work before publishing the sandbox. See the steps outlined in the related topic Assigning Yourself an Additional Job Role.

To modify the work area lists, you do the following:

  1. Navigate to the work area and get ready by activating a sandbox and opening Page Composer.

  2. Make your modifications. You can:

    • Create your own list.

    • Hide lists provided by Oracle.

    • Delete any of the lists you created.

  3. Publish the sandbox to make your changes available to users.

Getting Ready to Modify Work Area Lists

Follow these steps to enable a sandbox and get ready to start modifying lists:

  1. Navigate to the work area landing page you want to modify.

  2. Click your user image or name, select Manage Sandboxes, and activate an existing sandbox or create and activate a new one.

    The application displays a bar across the top of the window indicating the sandbox is active.

  3. From the same user name menu, select Customize Pages.

    The Customize Pages window appears.

  4. Select one of the two context layers:

    • Site to make your changes available to everyone.

    • Job Role to target a specific job role you select from the list.

    The Editing: User Interface Page Composer toolbar appears at the top of the page with the Design mode selected.

    You are now ready to modify the work area lists. After you make your changes and test them, you must publish the sandbox to make your changes available to your users.

Creating a List

With both the sandbox and the Editing: User Interface Page Composer toolbar displayed on the top of the page, follow these steps to create your list. You create a new list by editing an existing list and saving it under a new name.

  1. In the work area landing pad, click Show Advanced SearchList field.

    The Saved Searches window appears.

  2. From the Saved Search list, select a saved search to use as the starting point for creating a new one.

    Tip: To create a list using only one field, including administrator-created fields, select one of two predefined saved searches: Name and Close Date. For opportunities and leads, select the Close Date saved search. For all other objects, select the name saved search, for example, the Account Name saved search or the Contact Name saved search.
  3. Make your changes. You can:

    • Select a different record set to change the scope of your search. For example, selecting My territory hierarchy searches all the records in your territories and their subordinate territories. The available record sets vary from object to object.

      To improve saved search performance, restrict your saved searches to smaller record sets. For example, rather than searching all the records you can see, search all the records in your territory hierarchy. Or restrict your searches to a smaller geographical area. For example, search all the accounts in one state instead of the whole country.

    • Add additional fields by clicking Add.

      Note: If you are adding an administrator-created field to your search, then the field must be indexed for best search performance.
    • Select different operators for the fields in your search. While most of the operators, which differ field by field, are self-explanatory, here are some notes on the more complex:

      • Between

        Selecting the Between operator for a date field, prompts you to enter a specific date range for the search.

      • Rolling-time operators, including Yesterday, Today, Tomorrow, Last Week, This Week, Next Week, Last Month, This Month, and Next Month

        Searching for opportunities created this month, for example, returns opportunities created in the current calendar month. The rolling-time filters use the time zone of the signed-in user for the calculation.

      • Current User

        In some fields, including the Last Updated By and Created By fields, you can create a list that displays only the records relevant to each signed-in user. For example, when you create a list of all opportunities last updated by the current user, all of your users can view the opportunities they recently updated.

      • Is Blank, Is Not Blank, and Does Not Equal

        Selecting the Is Blank operator, makes it possible to search for records missing values in a text field or a field validated by a list of values, for example. Administrators can make these operators available on fields that are not mandatory, by setting two system profile options. The Enable Additional Search Operators for Text Fields (ZCA_ENABLE_ADDITIONAL_TEXT_OPERATORS) profile option enables the Is Blank and Is Not Blank operators in text field searches. The Enable Additional Search Operators for List of Values (ZCA_ENABLE_ADDITIONAL_LOV_OPERATORS) enables the Is Blank, Is Not Blank, and Does Not Equal operators on fields validated by list of values (both fixed choice and dynamic choice list fields).

    • Specify which attributes you want to display in the search results table by selecting Columns from the View menu.

      You can select specific columns or display all columns.

    • Reorder the filter conditions by clicking Reorder.

    • Delete any fields you added to the search.

      You cannot delete the fields provided by Oracle. You can only delete fields you added.

  4. You can test your search by clicking Search.

  5. When you are satisfied with the results, click Save.

    The Create Saved Search window appears.

  6. Enter a new name for the saved search.

    You cannot reuse the names of the saved searches provided by Oracle with the application.

  7. Make sure the Run Automatically option remains selected. Selecting this option runs the query each time you select the list in the UI.

  8. If you want users to see the list generated by this search when they navigate to the work area, then select the Set as Default option.

    Note: Making a search the default does not override any default searches individual users may have created for their own use. Each user can personalize lists provided by administrators.
  9. Click OK to return to the Saved Searches window

Hiding a Saved Search Provided by Oracle

Use the following procedure to hide a saved search supplied by Oracle from the list of searches available for selection in the work area. If you want to hide a saved search that is designated as the default search, then you must first designate a different list as the default.

  1. In the work area landing pad, click Show Advanced SearchList field.

    The Saved Searches window appears.

  2. From the Saved Search list, select a saved search different from the one you want to hide.

  3. Now select Personalize.

    The Personalize Saved Searches window appears.

  4. Select the saved search you want to hide.

  5. Deselect the Show in Search List option.

  6. Click OK.

    A saved search supplied by Oracle remains available for future use but does not display in the work area. You can restore the saved search to the list in the future by selecting the Show in Search List option.

Deleting a Saved Search You Have Created

Use the following procedure to delete a saved search you have created.

Note: If you delete a saved search that you specified as the default, then no list displays when users navigate to the work area.
  1. In the work area landing pad, click Show Advanced SearchList field.

    The Saved Searches window appears.

  2. From the Saved Search list, select a saved search you want to delete.

  3. Now select Personalize.

    The Personalize Saved Searches window appears. The Saves Searches list displays the name of the saved search you are about to delete.

  4. Click Delete.

  5. Click OK.

FAQs for Extending Simplified Pages

What's the difference in upgrade behavior between standard layouts and duplicated layouts?

After an upgrade, the standard layouts for an object's creation and details pages automatically include any new underlying changes made as part of the upgrade.

However, duplicated layouts (copied versions of standard layouts) exist independently from the original, standard layout, and in general, do not uptake most underlying changes that come with an upgrade. In other words, duplicated layouts remain functionally identical to their preupgrade versions, even after an upgrade.

Thus, after every upgrade, carefully review all your duplicated layouts. You can re-create them if you want to pick up new changes introduced in the upgrade.

How can I post announcements on the home page?

Use the Announcements page to create, edit, and delete announcements. From the Navigator menu, select Tools > Announcements.

  • Only the announcement's content (not subject) appears on the home page.

  • If social networking features appear instead of announcements, then on the Home Page Layout page, change the home panel options to display announcements. To open this page from the Navigator menu, select Tools > Appearance, and then click the Home Page Layout tab.

  • Your changes on the Announcements page apply immediately to all users, even if you saved your changes while a sandbox is active and not yet published.