Oracle® Fusion
Applications Marketing Implementation Guide 11g Release 1 (11.1.3) Part Number E20372-03 |
Contents |
Previous |
Next |
This chapter contains the following:
Define Custom Enterprise Scheduler Jobs
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.
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.
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.
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 Oracle Composer, which enables the customization. The Administration menu is only available if you have appropriate roles.
From the same menu, you can also access the Customization Manager, which displays a list of components in the current page and details about the layers in which each component is customized. You can also access sandboxes from the Administration menu, to make customizations to a runtime use session before deploying your changes to the mainline.
Customizing pages using Oracle Composer, the Customization Manager, and sandboxes are described in the Oracle Fusion Applications Extensibility Guide.
Oracle Composer lets you make user interface changes at run time, such as hide or show fields and regions, across all Oracle Fusion applications. You can also customize a page by adding new content from the Resource Catalog.
The Oracle Fusion CRM Application Composer also lets you make user interface changes at run time. However, the types of user interface changes that you can make using the CRM Application Composer are quite different. Specifically, your primary focus when using the CRM 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 CRM Application Composer, you cannot access the Resource Catalog to add new content to a page.
This table describes some of the primary differences between Oracle Composer and the CRM Application Composer:
Customization Task |
Available in Oracle Composer? |
Available in Oracle Fusion CRM Application Composer? |
---|---|---|
Make object model extensions and expose your customizations by creating or modifying work area pages |
No |
Yes |
Reorder subtabs |
Yes, on a page-by-page basis, if the page author enabled this feature. |
Yes |
Reorder tree nodes |
Yes |
No |
Customize dashboard pages |
Yes |
No |
Add content from the Resource Catalog |
Yes |
No |
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 Oracle Composer design interface |
Yes, in the CRM application that you are customizing |
Apply specific styling (such as font, color, and size) to user interface components |
Yes |
No |
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 new 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. This topic provides an overview of which CRM Application Composer task flows are available for use in each CRM application.
This topic addresses extensibility for these CRM applications:
Oracle Fusion Common CRM
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.
The creation of custom objects is not supported for the Oracle Fusion Common CRM application.
For Oracle Fusion Common CRM standard objects, you can do the following in the Application Composer:
Customization Task Flow |
Trading Community Org Contact |
Trading Community Resource Profile |
Trading Community Organization Profile |
Trading Community Address |
Activity Task |
Interaction |
Note |
---|---|---|---|---|---|---|---|
Create and expose custom fields on existing pages that are available for extensibility |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Edit display label and help text of standard fields |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Create custom currency fields |
No |
No |
No |
No |
No |
No |
No |
Index custom fields |
Yes |
Yes |
Yes |
Yes |
No |
Yes |
Yes |
Add custom buttons (Groovy script or URL) to selected pages |
No |
Yes |
No |
No |
No |
Yes |
Yes |
Add links (URL) to selected pages |
No |
Yes |
No |
No |
No |
Yes |
Yes |
Create and expose custom child objects on an object's details page |
No |
Yes |
No |
No |
Not applicable |
Not applicable |
Not applicable |
Create custom field-level and object-level validation logic (Groovy scripts) |
Yes |
Yes |
Yes |
Yes |
No |
Yes |
Yes |
Create custom logic at various object trigger points (Groovy scripts) |
Yes |
Yes |
Yes |
Yes |
No |
Yes |
Yes |
Create custom saved searches at the site level |
Yes |
Yes |
Yes |
Yes |
No |
Yes |
Yes |
Provide Mobile page support |
Yes |
No |
No |
No |
No |
No |
No |
Create custom relationships |
Yes |
Yes |
Yes |
Yes |
No |
No |
No |
Manage object workflows |
No |
Yes |
No |
No |
No |
No |
No |
Web services |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Not applicable |
Import data using file-based import |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Export data using bulk export |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Create custom subject areas |
No |
Yes |
No |
No |
No |
No |
No |
You can create custom objects for the Oracle Fusion Customer Center application.
For Oracle Fusion Customer Center's standard object, you can do the following in the Application Composer:
Customization Task Flow |
Sales Account Profile |
---|---|
Create and expose custom fields on existing pages that are available for extensibility |
Yes |
Edit display label and help text of standard fields |
Yes |
Create custom currency fields |
No |
Index custom fields |
Yes |
Add custom buttons (Groovy script or URL) to selected pages |
No |
Add links (URL) to selected pages |
No |
Create and expose custom child objects on an object's details page |
Yes |
Create custom field-level and object-level validation logic (Groovy scripts) |
Yes |
Create custom logic at various object trigger points (Groovy scripts) |
Yes |
Create custom saved searches at the site level |
No |
Provide Mobile page support |
No |
Create custom relationships |
Yes |
Manage object workflows |
Yes |
Web services |
Yes |
Import data using file-based import |
Yes |
Export data using bulk export |
Yes |
Create custom subject areas |
Yes |
You can create custom objects for the Oracle Fusion Marketing application.
For Oracle Fusion Marketing standard objects, you can do the following in the Application Composer:
Customization Task Flow |
Sales Lead |
Marketing Campaign |
Marketing Budget |
Marketing Response |
Marketing List |
Marketing Treatment |
Marketing Event Activity |
MarketingAdvertising Activity |
Marketing Claim |
Marketing Claim Settlement (child) |
Marketing Budget Entry |
Marketing Budget Fund Request |
---|---|---|---|---|---|---|---|---|---|---|---|---|
Create and expose custom fields on existing pages that are available for extensibility |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Edit display label and help text of standard fields |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Create custom currency fields |
No |
No |
No |
No |
No |
No |
No |
No |
No |
No |
No |
No |
Index custom fields |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Add custom buttons (Groovy script or URL) to selected pages |
Yes |
No |
Yes |
No |
No |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
Add links (URL) to selected pages |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Create and expose custom child objects on an object's details page |
Yes |
No |
Yes |
Yes |
No |
No |
No |
No |
Yes |
Not applicable |
No |
Yes |
Create custom field-level and object-level validation logic (Groovy scripts) |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Create custom logic at various object trigger points (Groovy scripts) |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Create custom saved searches at the site level |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
No |
Yes |
No |
Yes |
Yes |
Provide Mobile page support |
No |
No |
No |
No |
No |
No |
No |
No |
No |
No |
No |
No |
Create custom relationships |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
Yes |
Yes |
Manage object workflows |
Yes |
No |
Yes |
No |
No |
No |
No |
No |
Yes |
Yes |
Yes |
Yes |
Web services |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Import data using file-based import |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
Yes |
Yes |
No |
No |
No |
No |
Export data using bulk export |
Yes |
No |
Yes |
No |
No |
No |
No |
No |
No |
No |
No |
No |
Create custom subject areas |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
You can create custom objects for the Oracle Fusion Sales application.
For Oracle Fusion Sales standard objects, you can do the following in the Application Composer:
Customization Task Flow |
Opportunity |
Sales Competitor |
Partner |
Opportunity Resource (child) |
Opportunity Revenue (child) |
---|---|---|---|---|---|
Create and expose custom fields on existing pages that are available for extensibility |
Yes |
Yes |
Yes |
Yes |
Yes |
Edit display label and help text of standard fields |
Yes |
Yes |
Yes |
Yes |
Yes |
Create custom currency fields |
Yes |
No |
No |
No |
Yes |
Index custom fields |
Yes |
Yes |
Yes |
Yes |
Yes |
Add custom buttons (Groovy script or URL) to selected pages |
Yes |
Yes |
Yes |
Yes |
Yes |
Add links (URL) to selected pages |
Yes |
Yes |
Yes |
Yes |
Yes |
Create and expose custom child objects on an object's details page |
Yes |
Yes |
Yes |
Not applicable |
Not applicable |
Create custom field-level and object-level validation logic (Groovy scripts) |
Yes |
Yes |
Yes |
Yes |
Yes |
Create custom logic at various object trigger points (Groovy scripts) |
Yes |
Yes |
Yes |
Yes |
Yes |
Create custom saved searches at the site level |
Yes |
Yes |
Yes |
No |
No |
Provide Mobile page support |
Yes |
Yes |
Yes |
Yes |
Yes |
Create custom relationships |
Yes |
Yes |
Yes |
No |
No |
Manage object workflows |
Yes |
Yes |
Yes |
No |
No |
Web services |
Yes |
Yes |
Yes |
Not applicable |
Not applicable |
Import data using file-based import |
Yes |
Yes |
Yes |
Yes |
Yes |
Export data using bulk export |
Yes |
Yes |
Yes |
Yes |
Yes |
Create custom subject areas |
Yes |
Yes |
Yes |
Yes |
Yes |
The creation of custom objects is not supported for the Oracle Fusion Sales Catalog application.
For Oracle Fusion Sales Catalog's standard object, you can do the following in the Application Composer:
Customization Task Flow |
Product Group |
---|---|
Create and expose custom fields on existing pages that are available for extensibility |
Yes |
Edit display label and help text of standard fields |
Yes |
Create custom currency fields |
No |
Index custom fields |
Yes |
Add custom buttons (Groovy script or URL) to selected pages |
No |
Add links (URL) to selected pages |
No |
Create and expose custom child objects on an object's details page |
No |
Create custom field-level and object-level validation logic (Groovy scripts) |
No |
Create custom logic at various object trigger points (Groovy scripts) |
No |
Create custom saved searches at the site level |
No |
Provide Mobile page support |
No |
Create custom relationships |
No |
Manage object workflows |
No |
Web services |
No |
Import data using file-based import |
Yes |
Export data using bulk export |
Yes |
Create custom subject areas |
No |
In Oracle Fusion Customer Center, you can customize the Sales Account region on the customer profile page using Oracle Composer. To access Oracle Composer, navigate to the customer profile page and select to customize the page from the Administration menu in the global area. You can also access Oracle Composer by selecting Customization Manager from the Administration menu.
When you select to customize a page from the Administration menu in the global area, you launch Oracle Composer.
The customizations that you make to the customer profile are applied based on your layer selection:
Site
Your customizations are visible to all users.
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.
Job Role
Your customizations are visible to users who have the selected job role.
If a user has more than one job role, then the sequence in which customizations are applied is alphabetically ordered by job role name.
Oracle Composer provides two views for working with page content: Design View and Source View. Design View provides a WYSIWYG rendering of the page and its content, where controls are directly selectable on each component. Source View provides a combined WYSIWYG and hierarchical rendering of page components, where controls are available on the header of the hierarchical list. Source View provides access to page layout components that are otherwise not exposed on the page, and therefore not available in Design View.
This table lists the types of customizations available for the customer profile page. You can perform most of the basic customizations in either Design View or Source View. Some customizations, however, must be completed only in Source View.
Oracle Fusion Customer Center Page |
Customization Task |
---|---|
Customer profile |
Show and hide components on a page:
Tip You might have to scroll down to see the Show Component check box. |
Customer profile |
Move components on a page:
|
Customer profile |
Make an updateable field read only by selecting the Read Only check box on the Display Options tab in the Component Properties dialog. |
Customer profile |
Make a field required by selecting the Show Required check box on the Display Options tab in the Component Properties dialog. |
The customizations that you can make using the Oracle Composer Source View are available to you only if your assigned job role includes the Page Composer Source View Access Duty duty role. Contact your security administrator for details.
Note
Your assigned job role must also include the Administration Link View Duty duty role to access Oracle Composer at all, even if only the Design View. This duty role exposes the Administration menu in the global area.
Use a sandbox to commit customizations to a runtime use session for validation before deploying changes to the mainline. Administrators create and manage sandboxes. An active sandbox isolates changes from the mainline and other users.
Sandboxes can contain the following types of customization changes.
Metadata, such as non-flexfield UI page customizations
Data security
Generated flexfields business components
Metadata changes are captured in a metadata sandbox. Data security changes are additionally captured in a data security enabled sandbox. Changes to a flexfield are captured in a flexfield that is deployed as a single flexfield sandbox. Once you are ready to make sandbox changes available in the mainline, you either publish the metadata or data security sandbox, or deploy the flexfield. Only metadata and data security sandboxes can be downloaded as a sandbox file for import to another Oracle Fusion Applications instance.
The following table lists the differences among the types of sandboxes.
Type of Changes |
Type of Sandbox |
Method for Making Changes Available in Mainline |
Downloadable? |
---|---|---|---|
Metadata |
Sandbox |
Publish sandbox |
Yes |
Data security |
Sandbox enabled for data security changes |
Publish sandbox |
Yes |
Flexfield |
Flexfield deployed as a flexfield-enabled sandbox |
Deploy flexfield |
No |
Only one sandbox can be active at a time. Changes made while a sandbox is active are captured in that sandbox.
For more information on using the Sandbox Manager, and customizing and securing pages, business objects, data, and custom objects in a sandbox, see the Oracle Fusion Applications Extensibility Guide.
You can make metadata (MDS) type changes in a sandbox, including menu customizations, changes to the personalization menu, implicit ADF customizations, or changes made with Oracle Composer or CRM Application Composer.
You can create a sandbox for data security testing, or designate an existing sandbox to become enabled for data security testing.
You create a flexfield-enabled sandbox by deploying one flexfield to a sandbox using the Manage Flexfield task flow. The flexfield sandbox gets its name from the flexfield you deploy. You cannot test two flexfields in the same sandbox. Once you deploy a flexfield as a sandbox, you must sign out and back in to view how the sandbox runtime reflects the flexfield changes, such as new segments. You can redeploy the same flexfield to the same sandbox repeatedly as you make incremental changes to the flexfield setup.