Oracle® Fusion Applications Sales Implementation Guide 11g Release 7 (11.1.7) Part Number E20373-08

Home

Contents

Book List

Contact Us

Previous

Next

PDF

36 Define Extensions for Sales

This chapter contains the following:

Define Custom Enterprise Scheduler Jobs

Customization and Sandboxes

FAQs for Customization and Sandboxes

Define Custom Enterprise Scheduler Jobs

Managing Job Definitions: Highlights

Oracle Enterprise Scheduler jobs are run in Oracle Fusion Applications to process data and, in some cases, to provide report output. A job definition contains the metadata that determines what the job does and what options are available to users who run the job. You can create and maintain job definitions for use in Oracle Fusion Applications.

Managing job definitions is fully described in the Oracle Fusion Applications Administrator's Guide. As you read content from that guide, note that the guide describes managing Oracle Enterprise Scheduler, including job definitions, from Oracle Enterprise Manager Fusion Applications Control. You can also access job definitions by starting in the Setup and Maintenance Overview page and searching for the Enterprise Scheduler job tasks for your applications.

Selecting the Appropriate Implementation Task

Each Enterprise Scheduler job definition task uses one Java EE application, which is referenced in the task name. You must use the right task because, to access the product job definition that you want to view or work on, the view objects must be contained in the application. If you do not select the right task, then the job definition will not be displayed properly or function correctly. The application name is usually the same as the product that the job definition belongs to, but not always.

• For example, the Oracle Fusion Payables Java EE application contains the Oracle Fusion Expenses product view objects. To create or maintain a job definition for use in Expenses, you select the Manage Custom Enterprise Scheduler Jobs for Payables and Related Applications task.
• In another example, the Oracle Fusion Payments product view objects are contained in both Oracle Fusion Payables and Oracle Fusion Receivables Java EE applications. You need to select the task appropriate to the job definition for Payments. Use the Manage Custom Enterprise Scheduler Jobs for Receivables and Related Applications task if the job is for receivables functionality, or the Manage Custom Enterprise Scheduler Jobs for Payables and Related Applications task if the job is for payables functionality.
• Use the task description to see the products that correspond to the Java EE application specified in the task name. For example, the description for the Payables task lists Oracle Fusion Payables, Assets, Expenses, and Payments.
• You can view task descriptions in the help window for the task, if any, or in the generated setup task lists and tasks report from the Getting Started page.
• If you have access to the Manage Task Lists and Tasks page, you can also open the details for specific tasks to see the description.
• For general information about product and Java EE application relationships, use Oracle Enterprise Manager Fusion Applications Control (Fusion Applications Control).
  See: Topology Section

Viewing and Creating Job Definitions

• You can access predefined and custom job definitions.
  See: Viewing Job Definitions
• You can create jobs based on Java, PL/SQL, or any other supported technology.
  See: Creating a Job Definition
• If you are using the Setup and Maintenance work area, then the Enable submission from Enterprise Manager check box is available for the job definition.
• If you do not select this check box, then the job cannot be run from Enterprise Manager.
• If you select this check box, then you can define parameters for this job definition only in Enterprise Manager. Save the rest of your work on the job definition, and then go to Enterprise Manager if you need to define parameters.

Managing List of Values Sources: Highlights

A list of values source for Oracle Enterprise Scheduler job definitions determines where a list of values comes from and what the specific values are. These lists of values are used in parameters and user properties of job definitions. For example, you can use a source of country values for a Country job parameter.

Managing list of values sources is fully described in the Oracle Fusion Applications Administrator's Guide. As you read content from that guide, note that the guide describes managing Oracle Enterprise Scheduler, including list of values sources, from Oracle Enterprise Manager Fusion Applications Control. You can also access list of values sources by starting in the Setup and Maintenance Overview page and searching for Enterprise Scheduler job tasks.

Registering and Searching for List of Values Sources

• Create list of values sources to register them for use in job definitions.
  See: Registering Sources for Lists of Values
• Search for list of values sources to edit or delete, or to make sure a particular source does not already exist before you create it.
  See: Searching for List of Value Sources

Customization and Sandboxes

Customizing Pages Using Page Composer: Highlights

You can customize dashboards and some work areas, where available, for all or some users based on a selected customization layer, for example only for users in a specific country or with a specific job role. When you select to customize a page from the Administration menu in the global area, you invoke Page Composer, which enables the customization. The Administration menu is only available if you have appropriate roles.

From the same menu, you can also:

• Customize the global area.

• Manage customizations by accessing a list of components in the current page and details about the layers in which each component is customized.

• Access sandboxes to make customizations to a runtime use session before deploying your changes to the mainline.

Customizing pages using Page Composer, managing customizations, and using sandboxes are described in the Oracle Fusion Applications Extensibility Guide. For more information on customization layers, see assets with the Customization Layer type in Oracle Enterprise Repository for Oracle Fusion Applications (http://fusionappsoer.oracle.com).

Editing Pages

• Customizations that you can make to existing pages include adding content and changing layout.
  See: Editing a Page in Page Composer
• You can also update display and other options for specific components within the page.
  See: Editing Component Properties in Page Composer

Global Page Template

• Customize the global area at the site layer.
  See: Editing the UI Shell Template Used by All Pages

Managing Customizations

• Use the Manage Customizations dialog box to analyze and diagnose customization metadata, and to perform customization related tasks that cannot be done in the user interface, for example to revert customizations to a previous version. You can also do direct customization by manipulating the metadata and uploading it back.
  See: Viewing and Diagnosing Runtime Customizations

Sandboxes

• Create or select an appropriate sandbox, and set it as active to capture your customizations using Page Composer. When you are ready, you publish the sandbox to make your changes available to users.
  See: Using the Sandbox Manager

Customizing CRM Applications Using the Application Composer: Explained

The Oracle Fusion CRM Application Composer provides a series of task flows which let you customize and extend an Oracle Fusion CRM application according to the needs of your users. For example, you can create fields for an existing standard object, and expose those new fields on the object's work area. Or, create a brand new custom object and related fields, then create a work area where that object and its fields are exposed to users. The task flows available to you are dependent upon the CRM application that you are customizing.

Available Customization Task Flows

Different sets of customization task flows are available to you, depending on the CRM application that you are customizing. See Customizing Oracle Fusion CRM Applications Using Oracle Fusion CRM Application Composer (Doc ID 1516151.1) on My Oracle Support at https://support.oracle.com. This document provides a list of which task flows are available for use in these CRM applications:

• Oracle Fusion Common CRM

  This includes Master Data Management (MDM) and Common Party User Interface (CPUI) objects.

• Oracle Fusion Customer Center

• Oracle Fusion Marketing

• Oracle Fusion Sales

• Oracle Fusion Sales Catalog

You can also refer to the product-specific implementation guides to learn more about how a particular application works with the Application Composer.

Customizing Oracle Fusion CRM Pages Using Page Composer: Explained

Page Composer is a page editor that lets you easily edit the user interface composition at run time. In Oracle Fusion CRM, Page Composer is intended for simple user interface editing functions, such as showing and hiding regions, fields, and tables, changing the order of regions, or changing a dashboard page layout. You can also use it for adding or removing predefined content from the Resource Library. All changes are done and stored in the UI layer. Oracle Fusion CRM transactional pages and dashboards are enabled for runtime customization using Page Composer. These pages and regions are delivered already enabled for page editing. Administration and setup pages are not Page Composer-enabled.

The following figure shows how Page Composer affects only the UI layer.

Page Composer Customization Modes

Page Composer supports two editing modes: Design View and Source View. In Design View mode, editing is done by direct manipulation of the target components and their properties. In the Source View mode, editing can be done from the programmatic code of the target component. In Oracle Fusion CRM, Page Composer is launched in Design View mode by default. Customizations can be done only in Design View mode. The only exception is the Partner Relationship Management's Partner Portal UI Shell customization, which is done in Source View mode.

The Page Composer Design View mode has two selection submodes. Design mode is launched by default when opening a page with Page Composer. You can also select this mode by clicking the Design tab on the top left corner of a page in Page Composer mode. Direct Selection mode is activated when you click the Select tab that is next to the Design tab.

The following figure shows a Page Composer-enabled dashboard in Design View mode and Design Selection mode.

The Direct Selection mode is mainly used to select and edit UI components, such as form fields and table columns. In Direct Selection mode, the enabled UI components become apparent when you move the cursor over the component. Enabled UI components get focus on hovering and are highlighted by a light blue border for editing. When you click the highlighted component, the border changes to dark blue and an Edit popup window appears.

The popup window allows you to select whether to edit the selected component or the parent component. Examples of parent components include tables that hold columns and forms that hold fields.

Accessing Page Composer

You access Page Composer from the Administration global menu. Access to the Administration menu is controlled through the Administration Link View Duty. The following table lists examples of duty and job roles that must be assigned to you so that you can access the Page Composer editor.

Contact your security administrator for additional details on these security privileges.

Sandbox support is also available through Page Composer. The sandbox provides temporary storage for your customization changes until you are ready to commit them to the back end. Before working with sandboxes, review the guidelines and recommendations on using sandboxes, available in related help topics.

To launch Page Composer:

1. Navigate to the Page Composer-enabled page.

2. Before making changes using Page Composer, confirm that you are working in the desired sandbox. If not, create a sandbox before making your changes.

3. Select the Administration global menu.

4. On the Customize <page name> Pages popup dialog, select the MDS layer that you want to customize.

5. Click OK.

6. Click Customize <page name>.

7. Select Customize Work Areas for dashboard customization.

   Page Composer is now launched.

8. Customize the page.

9. When you are done, click the Close button in the header to leave the Page Composer editor.

Available Customization Options

In Oracle Fusion CRM, you can use the following customization options:

• Transactional, landing, and dashboard page customizations. Only administrators can do these customizations.

• Partner Portal UI shell and branding customizations. Only Partner Portal administrators can do these customizations.

• User-level page personalization for limited personalization tasks, such as hiding or adding content. Personalization changes are only visible to the user who is doing them.

Additionally, you can do Page Composer customizations in any of these MDS customization layers:

• Site: Your customizations are visible to all site users.

• Job Role: Your customizations are visible to users who have the selected job role.

• External or Internal: Depending on your selection, your customizations are visible to either external or internal users. External users could be your partners or anonymous users. Internal users could be your employees.

When Page Composer is launched, the Customize <page name> Pages dialog opens, where you can select the MDS layer to customize. The layer that is selected in the Edit column is the layer that you want to edit. The layers that are selected in the Include column inherit any changes you make to the layer you edit.

By default, changes made at higher levels (Site) are propagated to lower level layers (External or Internal and Job Role), unless you uncheck these layers in the Include column.

The following figure shows selecting the MDS layer for customization.

Available Customization Tasks

Design and Direct Selection modes support different sets of customization tasks (although in some instances a task can be performed in either mode). The Design mode is intended for overall UI composition customizations, such as adding content, changing the dashboard layout, and changing region properties. The Direct Selection mode is intended for customizations at the component rather than the region level, mainly for fields, forms, tables, and tree nodes customizations.

All Oracle Fusion CRM dashboard pages support the design mode of the Page Composer-enabled regions. External facing landing and transactional pages that are expected to need customizations also support the design mode for Page Composer-enabled regions:

• Partner Snapshot

• Edit Partner Profile

• Edit Partner Public Profile

• Edit Personal Profile

• Partner Landing

• Partner Registration Landing

• Partner Registration: Partner Information

• Partner Registration: Review and Accept Terms

• Partner Registration Information

In general, the following customizations are meant to be done using Direct Selection mode:

• Fields (input text fields, output fields, list of values fields):

  • Show or hide component

  • Make read-only

  • Make required

  • Edit label

• UI Containers (forms, tables and trees):

  • Show or hide child components (for example, fields in the form)

  • Reorder child components (for example, reorder fields in a form)

The following table lists the customization tasks available through Page Composer and the modes in which they are supported.

Customizing the Oracle Fusion CRM Welcome Dashboard

Also known as the Oracle Fusion CRM Home page, the Welcome dashboard is the application suite's default starting page. It is composed of a collection of tabs that are visible based on the roles assigned to users. The Welcome dashboard provides a collection of high-level data summaries meant for quick monitoring and navigation to key business objects. You can customize this page.

To customize the Welcome dashboard:

1. Navigate to the dashboard.

2. Click the Administration global menu.

3. Select the Customize Workarea Pages... menu item.

The Welcome dashboard consists of a local area only. The supported customization tasks, which you do in Design mode, are:

• Change local area layout.

• Add or remove panel boxes.

• Add seeded content to dashboard panel boxes.

• Edit dashboard panel box properties: show or hide a box, reorder child regions, change display options and style.

• Add, edit, and remove ADF components to or from dashboards, such as regions, hyperlinks, images, text boxes, movable boxes, and Web pages.

Customizing Oracle Fusion Customer Center Pages: Explained

You can customize a variety of pages and regions in Oracle Fusion Customer Center using the Oracle Fusion CRM Application Composer. The Application Composer lets you create custom fields and objects, which you then add for display in the run time Customer Center application. To access the Application Composer, select Application Composer from the Navigator menu, under the Tools category.

Customizing Oracle Fusion Customer Center Pages Using the Application Composer

In general, every top-level CRM object has a work area, which includes an overview page, a creation page, and a details page. When you make changes to the object, those changes can be reflected in the object's associated work area. Customer Center, however, is unique in that its user interface pages do not include the traditional work area combination of overview page, creation page, and details page. Instead, Customer Center has a series of tree nodes that, when selected, display user interface pages, and even a single page can be associated with multiple business objects.

This table lists Customer Center pages, and the related objects that you can access in the Application Composer to customize those pages.

Oracle Fusion Common CRM Objects

The Oracle Fusion Common CRM objects that are associated with Customer Center pages are:

• Trading Community Org Profile

• Trading Community Person Profile

• Trading Community Address

• Trading Community Org Contact

This table indicates which Common objects populate which Customer Center pages and regions, as well as the Application Composer configuration pages where you can make user interface changes on those pages and regions.

Oracle Fusion Customer Center Objects

The Oracle Fusion Customer Center objects that are associated with Customer Center pages are:

• Sales Account

  • Sales Account Resource (child of the Sales Account)

This table indicates which Customer Center objects populate which Customer Center pages and regions, as well as the Application Composer configuration pages where you can make user interface changes on those pages and regions.

Using the Pages Overview Page

To add custom fields to the Customer Center pages listed in the tables above, use the Application Composer's various configuration pages. You access the configuration pages in the Application Composer from each object's Pages Overview page. Before you access the configuration pages, you must have already created your custom fields using the Application Composer.

To access the Pages Overview page:

1. Select either the Common or Customer Center application on the main Overview page.

2. In the object tree, select the object you want to customize.

3. Select the Pages node.

4. On the Pages Overview page, select the configuration page hyperlink related to the Customer Center page that you want to customize.

Adding Custom Reports Using Page Composer

The customizations that you can make in Customer Center also include the creation of reports. This type of customization does not involve the creation of fields or objects within the Application Composer. Instead, create a report using BI Answers, save the report to the Resource Catalog, and then use Page Composer to add the report to two pages: the Customer Snapshot and the Customer Overview, Analysis tab.

Customizing Oracle Fusion Sales Forecasting Pages: Explained

You can customize a variety of regions in Oracle Fusion Sales Forecasting using the Oracle Fusion CRM Application Composer. The Application Composer lets you create custom fields and objects, which you then add for display in the runtime Sales Forecasting application. To access the Application Composer, select Application Composer from the Navigator menu, under the Tools category.

Understanding Which Oracle Fusion Sales Forecasting Pages Are Extensible

To customize Sales Forecasting pages, you need to know which pages and regions are extensible, and which objects to select in the Application Composer to customize those pages.

The Oracle Fusion Sales objects that are associated with Sales Forecasting pages are:

• Forecast Item

• Forecast Territory Details

This table lists Sales Forecasting pages and regions, and the related objects that you can access in the Application Composer to customize those pages. For example, the Forecast Items tab on the Edit Forecast page is extensible. To create custom fields that you can later add to the Forecast Items tab, you must select the Forecast Item object in the Application Composer and create your custom fields.

Next, expose those custom fields on the Forecast Items tab by accessing the appropriate Application Composer configuration page, listed in the following section.

Adding Your Changes to the Runtime Application

To add custom fields to the Sales Forecasting regions listed in the table above, first create your custom fields using the Application Composer. Next, use the Application Composer's configuration pages to add those custom fields to the desired Sales Forecasting regions. You access the configuration pages in the Application Composer from the Pages node under the Forecast Territory Details object.

To access the Pages Overview page:

1. Select the Sales application on the main Overview page.

2. In the object tree, select the Forecast Territory Details object.

3. Select the Pages node.

   
   
   

4. On the Pages Overview page, select the configuration page hyperlink related to the Sales Forecasting region that you want to customize.

This table indicates which Sales objects populate which Sales Forecasting pages and regions, as well as the Application Composer configuration pages where you can make user interface changes on those pages and regions.

Customizing Partner Management Dashboard and Pages Using Page Composer: Explained

Oracle Fusion Partner Management (PRM) consists of external facing pages (for partner users), and internal facing pages for employee users. Several external facing pages need to be customizable to allow brand owners to tailor the presentation and content to the specific needs of the external user.

In PRM, you can customiorze any of the following pages using Page Composer:

• External pages

  • Partner Dashboard

  • Edit Partner Profile

  • Edit Partner Public Profile

  • Edit Personal Profile

  • Partner Landing

  • Partner Registration Landing

  • Partner Registration: Partner Information

  • Partner Registration: Review and Accept Terms

  • Partner Registration Confirmation

• Internal Pages

  • Channel Dashboard

  • Partner Snapshot

  • Edit Partner Profile

  • Edit Partner Public Profile

Customizing External Facing PRM Pages

To customize the eligible external facing pages, you must have the Channel Partner Portal Administrator privileges.

To access the Partner dashboard:

1. Navigate to the dashboard page.

2. From the Administration menu at the top of the page, click Customize Workarea Pages....

These are the available customization tasks, which you can do at the Site, External or Internal, and Job Role layers, in either Design and Direct Selection customization modes:

• Change the local area layout. For example, change a two-column layout to a three-column layout (eight layouts are available).

• Add, rename, or remove Partner dashboard subtabs (except the predefined tabs labeled Partner Administrator and Partner Sales Representative).

• Expand or collapse the dashboard Regional pane (by moving the page splitter location).

• Add or remove panel boxes to or from the dashboard local area.

• Add Resource Library content to dashboard panels.

• Edit dashboard panel box properties: show or hide box, reorder child regions, change display and style options.

• Add or remove ADF components to or from dashboards (for example, regions, hyperlinks, images, text boxes, movable boxes, and Web pages) and edit their properties.

To customize the remaining external partner pages (Edit Partner Profile, Edit Partner Public Profile, Edit Personal Profile, Partner Landing, and Partner Registration Landing):

1. Navigate to the Partner dashboard.

2. From the Administration menu at the top of the page, click Customize Workarea Pages... to launch Page Composer.

To customize the partner registration pages (Partner Registration Landing, Partner Registration: Partner Information, Partner Registration: Review and Accept Terms, and Partner Registration Confirmation):

1. Click the View Partner Portal Registration link in the Partner dashboard. The Partner Registration Landing Page displays.

2. Click the Register Your Company as a New Partner link to access the partner registration pages.

These are the available customization tasks, which you can do at the Site, External or Internal, and Job Role layers, in either Design and Direct Selection customization modes.

• Change local area layout (except for Edit Partner Profile and Edit Personal Profile pages).

• Add, rename, or remove Partner dashboard subtabs (except for the seeded tabs for Partner Administrator and Partner Sales Representative job roles).

• Expand or collapse the dashboard Regional pane (by moving the page splitter location).

• Add or remove panel boxes to or from the dashboard local area.

• Add predefined content to the dashboard panel.

• Edit dashboard panel box properties: show or hide box, reorder child regions, change display options, and style.

• Add, edit, or remove ADF components to or from dashboards, such as regions, hyperlinks, images, text boxes, movable boxes, and Web pages.

Customizing Internal Facing PRM Pages

To customize the Channel dashboard or any of the eligible internal facing pages, you must have the Channel Partner Portal Administrator or the Channel Administrator privileges.

To customize the Channel dashboard:

1. Navigate to the dashboard page.

2. From the Administration menu at the top of the page, click Customize Workarea Pages....

These are the available customization tasks, which you can do at the Site, External or Internal, and Job Role layers, in either Design and Direct Selection customization modes:

• Change the local area layout. For example, change a two-column layout to a three-column layout (eight layouts are available).

• Add, rename, or remove Channel dashboard subtabs (except the seeded Channel Manager tab).

• Expand or collapse the dashboard Regional pane (by moving the page splitter location).

• Add or remove panel boxes to or from the dashboard local area.

• Add seeded content to dashboard panels.

• Edit dashboard panel box properties: show or hide box, reorder child regions, change display and style options.

• Add, edit, or remove ADF components to or from dashboards (for example, regions, hyperlinks, images, text boxes, movable boxes, and Web pages).

To customize the Edit Partner Profile, Partner Snapshot, and Edit Partner Public Profile pages, you must have either the Channel Partner Portal Administrator or the Channel Administrator privileges.

To access the Edit Partner Profile page:

1. Navigate to the Channel dashboard.

2. Select the Review Partners link.

From the Edit Partner Profile page, you can access the Partner Snapshot and the Edit Partner Public Profile pages. You can launch Page Composer in any of these pages by selecting Customize Workarea Pages... from the Administration menu.

These are the available customization tasks, which you can do at the Site, External or Internal, and Job Role layers, in either Design and Direct Selection customization modes:

• Change the local area layout. For example, change a two column layout to three column layout (eight layouts are available).

• Add, rename, or remove the Channel dashboard subtabs (except for the seeded tab for the Channel Manager job role).

• Expand or collapse the dashboard Regional pane (by moving the splitter location).

• Add or remove panel boxes to or from the dashboard local area.

• Add Resource Library content to dashboard panels.

• Edit dashboard panel box properties: show or hide box, reorder child regions, change display and style options.

• Add, edit, or remove ADF components to or from dashboards, such as regions, hyperlinks, images, text boxes, movable boxes, and Web pages.

Customizing the Partner Portal UI Shell

This is a customization workflow that allows a brand owner to customize the standard Oracle Fusion user interface shell for the application's external facing pages. Changes are made at the Internal/External MDS layer by selecting the External option.

To access and execute this flow, you must be assigned the Channel Partner Portal Administrator job role, which has the Partner Portal Customize Links Duty role. After logging in, the administrator can customize the user interface shell by clicking the Update Partner Portal UI Shell link in the regional task list.

This customization task requires the use of Page Composer's Source View, which is enabled only for this task in Oracle Fusion CRM.

For more information on Source View, see "Introducing Design View and Source View" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Spaces on Oracle Technology Network at http://www.oracle.com/technetwork/indexes/documentation.

User interface shell and branding customization supported tasks are:

• Modify the user interface shell header (for example, add new content, hide or show global hyperlinks, and hide, show, or add menu items).

• Modify the user interface shell footer (for example, add, edit, or hide links).

• Replace the branding logo.

• Replace the branding text.

• Change the menu rendering: you can use either the Oracle Fusion Navigator or a tabbed-style menu.

Creating a Sales Lead Validation Rule Using Application Composer: Worked Example

Lead management users can change the status of a lead to Qualified, regardless of whether the lead customer is a sales account or has a primary product associated with the lead. However, to enforce compliance with your company's lead management business processes, you might want to create business rules to control when a lead's status can actually be changed to Qualified.

To do this, use the Oracle Fusion CRM Application Composer to create validation rules to enforce certain criteria before allowing a sales lead status to be changed to Qualified.

In this example, you will use the Application Composer to create a validation rule that ensures a primary product and sell-to address exist, before a lead's status can be changed to Qualified.

Create a validation rule for Sell-to Address

1. Go to Navigator, Application Composer.
2. From the Application field, select Marketing.
3. From the Objects View, select Standard Objects, Sales Lead, Server Scripts.
4. Click the Object Functions tab, and then click the Add a New Object Function icon to go to the Create Object Function screen.
5. In the Function Name field, enter the following name without spaces: isSellToExists In the Returns field, select Boolean.
6. In the Function Body area enter the following: if(null != CustomerId){ def partySites = newView('Address'); def criteria = partySites.createViewCriteria(); def criteriaRow = criteria.createRow(); criteria.insertRow(criteriaRow); def criteriaItem = criteriaRow.ensureCriteriaItem('PartyId'); criteriaItem.setValue(CustomerId) partySites.appendViewCriteria(criteria) partySites.executeQuery(); while(partySites?.hasNext()) { def partySite = partySites.next(); def partySiteUses = partySite?.getAttribute('PartySiteUse'); while (partySiteUses?.hasNext()) { def partySiteUse = partySiteUses.next(); if ('SELL_TO' == partySiteUse?.getAttribute('SiteUseType')) { return true; } } } } return false;
7. Click Validate.
8. Click Save and Close.

Create a rule for enforcing the Primary Product association for the sales lead

Next, you want to create a rule for enforcing the primary product association for the sales lead as follows:

1. Click the Add a New Object Function icon to go to the Create Object Function screen.
2. In the Function Name field, enter the following name without spaces: isPrimaryProductAssigned. In the Returns field, select Boolean.
3. In the Function Body area enter the following: if((null != PrimaryInventoryOrgId && null != PrimaryInventoryItemId) || null != PrimaryProductGroupId) return true; else return false;
4. Click Validate.
5. Click Save and Close to return to theServer Scripts Sales Lead screen.

Create a validation rule to check for Lead qualification

1. Click the Validation Rules tab and from the Object Rules area, click the Add a new validation rule icon.
2. In the Create Object Validation Rule screen, go to the Rule Name field and enter the following rule name without spaces: qualifyLead
3. In the rule definition area , enter the following: if(isAttributeChanged('StatusCode') && getAttribute('StatusCode') == 'QUALIFIED') return (isPrimaryProductAssigned() && isSellToExists()); else return true;
4. Go to the Error Message section and enter the following message text: Primary Product and Sell to Address are required for qualifying a Lead.
5. Click Save and Close to complete the task of using the Application Composer to create validation rules for the primary product and sell-to address fields when setting the lead to qualified.

Test the rule

1. Go to Navigator, Lead Qualification, Edit Lead page.
2. From the Actions menu, select Qualify.

   If the Primary Product andSell to Address fields contain no data, you should receive the following error message text:

   Primary Product and Sell to Address are required for qualifying a Lead.

FAQs for Customization and Sandboxes

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.

This 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):

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 Application Composer, administrators can make customizations at the site level only.

This table describes some of the primary differences between Page Composer and the Application Composer:

Previous

Next

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

Home

Contents

Book List

Contact Us