Oracle® Fusion Applications CRM Extensibility Guide 11g Release 7 (11.1.7) Part Number E20388-06

Home

Contents

Book List

Contact Us

Previous

Next

PDF

4 Application Composer: Using the Application Composer

This chapter contains the following:

Using Application Composer : Overview

Extending CRM Applications : How It Works

Customizing CRM Applications Across Application Boundaries : Explained

Customizing CRM Applications Using the Application Composer : Explained

Defining Objects : Explained

Object Relationships : Explained

Defining Fields : Explained

Joins and Join Fields: Explained

Field Types and Field Properties : Explained

Text Fields : Explained

Long Text Fields : Explained

Number Fields : Explained

Date Fields : Explained

Datetime Fields : Explained

Check Box Fields : Explained

Percentage Fields : Explained

Currency Fields : Explained

Fixed Choice Lists : Explained

Dynamic Choice Lists : Explained

Formula Fields : Explained

Defining Pages : Explained

Creating a Work Area: Explained

Subtabs : Explained

Tree Nodes : Explained

Actions and Links : Explained

Saved Searches for CRM Objects : Explained

Creating Saved Searches Using Page Composer : Highlights

Securing Custom Objects : Explained

Importing and Exporting Custom Objects : Explained

FAQs for Using Application Composer

From the Application Composer's Overview page, you can make application changes such as:

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

• Create foreign key-based relationships between two objects.

• Customize desktop pages by exposing your newly created fields for an object, or create an entirely new work area for your newly created objects.

  Expose object relationships on desktop pages in the form of subtabs or tree nodes.

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

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

• Enable objects for custom reporting.

Getting Started: The Application Composer's Overview Page

To access the Application Composer, log in with the Customer Relationship Management Administrator job role. Then, select Application Composer under the Tools category in the Navigator menu to navigate to the main Overview page.

From the main Overview page, select the application you want to customize using the Application choice list. Then:

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

  
  
  

• Use the links in main Overview page, also known as the local area, to select a customization task.

  Or, use the links in the Common Setup pane.

  
  
  

Change the selected application in the Application choice list at any time to customize another CRM application.

Oracle Fusion Applications Extensibility

The Application Composer is but one tool that lets you customize and extend your Oracle Fusion CRM applications. To learn more about extensibility options that are available to you across all Oracle Fusion applications, see the Oracle Fusion Applications Extensibility Guide for Business Analysts.

Cross-Application Customization Tasks

What is a cross-application customization task? This refers to any customization task that you can do to an object in one Web application by accessing an object in another Web application. For example, you might want to add a subtab to an opportunity's page (Oracle Fusion Sales) that displays marketing campaign records (Oracle Fusion Marketing).

In general, customization tasks that are available in the Application Composer can be categorized into three areas:

• Object model customizations

  For example, add a new field to an object, or create a new object entirely.

• User interface customizations

  For example, show or hide a field. Or create a work area for a new top-level object.

  Tip

  A top-level object is an object that does not have a parent as part of its definition. In other words, it is not a child object. Top-level objects have their own work areas (a set of user interface pages such as an overview page and details page). A child object does not have its own work area, and appears instead as a subtab or tree node within the work area of its parent.

• Scripting customizations

  For example, make a field conditionally required based upon a value in another field.

You can make object model, user interface, or scripting changes that cross Web application boundaries, provided that the object you are customizing exists in one of three CRM applications:

• Oracle Fusion Customer Center

• Oracle Fusion Marketing

• Oracle Fusion Sales

Additionally, when customizing an object in Customer Center, Marketing, or Sales, your customizations can include the following types of objects:

• Custom top-level objects

  When customizing an object in Customer Center, Marketing, or Sales, your customizations can include any custom top-level object that was created in Customer Center, Marketing, or Sales.

• Standard top-level objects

  When customizing an object in Customer Center, Marketing, or Sales, your customizations can include any standard top-level object that exists in any Oracle Fusion CRM Web application.

Object Model Customizations

When customizing an object's model in Customer Center, Marketing, or Sales, you can include objects from other Web applications. The types of changes you can make include:

• Dynamic choice lists

  A dynamic choice list is a field that contains a list of values which are populated from the actual data of another object.

  From a cross-application perspective, you can create a dynamic choice list field for an object in one Web application that is populated by the records from an object in another Web application.

  • For example, create a dynamic choice list field for the opportunity object (Oracle Fusion Sales) which is populated with sales lead records (Oracle Fusion Marketing).

  • Or, create a dynamic choice list field for the sales account object (Oracle Fusion Customer Center) which is populated with competitor records (Oracle Fusion Sales).

• Relationships

  A relationship is a foreign key association between two objects, and indicates a connection between two objects' data. (You create a relationship between two objects, so that you can later expose this connection on user interface pages through the use of child or related object subtabs or tree nodes.)

  From a cross-application perspective, you can create a relationship between two objects from different Web applications.

  • For example, create a relationship where the opportunity object is the source and the sales lead object is the target.

    This enables the creation of the sales lead object subtab on the opportunity object's details page. See the "User Interface Customizations" section in this topic.

  • Or, create a relationship where the sales account object is the source and the competitor object is the target.

    This enables the creation of the competitor object tree node on the Customer 360 tree. See the "User Interface Customizations" section in this topic.

  Note

  Relationships enable not only user interface changes, such as subtabs and tree nodes. In addition:

  • Each object in the relationship becomes available for scripting against the other object. See the "Scripting Customizations" section in this topic.

  • Objects in a relationship are available to be selected as child objects, when defining a custom subject area.

User Interface Customizations

When customizing an object's user interface in Customer Center, Marketing, or Sales, you can include objects from other Web applications. The types of changes you can make include:

• Subtabs and tree nodes

  You can display details that are related to the current object but derived from another object. You do this by adding subtabs to an object's details page, and specifying the source of subtab data, or by adding tree nodes to the object's tree, and specifying the source of tree node data.

  From a cross-application perspective, the source of subtab or tree node data can come from an object in a different Web application.

  • For example, add a Sales Leads subtab to the Opportunity details page.

  • Or, add a Competitor tree node to the Customer 360 tree.

Note that a relationship must first exist between the two objects, prior to adding subtabs or tree nodes.

Scripting Customizations

When writing groovy scripts as part of customizations to an object in Customer Center, Marketing, or Sales, you can include objects from other Web applications in your scripts. The types of changes you can make include:

• When writing a script, access data from any standard object in any CRM Web application, as well as from any custom top-level object created in Customer Center, Marketing, or Sales, using the newView() built-in function. The newView() built-in function is described in "Accessing the View Object for Programmatic Access to Business Objects" in Oracle Fusion CRM Application Composer Scripting Guide (ID 1354807.1) on My Oracle Support.

  Note that a relationship must first exist before you can script against other objects.

  • For example, write a script in a "before update" trigger on the opportunity object that counts the number of leads that involve this opportunity. At run time, when a user saves an opportunity record, the trigger populates a custom field on the opportunity with the number of related leads.

  • Or, write a script in a "before insert" trigger on the sales account object that retrieves information about the opportunity associated with the organization that the sales account is tied to.

Oracle Fusion Common CRM Objects: Exceptions

Objects available in the Common Web application include CRM common components such as tasks, interactions, and notes, as well as Master Data Management (MDM) and Common Party User Interface (CPUI) objects. These Common objects are available to you when customizing an object in Customer Center, Marketing, or Sales.

When customizing Common objects themselves, however, the object model and user interface cross-application customization tasks described above are not available. Scripting customizations are available, although you should proceed carefully when writing scripts for Common objects that access objects outside the Common Web application. Your scripts will work only when triggered within the context of the other Web application.

For example, when creating a note, you can write a script to insert details about an opportunity into a custom field on the note. This script will work only if a user creates the note from within Sales. If, however, the user creates the note from within Marketing, then the script will not work.

On the main Overview page, the regional pane at left displays the object tree, which lets you browse an application's existing object configuration in a tree format. The object tree reflects the latest configuration of the application: both standard objects as well as custom objects.

To use the object tree:

1. Select Application Composer from the Navigator menu, under the Tools category.

2. On the main Overview page, select an application from the Application choice list.

   
   
   

3. For each object node, whether standard or custom, expand it further to view and edit object details, such as an object's fields and desktop pages where the object is exposed.

   
   
   

   Note

   At the top of the object tree, you can also click the New icon to create a new custom object.

   For both standard and custom objects, you can view and edit the following details:

   • Fields

     Add new fields to an object.

   • Pages

     Modify the pages on which an object appears.

   • Buttons and links

     Add buttons or links to desktop pages.

   • Server scripts

     Write application logic that controls the behavior of an object's records.

   • Saved searches

     Edit saved searches for an object.

   For custom objects, you can also view and edit details for:

   • Security

     Implement functional and data-level security for an object and its records.

Creating a Custom Object

To create a new custom object, you first select an application on the main Overview page of the Application Composer. The new custom object will belong to the application that you select. After you select the application:

1. Select the Custom Objects node or link in either the object tree or local area of the main Overview page.

   On the resulting summary table, click the New icon.

2. Or, at the top of the object tree, click the New icon

3. Complete the primary identifying attributes for a custom object:

   1. Display Label

      An object's display label is the user-friendly label for an object, and also becomes the default page title for the object's work area.

   2. Plural Label

      The plural label is used as the title of the object's work area.

   3. Record Name

      Use the Record Name field to specify the display label for the object's RecordName field. The RecordName field stores the "name" of the record. For example, for an opportunity object, this RecordName field stores the opportunity's name. Accordingly, if you were creating this object as a custom object, then you would set the Record Name field to Opportunity Name.

      Typically, this field is the object's primary user-recognizable identifier for the object, and as such, is usually the identifier that run time users drill down on, from the overview page to the detail page.

   4. Object Name

      The object name is the internal name for the object.

   5. Description

Using the Object Overview Page

The Object Overview page provides a high-level overview of a standard or custom object. The Object Overview page displays the primary attributes for an object, plus a list of child objects and related objects, if any.

To access the Object Overview page:

1. Select an application on the main Overview page.

2. Select a standard or custom object in the object tree.

3. Or, select the Standard Objects or Custom Objects node or link in either the object tree or local area of the main Overview page, choose an object from the resulting summary table, and select the Edit icon.

From the Object Overview page, you can:

• Edit the object's primary attributes, described in the previous section.

• View the parent child relationships that were created for this object.

  You can also create new child objects from this page, which implicitly creates a new parent child relationship.

• View the non-parent child relationships that were created for this object.

Editing an Object's Attributes

After an object has been created, you can edit its attributes from its Object Overview page.

To edit an object's attributes:

1. Select an application on the main Overview page.

2. Select the Standard Objects or Custom Objects node or link in either the object tree or local area of the main Overview page.

3. From the resulting summary table, select an object and then select the Edit icon to navigate to its Object Overview page.

4. On the Object Overview page, click Edit:

   • Change the object's display label, description, and record name at any time.

   • You cannot change the Object Name and API Name after the object has been created.

     A custom object's API name for an object is automatically derived using the logical name followed by _c. You use the API name in Groovy expressions that you build with the expression editor, when writing business logic for the object.

Viewing Child and Related Objects

The Object Overview page displays a list of child objects and related objects, if any, that have been created for an object. You can also create new child objects from this page.

• A child object is an object with a cascade delete relationship to a parent object. This means that if you delete the parent object, then all its children are automatically deleted. A child object does not exist outside the context of the parent object, and does not have its own work area. You cannot change a child object to a parent object after the child object has been created.

• Related objects can exist independently of each other, even if one object is deleted. Related objects are connected in a foreign key-based relationship between two top-level objects, not as parent and child. These types of relationships include reference relationships and dynamic choice list relationships.

  Related objects can have either a one-to-many or a many-to-one relationship with the current object. Note that an object can be related to itself to model a hierarchy of the object. In this case, the object itself is displayed on its Object Overview page as a related object. For example, the Department and Sub-department objects would be displayed in this way.

  Note

  You do not create these types of relationships from this page. Instead, manage relationships from the Relationships page, which you can access from the Application Composer's main Overview page. Or, create a dynamic choice list relationship by creating a dynamic choice list field for an object, which derives its choice list values from another object.

To create a child object for a standard or custom object:

1. Navigate to an object's Object Overview page.

2. Click the Create Child Object button. Creating a child object is the same as creating a custom object, except:

   • The current object is automatically displayed as the parent object.

   • Specify the Child Collection Name field to specify the internal name for this set of child object records, which can be used later when writing Groovy scripts.

Deleting a Custom Object

The Application Composer does not support the deletion of either standard or custom objects. If you no longer need an object, optionally enter a note in the description that the object is no longer used.

1. Select Relationships in the Common Setup pane.

2. On the Relationships page, click the New icon.

   
   
   

3. Select the source object and target object.

   
   
   

   A child object cannot be the source object or target object.

   Common components, such as notes, interactions, or tasks, are not available for selection as either source objects or target objects.

   In general, you create a relationship between two objects within the same application. You can, however, select common objects as target objects. Common objects include:

   • Trading Community Resource

   • Trading Community Organization Contact

   • Trading Community Organization Profile

   • Trading Community Address

   Once you create a relationship, you can no longer edit the source and target objects.

   This relationship adds a field to the target object to store the foreign key details. If the source object is ever deleted, the target object records remain in the system.

4. Enter the relationship name and description.

   Once you create a relationship, you can no longer edit the relationship name.

5. Optionally add the target object in a subtab to the source object's detail page, or as a tree node.

Adding Subtabs or Tree Nodes

After you create relationships between objects, you can then expose the "many" objects on a subtab or tree node that is displayed on the "one" object's details page or tree.

When adding a subtab or a tree node to an object's details page or object, you select to add a Child or Related Objects subtab from the object's Pages Overview page. The Application Composer lets you add a subtab or tree node based on any target object that has a relationship with the current object as the source object. Subtabs and tree nodes are discussed in related topics.

Many-to-Many Relationships

Objects can also have a many-to-many relationship. For example, a service request can have multiple employees working on it. At the same time, a single employee can work on multiple service requests. In this scenario, you would create a many-to-many relationship between the service request and employee objects, where the related records from both objects store their primary identifiers in an intersection table.

To create a many-to-many relationship using the Application Composer:

1. Create a child object of one object, and use this child object to represent the intersection table that stores the record identifiers of both objects.

   For example, create a service request member object as a child of the service request object. The service request member object's table records the service request identifier as a foreign key.

2. Add a dynamic choice list for the new child object whose related object is the other object in the many-to-many relationship.

   For example, create a dynamic choice list, Support Representative, for the service request member object where the choice list's related object is employee. The Application Composer automatically creates the underlying relationship for you, where the employee is the source object and the service request member is the target object. The service request member object's table records the employee identifier as a foreign key.

Now, the service request member object's table records two foreign keys: one for the service request object and the other for the employee object. This enables the many-to-many relationship. You can now do the following:

• Create a child subtab on a service request's details page. The subtab displays all employees that are working on a specific service request.

• Create a related object subtab on an employee's details page. The subtab displays all service requests that an employee is working on, since each employee can work on multiple service requests.

Defining Fields : Explained

You can constrain the actual values that display in this fixed choice list at run time by relating this fixed choice list to a parent fixed choice list. The value selected in the parent fixed choice list drives the values that display in this fixed choice list. For example, you might want your users to see two choice lists on a desktop page where they can create a trouble ticket: one choice list for specifying the trouble ticket type and one choice list for specifying the trouble ticket area. If a user selects Hardware from the Type choice list, then the Area choice list should contain a list of only hardware options against which the trouble ticket can be logged.

To do this, select the Constrain List by Parent Field Value Selection check box, select the parent field, and then map the values between the parent lookup type and this field's lookup type.

To implement the previous example:

1. Define the Type fixed choice list.

2. Define the Area fixed choice list.

3. Select the Constrain List by Parent Field Value Selection check box and select the parent field, Type.

4. Finally, map the values between the Type and Area lookup types.

   For example, map all relevant hardware values in the Area lookup type's set of values, such as desktop and laptop, to the value of Hardware in the Type's lookup type.

Additional Fixed Choice List Specifications

Additional specifications for this field type include the following details:

• Data type is VARCHAR2 (1500).

• List Data Source region

  
  
  

  • Related Object

    The values in a dynamic choice list are populated from another object's data. Select the related object first, then use the List Selection Display Value choice list to select the related object's field that you want to expose as a field for your own object. Selecting the related object is possible only during field creation.

    Note

    The set of objects that are available for selection is constrained to top-level objects only. You cannot select a child object as a related object.

    In our example, the related object would be Account.

    Tip

    Once you create a dynamic choice list, you can easily recognize the choice list's related object from the Fields page. The Fields page displays summaries of both standard and custom fields for the selected object. If a dynamic choice list was created, then the Type column includes the related object. In our example, the field type would be Choice List (Dynamic) <Account>.

  • List Selection Display Value

    The List Selection Display Value choice list is the related object's field that is displayed within the dynamic choice list as the first column at runtime. This is the primary field on the related object that your users will use to make the appropriate selection. In our example, the field might be something like Name.

  • Data Filter

    You can further refine the set of data that appears within the dynamic choice list at run time by using data filters.

    In our example, we could filter out any accounts outside a particular region.

• Additional List Display Values region

  
  
  

  You can further refine the look and feel of the dynamic choice list by selecting additional fields to display in the choice list.

  Use the Additional List Display Values shuttle to include additional related object fields in the dynamic choice list at run time. These additional fields assist your users in making a selection from the choice list. The shuttle does not include the field that you already selected in the List Selection Display Value choice list.

  There is no limit on the number of additional fields that you can select.

• Additional List Search Fields region

  
  
  

  You can indicate which additional related object fields can be added as search criteria in the dynamic choice list's Search and Select dialog.

  Use the Additional List Search Values shuttle to include additional related object fields in the dynamic choice list's Search and Select dialog, accessed using the Search... link at run time. The shuttle does not include the field that you already selected in the List Selection Display Value choice list.

  There is no limit on the number of additional fields that you can select.

Implicit Relationship Creation

When you create a dynamic choice list for an object based on a related object, you are implicitly creating a one-to-many foreign key relationship where the current object is the "many" object and the related object is the "one" object. This implicit creation of a relationship lets you later add a related object subtab for the "many" object on the "one" object's details page. You can view these implicitly created choice list relationships on the Relationships page.

In the previous example of making a list of accounts available for selection for a help request, an account can be tied to multiple help requests. The relationship that is created is a one-to-many relationship between the account and help request objects, which enables users to store an account identifier in the help request object's table. In this relationship, the account object is the source object and the help request object is the target object. If a source object is ever deleted from the system, then at run time, the dynamic choice list will have no values in it.

Later, you might want to expose a related object subtab on the account details page which shows, for a single account, all the help requests that are related to it. You can create this related object subtab because the relationship was already created when you created the dynamic choice list.

Additional Dynamic Choice List Specifications

Additional specifications for this field type include the following details:

• Data type is VARCHAR2 (1500).

Use the expression editor to write an expression that calculates the field's value at run time.

For example, if your expression calculates the value of an employee's annual bonus amount, then you could set the expression to automatically recalculate that amount if the employee's salary changes. Whenever the salary changes, the bonus field immediately reflects the new bonus amount without your users having to refresh the employee's record.

In another example, if your expression determines the right customer phone number to use for an opportunity, then you could set the expression to automatically reset the phone number if the opportunity's customer account changes. Whenever the customer account changes, the phone number field immediately reflects the new phone number without your users having to refresh the opportunity record.

Additional Formula Field Specifications

Additional specifications for this field type include the following details:

• Data type is set by the Formula Type property.

• The formula field type is not supported by custom subject areas. This means that you cannot add formula fields to a custom report.

• You cannot search on a formula field.

To access the Pages overview page:

1. Select an application on the main Overview page.

2. Select a standard or custom object in the object tree.

3. Select the Pages node.

   
   
   

   Note

   Only top-level objects have pages that you can configure. A child object does not exist outside the context of the parent object, and does not have its own work area.

From the Pages overview page, you can:

• Create a new set of pages for an object, collectively known as a work area, if no set of pages has been created yet.

• View the pages where the object is already exposed to users, and further customize those pages by adding or removing fields.

• Create one or more subtabs to display on the object's Details page.

• Create mobile application pages in Oracle Fusion Mobile Sales by using a wizard.

  Similar to the work area creation process, the creation process for mobile pages uses a wizard where you can select which custom fields and related objects to add to mobile pages. Select the Mobile Pages tab to access the mobile pages wizard.

• Expose new fields in an alternative set of simplified user interface pages, if available for a standard object, by selecting the Simplified Pages tab.

  Note that the Simplified Pages tab displays only if a set of simplified pages exists for the standard object.

Defining Pages

Use configuration pages to specify which fields are displayed on the standard application pages for an object. After you create new objects and fields, navigate to the Pages overview page. The Pages overview page contains hyperlinks to the configuration pages for an object's existing work area. Use these configuration pages to customize the object's work area pages, for example add newly created fields to a creation page.

Use the configuration pages available from the Pages overview page as follows:

• Navigator Menu

  For custom objects, specify the display label that appears in the Navigator menu at run time. For standard objects, use the Manage Menu Customizations task in the Setup and Maintenance work area to change the display label for standard object work areas.

  
  
  

• Regional Pane

  Select which panes to display in the regional area. You can also specify if you want the regional area and individual panes to be expanded (or collapsed) by default.

• Overview Page

  The overview page includes two regions, the local search and the summary table, and includes configuration pages for each.

  • Edit Local Search

    The following figure show the Edit Local Search fields selection, one of the work area configuration pages in the Application Composer.

    
    
    

    1. Select the fields that will be used to search in the local search region.

       The list of fields available for selection is displayed to you in a single column, although the local search is formatted as a region with two columns. The first field you select is displayed in the first column, the second field you select is displayed in the second column, the third field you select is displayed in the first column again, and so on.

       Note

       During field creation, consider indexing any fields that you plan to display as search criteria for your custom objects.

       The following figure shows the Edit Local Search fields operators, one of the work area configuration pages in the Application Composer.

       
       
       

    2. For any field, you can select the following options:

       • Required: The user must include this field in a search at run time.

       • At Least One is Required: The user must include at least one of the selected fields in a search at run time.

  • Edit Summary Table

    
    
    

    1. Select the fields that you want to display as columns in the summary table.

    2. Add custom buttons to the summary table, if you previously created them.

• Creation Page

  
  
  

  1. Select the fields that you want to display on the object's creation page.

     The list of fields available for selection is displayed to you in a single column, although the creation page is formatted as a page with three columns. The first field you select is displayed in the first column, the second field you select is displayed in the second column, the third field you select is displayed in the third column, the fourth field you select is displayed in the first column again, and so on.

• Details Page

  
  
  

  1. Select the fields that you want to display on the object's details page, including both the default summary and detailed summary regions.

     Tip

     Include the primary object fields in the default summary, since the detailed summary could be collapsed when users navigate to this page.

     The list of fields available for selection is displayed to you in a single column, although the details page is formatted as a page with three columns. The first field you select is displayed in the first column, the second field you select is displayed in the second column, the third field you select is displayed in the third column, the fourth field you select is displayed in the first column again, and so on.

  2. Add custom buttons, links, and actions to the details page, if you previously created them.

  3. Select the Allow Attachments check box to enable the attachments feature on the run time details page, in the collapsible detailed summary.

  4. The Pages Overview page also lets you configure subtabs that display on the details page. Subtabs include information that is related to the object record. Adding subtabs to a details page is discussed in a related topic.

     If the object uses a tree rather than subtabs to display related pages, then you can configure tree nodes that you add to the object's tree. The information displayed in both subtabs and trees can be derived from other objects or from a source outside Oracle Fusion CRM Applications. For more information on adding tree nodes to an object's tree, see the related topic on this subject.

• Reusable Regions

  At run time, users can launch the Select and Add dialog box from a dynamic choice list field to search for and select a value. Users can use the dynamic choice list field at run time, and can launch the picker to limit their choices and more easily find and make the right selection. Use the Create Picker link or Edit Picker link to access the Search and Select picker dialog box for an object, which you can start from any dynamic choice list that is based on that object. In the Search and Select picker dialog box you can specify which fields you want to appear in the search region and in the search results table.

  Note

  If you create a dynamic choice list that is based on a custom object, you must create the picker for the same custom object.

  To create or edit a picker, use the following steps.

  1. Create or edit the dynamic choice list field for which you want to create a picker. In the Related Object field for that dynamic choice list, make sure that you have selected the correct object on which you want to base the dynamic choice list.

  2. In the Pages page, click Create Picker or Edit Picker.

     The Edit Picker page opens.

  3. In the Configure Picker Search list, select the fields that you want to appear in the search region.

  4. In the Configure Picker Table list, select the fields that you want to appear in the search results table.

  At run time, the user can select a value from the dynamic choice list field by using the Search and Select picker to find the right value among all the other values.

  1. Navigate to the object's work area for which you created the picker and dynamic choice list.

  2. In the Overview page, click the object name.

     The following figure shows the Summary page for a custom object named Primary with a dynamic choice list field named Opportunity List.

     
     
     

  3. In the Edit object page, click the magnifying glass icon next to the dynamic choice list field to open the Search and Select picker dialog box.

     The following figure shows the Search and Select picker dialog box at run time.

     
     
     

  The user can add the selected value in the dynamic choice list field by using the following steps:

  1. In the Search and Select picker dialog box, enter the search criteria for the field.

  2. Click Search.

  3. Select the record.

  4. Click OK.

     The value is populated into the dynamic choice list field.

  • Edit Regional Search

    Select the fields the user can search on using the search pane in the regional area.

    
    
    

    To display the entire regional search pane, check the Enable check box. Otherwise, the regional search shows only the selected fields.

    For any field, you can select the following options:

    • Required: The user must include this field in a search at run time.

    • At Least One is Required: The user must include at least one of the selected fields in a search at run time.

    • Default Operator: The user can define each search field value by using one of the listed operator options. For example, you can specify that CreationDate is equal to or occurs before or after the date the user enters, or that Sales Name starts with a specific letter.

Creating a Work Area

When first created, top-level custom objects do not yet have pages in a run time CRM application where those objects are exposed to users. For each custom object that you create, you must create the set of pages where the records that belong to the object will be exposed to users.

The Application Composer uses a wizard to walk you through the creation of these pages, collectively known as a work area. For more information on creating a work area, see the related topic on this subject.

Do not create a work area for child objects.

Object Security on Pages

After you create custom objects and fields, you then expose them on desktop pages for your users. By default, the object and its records are visible and can be edited only by a user who has the Application Composer duty role. Grant additional access manually for either an object or role, using the Application Composer's security policy configuration pages.

The security options available to you for restricting access to custom objects, including child objects, are discussed in a related topic.

Using Page Composer to Customize Pages

After you create a set of new pages, or edit preexisting pages delivered by a CRM application, you cannot use Page Composer to edit those pages again.

To access the work area wizard:

1. Select an application on the main Overview page.

2. Select a standard or custom object in the object tree.

3. Select the Pages node.

   Note

   Only top-level objects have pages that you can configure. A child object does not exist outside the context of the parent object, and does not have its own work area.

4. Select the hyperlink to launch the work area wizard.

Configuring the Navigator Menu

As part of the work area creation for a custom object, you must specify the object label that appears in the Navigator menu at run time. The label you specify is what users will select to navigate to this work area.

On this page, you can also do the following:

• Select a menu category under which the object label appears.

• Adjust the position of Navigator menu items within the selected menu category.

  For example, move your newly created object label to appear at the top of the list.

After creating the work area for a custom object, the work area label automatically appears in the Navigator menu without your having to reauthenticate.

Extending Regional Search Parameters

Extending the Regional search is part of the first step in creating a work area. By adding custom parameters, you can expand the search parameters of the Regional area for both custom and out-of-the-box objects in a Fusion application at run time.

Each field can have one of the following properties:

• Required: Set a field as required on the object search region. This field must be populated.

• At Least one is required: Set at least one field as a required field or a collection of required fields. You must populate one field from this group.

• Default Operator: Set an operator field that appears in object search as the default.

Configuring the Local Search Region

Select the fields that you want to display as search criteria in the local search region. The local search region appears above the summary table on an object's overview page. Adding fields to this region is optional.

1. Select the fields that you want to display as search criteria fields in the local search region.

   The list of fields available for selection is displayed to you in a single column, although the local search region is formatted as a region with two columns. The first field you select is displayed in the first column, the second field you select is displayed in the second column, the third field you select is displayed in the first column again, and so on.

Configuring the Overview and Creation Pages

Select the fields that you want to display in the work area's overview page, and in the object's creation page.

1. Select the fields that you want to display as columns in the summary table, on the object's overview page.

2. Select the drilldown column for the summary table.

   The drilldown column is the column in the summary table that users can click to drill down to an object record's details page. You cannot change a summary table's drilldown column after the work area is created.

3. Select the Allow Access Grant check box if you want users to be able to grant access to a record in the summary table to another user, at run time.

4. Add custom buttons to the summary table, if you previously created them.

5. Select the fields that you want to display on the object's creation page.

   The fields that you select should include the object's required fields.

   The list of fields available for selection is displayed to you in a single column, although the creation page is formatted as a page with three columns. The first field you select is displayed in the first column, the second field you select is displayed in the second column, the third field you select is displayed in the third column, the fourth field you select is displayed in the first column again, and so on.

Configuring the Details Page

Select the fields that you want to display on the object's details page.

1. Select the fields that you want to display on the object's details page, including both the default summary and detailed summary regions.

   Tip

   Include the primary object fields in the default summary, since the detailed summary could be collapsed when users navigate to this page.

   The list of fields available for selection is displayed to you in a single column, although the details page is formatted as a page with three columns. The first field you select is displayed in the first column, the second field you select is displayed in the second column, the third field you select is displayed in the third column, the fourth field you select is displayed in the first column again, and so on.

2. Add custom buttons, links, and actions to the details page, if you previously created them.

3. Select the Allow Attachments check box to enable the attachments feature on the run time details page, in the collapsible detailed summary.

1. Select an application on the main Overview page.

2. Select a standard or custom object in the object tree.

3. Select the Pages node.

   Note

   Only top-level objects have pages that you can configure. A child object does not have its own work area.

4. On the Pages Overview page, click the Create Subtab icon in the Details Page region to create one or more subtabs to display on the object's details page.

5. Select the type of subtab you want to add.

   
   
   

Child or Related Object Subtabs

A relationship is a foreign key association between two objects. Using Application Composer, you can create a one-to-many relationship between two objects within the same application. Once relationships are created, you can expose the "many" objects on a subtab that is displayed on the "one" object's details page. For example, an account can have multiple service requests associated to it. To expose a list of service requests associated with a specific account as a subtab on the account's details page, you must first create a one-to-many relationship between the account and service request objects. In this example, the account is the source object and the service request is the target object. This relationship adds the account identifier to the service request object's table.

Application Composer lets you add a subtab to an object's details page for either a child object or for three types of related objects. These objects exist in four types of one-to-many relationships:

• Parent child relationship

  Parent child relationships are implicitly created when a custom object is created as a child of a top-level object.

  For example, to enable the creation of a subaccount subtab on an account's details page, you would create the subaccount object as a child of the account object. This relationship adds the account identifier to the subaccount object's table.

• Choice list relationship

  Choice list relationships are implicitly created between two objects when you create a dynamic choice list field.

  For example, to enable the creation of a department subtab on an employee's details page, you would create a dynamic choice list, HR Representative, for the department object where the choice list's related object is employee. Application Composer automatically creates the underlying relationship for you, where the employee is the source object and the department is the target object. This relationship adds the employee identifier to the department object's table, thus enabling the creation of a department subtab on an employee's details page. The subtab displays all departments that an HR representative can manage, since each HR representative can be in charge of multiple departments of a company.

• Reference relationship

  Reference relationships are explicitly created between two top-level objects using the Create Relationships page.

  Using our previous example, perhaps you don't need to display an HR Representative choice list on a department desktop page, but you still want to add a department subtab to an employee's details page. In this case, manually create a reference relationship between the employee and department objects where the employee is the source object and the department is the target object. This enables the creation of the department subtab. Such a reference relationship, however, does not automatically create a corresponding HR Representative choice list for use on the department desktop page. In fact, once you manually create a relationship, you cannot reuse the relationship to create a choice list. This means that you should carefully consider the need for a choice list before you create a reference relationship.

• Standard relationship

  Standard relationships are relationships that are already created between two standard objects by the Oracle Fusion CRM application.

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

1. On the Pages Overview page, click the Create Subtab icon.

2. Select Child or Related Object.

   
   
   

3. On the Child or Related Object subtab configuration page:

   1. Select the related object from the list of all related objects that is to be exposed on the subtab, and choose the subtab display label.

   2. Optionally hide the New and Delete buttons that appear on the subtab at run time.

      For child object subtabs, you can also optionally hide the Edit button.

   3. For child object subtabs only, specify if you want to display the Manage Permission button on the subtab at run time.

      At run time, users can select an object record and click that button to specify the level of access another user should have to the selected record.

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

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

   5. Select which buttons you want to display on the subtab at run time.

      Note

      This region appears only if you previously created buttons for this object.

   6. Select which fields you want to display on the subtab detail form at run time.

      You can configure fields for the detail form that appears under the summary table. If the subtab's object is a child object, then users can enter child object data into this detail form at run time. Always include required fields in this section.

      If the subtab's object is a related object, then users can associate an existing record of the subtab object to the master object of the page. However, to create new related object records, users must do so in the object's own creation page.

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. On the Pages Overview page, click the Create Subtab icon.

2. Select Context Link.

   
   
   

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.

      Tip

      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.

      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.

Common Component Subtabs

A common component subtab adds a Notes, Tasks, Interactions or Appointments subtab to show a list of the selected components related to a custom, top-level object. Each component has a standard user interface (UI) that is shared across all Oracle Fusion CRM applications. To customize such a UI for all common components (other than Appointments), select the appropriate object under the Common application, then select the Pages node on the object's navigation tree to access the work area configuration pages.

At run time, users can access these subtabs and create a common component record that is tied to the object record. For example, a user can record a customer interaction on an service request record.

• Notes

• Tasks

• Interactions

• Appointments

To add a common component subtab to an existing details page:

1. On the Pages Overview page, click the Create Subtab icon.

2. Select Common Component.

   
   
   

3. On the Common Component subtab configuration page, select the type of common component you want to add to the details page as a subtab.

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 Google map that shows the location of the contact. The Google 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 Google Maps API.

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

1. On the Pages Overview page, click the Create Subtab icon to create one or more subtabs to display on the object's details page.

2. Select Web Content.

   
   
   

3. On the Web Content subab 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 editor to build the URL expression that you need.

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 myURL1 = adf.util.GlobalEncodeField(ContactAddress_c)
def myURL2 = adf.util.GlobalEncodeField(ContactCity_c)
def myURL3 = adf.util.GlobalEncodeField(ContactState_c)
def myfinalURL = "http://maps.google.com/maps?hl=en&q=" + myURL1 + "+" + myURL2 + "+" + myURL3
return(myfinalURL)

1. Select an application on the main Overview page.

2. Select a standard object, either the Sales Account Profile or Partner object, in the object tree.

3. Select the Pages node.

   Note

   Only the top-level objects, Sales Account Profile and Partner, let you add tree nodes.

4. On the Pages Overview page, click the Create Tree Node icon to create one or more tree nodes to display on the object's tree.

5. Select the type of tree node you want to add.

   
   
   

Child or Related Object Tree Nodes

A relationship is a foreign key association between two objects. Using the Application Composer, you can create a one-to-many relationship between two objects within the same application. Once relationships are created, you can expose the "many" objects on a tree node that is displayed on the "one" object's tree. For example, a partner can have multiple contacts associated to it. To expose a list of contacts associated with a specific partner as a tree node on the partner's tree, you must first create a one-to-many relationship between the partner and contact objects. In this example, the partner is the source object and the contact is the target object. This relationship adds the partner identifier to the contact object's table.

The Application Composer lets you add a tree node to an object's tree for either a child object or for three types of related objects. These objects exist in four types of one-to-many relationships, which are described in detail in the related topic about object relationships:

• Parent child relationship

• Choice list relationship

• Reference relationship

• Standard relationship

To add a child or related object tree node to an existing tree:

1. On the Pages Overview page, click the Create Tree Node icon.

2. Select Child or Related Object.

   
   
   

3. On the Child or Related Object tree node configuration page:

   1. Select the tree node category and enter the tree node label.

   2. Select the related object from the list of all related objects that is to be exposed on the tree node page.

   3. Set the position of the new tree node.

   4. Optionally hide the New and Delete buttons that appear on the tree node page at run time.

      For child object tree node pages, you can also optionally hide the Edit button.

   5. For child object tree node pages only, specify if you want to display the Manage Permission button on the tree node page's summary table at run time.

      At run time, users can select an object record and click that button to specify the level of access another user should have to the selected record.

   6. Select which fields and links you want to display on the tree node page's summary table at run time.

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

   7. Select which buttons you want to display on the tree node page at run time.

      Note

      This region appears only if you previously created buttons for this object.

      You cannot add buttons to a tree node page for the Sales Account Profile object.

   8. Select which fields you want to display on the tree node page's detail form at run time.

      You can configure fields for the detail form that appears under the summary table. If the tree node's object is a child object, then users can enter child object data into this detail form at run time. Always include required fields in this section.

      If the tree node's object is a related object, then users can associate an existing record of the tree node object to the master object of the page. However, to create new related object records, users must do so in the object's own creation page.

Context Link Tree Nodes

A context link tree node page 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 tree node pages are read only.

To add a context link tree node to an object's tree:

1. On the Pages Overview page, click the Create Tree Node icon.

2. Select Context Link.

   
   
   

3. On the Context Link tree node configuration page:

   1. Select the tree node category and enter the tree node label.

   2. Enter the name of the tree node filter.

   3. Select the object that is to be exposed on the tree node page.

   4. Set the position of the new tree node.

   5. 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.

      Tip

      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.

      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.

   6. Select which fields you want to display on the tree node page'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.

   7. Select which fields you want to display on the tree node page's read-only detail form at run time.

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

Web Content Tree Nodes

A Web content tree node page exposes an external Web site on desktop page. The Web content is a result of the expression that you define which builds the intended URL.

For example, on the Contact tree node page, perhaps you want to add a Google map that shows the location of the contact. The Google 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 Google Maps API.

To add a Web content tree node to object's tree:

1. On the Pages Overview page, click the Create Tree Node icon to create one or more tree nodes to display on the object's tree.

2. Select Web Content.

   
   
   

3. On the Web Content tree node configuration page:

   1. Select the tree node category and enter the tree node label.

   2. Set the position of the new tree node.

   3. Define the URL to retrieve the tree node page's Web content.

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

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 myURL1 = adf.util.GlobalEncodeField(ContactAddress_c)
def myURL2 = adf.util.GlobalEncodeField(ContactCity_c)
def myURL3 = adf.util.GlobalEncodeField(ContactState_c)
def myfinalURL = "http://maps.google.com/maps?hl=en&q=" + myURL1 + "+" + myURL2 + "+" + myURL3
return(myfinalURL)

To define an action or link for an object:

1. Select an application on the main Overview page.

2. Select a standard or custom object in the object tree.

3. Select the Actions and Links node.

To create a new script or URL:

1. In the Create Action or Link page, enter a descriptive name in the Display Label field.

2. For Type, select Action and, for Source, select Script or URL.

3. In the Script region click the New icon.

The following figure shows the Create Action or Link page showing a static URL enclosed in double quotation marks..

If the source is a URL, you can enter a static URL, enclosed in double quotation marks. Or, you can define the URL by using the expression editor, which provides access to this object's fields to assist you in constructing the URL. If this object has a parent or relationship with a source object, then optionally change the context to access another object's fields for URL definition.

Any new functions that you create will be added to the Method Name choice list. If functions were already created for the object, then you can select one of them from the Method Name choice list. Object functions that are created elsewhere through other flows, such as server scripts, can also be used here.

To switch the context to the object's parent or related source object, for access to the object's fields for the URL definition, check the Select alternative content check box.

The following figure shows a script in the URL Definition window.

If the source is a script, you can either select a predefined object function from the Method Name choice list, or create a new object function using the expression editor.

After you save actions or links, you can expose them on UI pages by configuring the Applications Composer options available in the Edit Summary Table page in the Pages node of an object.

The following figure shows a selected button and fields in the Edit Summary Table page in the Pages node of Applications Composer.

For example, the Edit Summary Table could have links in the fields selector with standard or custom fields because at runtime the UI displays the URL link as if it is a field in a table. Actions can be configured in potentially two places in the UI, on the toolbar as a button and in the Actions menu for a table. Depending on how you configure the actions and links, in the Edit Summary Table you could see both the available and selected buttons and actions, or one, or none.

The figure above shows the Configure Summary Table: Actions with options checked for the Show Create, Show Edit, and Show Delete options on the Action menu. It also shows a custom button and a custom action.

After you define an action, you can then expose it as a button or an Action menu option in a variety of locations:

• Summary table on the overview page

• Default summary on the details page

• Summary table on a details page's subtab

• Summary table on a tree node page for a child object

• Revenue table on the details page for the opportunity object

The following figure shows an overview page with exposed Create, Edit, and Delete options and a custom Ask_Assistance option on the Actions menu. It also shows the custom toolbar button Ask_Assistance, and a custom table column.

The figure above shows the exposed Create, Edit, and Delete options and a custom Ask_Assistance option on the Actions menu. It also shows the custom toolbar button Ask_Assistance, and a custom table column.

After you define a link for an object, you can add that link to a variety of locations in that object's work area. You can add a link wherever you can add a field. Possible locations include, but are not limited to:

• As a column in the summary table on the overview page

• Default summary on the details page

• As a column in the summary table on a details page's subtab

• In the detail form under the summary table on a details page's subtab

• As a column in the summary table on a tree node page for a child object

• As a column in the revenue table on the details page for the opportunity object

1. Select an application on the main Overview page.

2. Select a custom object in the object tree.

3. Select the Security node.

   Or, from the role-centric Define Policies page, select a custom object.

   
   
   

From the object-centric Define Policies page, you can:

• Enable function security for a role.

• Enable data security for a role.

• Allow users to grant access to a specific record at run time, to users with a given role.

Securing Roles

The Role Security page displays a list of the enterprise-level duty roles, which map to a CRM job role. Select a role and click the Define Policies button to navigate to the role-centric Define Policies page, which displays a list of the custom objects for your CRM implementation. Use this page to manage access for users with the corresponding role by specifying a security policy for one or more top-level or child custom objects. When you do this, users with the corresponding role can access the custom objects and related data, depending on the security policies you define.

To access the role-centric Define Policies page:

1. Select an application on the main Overview page.

2. Select the Role Security node from the Common Setup pane.

   Or, select the Role Security hyperlink in the local area of the main Overview page.

   Or, from the object-centric Define Policies page, select a role.

   
   
   

3. Click the Define Policies button.

   
   
   

From the role-centric Define Policies page, you can:

• Enable function security for a custom object.

• Enable data security for a custom object.

• Allow users to grant access to a specific record at run time, to users with a given role.

• View related roles, if any.

  If a related role is displayed next to an object, then the selected role is inheriting its access to that object from the related role. You can drill down into the related role to view its security policies.

Enabling Function Security and Data Security

A security policy specifies the type of access to an object and its records that users with the corresponding roles have. Access includes both function security as well as data security. Security settings are the same whether you are defining a security policy for an object or a role.

On the Define Policies page, the first four columns in the table manage function security, which applies to the object as a whole:

• Create

  Users with the corresponding role can create a record of the object.

• View

  Users with the corresponding role can view the object's work area pages.

• Update

  Users with the corresponding role can update a record of the object.

• Delete

  Users with the corresponding role can delete a record of the object.

The next two columns in the table manage data security.

• View All

  Users with the corresponding role can view the object's records.

• Update All

  Users with the corresponding role can update the object's records.

The last column contains the Grant Access check box. Selecting this check box controls the display of the Manage Permission button on the object's summary table at run time. At run time, users with the corresponding role (or an administrative role) can select an object record and click that button to specify the level of access another user should have to the selected record.

Application Composer and the Oracle Authorization Policy Manager (APM)

Across Oracle Fusion applications, Oracle Authorization Policy Manager (APM) manages the security policies that control access based on roles. However, you define the security policies for custom objects in the Application Composer's object-centric and role-centric Define Policies pages. This is outside APM.

Since you define the security policies outside APM, you cannot later modify the security policies within APM. Instead, modify all security policies for custom objects using only the Application Composer.

Default Security Settings

By default, top-level custom objects are visible and editable only to users with a default duty role specified by a CRM application. You must manually grant additional access to other duty roles, if desired. For example, if you create a custom object in Oracle Fusion Sales, then only users with the default duty role specified by Sales are automatically granted access to that object. This lets you first access an object and its pages for testing, before you officially grant access to your customizations to users in a production environment.

This table lists the default duty roles that are provided by CRM applications:

Child objects do not inherit security settings from parent objects. Rather, if you create a custom child object, then a default set of duty roles are granted access to the child object. In other words, a child object is visible and editable only to users with these default duty roles, as follows:

Importing and Exporting Custom Objects : Explained

What''s the difference between Page Composer and Application Composer?

Page Composer is an Oracle Fusion tool you can use to modify Oracle Fusion user interface (UI) pages and components for all products designated for use with Page Composer. Page Composer uses two different modes of Design View. The first mode, Design View: Standard mode, is selected by default in all CRM pages when opening a page with Page Composer with the Design button selected. The second mode, Design View: Direct Selection mode, is activated when you click the Select tab for the UI page you want to customize. In CRM, Direct Selection mode is available when you customize pages, but not when you personalize a dashboard page. With the Design View: Direct Selection mode, you can select and edit UI elements such as form fields and table columns. In Direct Selection mode, selectable UI components become apparent when you move your cursor over the UI component. Selectable UI components are highlighted and can be edited.

The following table describes how you can use each mode of Page Composer to customize dashboard pages and other select pages (such as the Partner Public Profile page, Partner Landing page, Partner Registration, Customer Snapshot, and Customer Overview - Analysis tab), and customize transactional pages (all other non-dashboard pages).

Use Cases	Design View - Standard mode	Design View - Direct Selection mode	Page Type
Add content (Business Intelligence reports, CRM portlets such as Calendar)	Yes	No	Dashboard and other select pages
Delete region	Yes	No	Dashboard and other select pages
Move region	Yes	No	Dashboard and other select pages
Change page layout (for example, change a two column layout to three column layout)	Yes	No	Dashboard and other select pages
Default region state (open or close)	Yes	No	Transactional pages (all non-dashboard pages)
Manage save queries (create and edit)	Yes	No	Transactional pages (all non-dashboard pages)
Hide or show field	No	Yes	Transactional pages (all non-dashboard pages)
Change field label	No	Yes	Transactional pages (all non-dashboard pages)
Make field required or not	No	Yes	Transactional pages (all non-dashboard pages)
Make field read-only or updateable	No	Yes	Transactional pages (all non-dashboard pages)
Reorder fields in a Form	No	Yes	Transactional pages (all non-dashboard pages)
Reorder table columns	Yes	Yes	Transactional pages (all non-dashboard pages)
Hide or show table columns	Yes	Yes	Transactional pages (all non-dashboard pages)
Set table column width with the mouse	Yes	No	Transactional pages (all non-dashboard pages)
Set table column width and min width in percent or pixels	No	Yes	Transactional pages (all non-dashboard pages)
Make column sortable or not	No	Yes	Transactional pages (all non-dashboard pages)

The Oracle Fusion CRM Application Composer also lets you make UI changes at run time. However, the types of UI changes that you can make using the Application Composer are quite different. Specifically, your primary focus when using the Application Composer is to make actual object model changes. For example, you can create a new business object and related fields, and then create new application pages where that object and its fields are exposed to users. The ability to make these types of object model extensions is available only in Oracle Fusion CRM applications. Also, using the Application Composer, you cannot access the Resource Catalog to add new content to a page. With the Application Composer, administrators can make customizations at the site level only.

The following table describes some of the primary differences between Page Composer and the Application Composer.

Customization Task	Available in Page Composer (site, job role, external or internal level)?	Available in Application Composer (site level only)?
Make object model extensions and expose your customizations by creating or modifying work area pages	No	Yes
Reorder subtabs	No	Yes
Customize dashboard pages	Yes	No
Add content from the Resource Catalog	Yes	No
Simple field customizations (show, hide, make read only, make required)	Yes (WYSIWYG - what you see is what you get)	Yes (non-WYSIWYG)
Select the MDS layer where you want to author customizations, such as at the site layer or job role layer	Yes	No
View results of customizations immediately	Yes, in the Page Composer design interface	Yes, in the CRM application that you are customizing

Previous

Next

Copyright ©  2011-2013, Oracle and/or its affiliates. All rights reserved. Legal Notices

Home

Contents

Book List

Contact Us