Oracle® Fusion Applications Extensibility Guide for Developers 11g Release 7 (11.1.7) Part Number E41852-03 |
|
|
PDF · Mobi · ePub |
This chapter provides an overview of how to customize and extend on-premises installations of Oracle Fusion Applications and introduces the design time and runtime tools that are used in the process. The remainder of this book describes how to use the following tools to customize and extend on-premises installations at design time:
Oracle JDeveloper
Oracle Business Process Management Worklist (Oracle BPM Worklist)
Oracle SOA Composer
Oracle Enterprise Manager Fusion Applications Control (Fusion Applications Control)
Oracle Application Development Framework (Oracle ADF) Skin Editor
This chapter includes the following sections:
While Oracle Fusion applications provide robust out-of-the-box functionality, there may be areas of one of the applications that you must change to meet your business needs. On-premises installations of Oracle Fusion Applications provide runtime and design time tools to customize and extend Oracle Fusion applications. This book gives an overview of both the runtime and design time tools, and then guides you through the process of using the design time tools that are available for on-premises installations. For further information about using runtime tools, see the Oracle Fusion Applications CRM Extensibility Guide, the Oracle Fusion Applications Common Implementation Guide, and the Oracle Fusion Applications Extensibility Guide for Business Analysts.
Most customizations made to an Oracle Fusion application, whether a personalization an end user makes, a change a business user makes using a runtime composer tool, or a change a developer makes using JDeveloper to create new source code, are stored in a metadata repository. Because these customizations are kept separate from the base code, you can safely upgrade your Oracle Fusion application without losing your changes.
Customizations made at runtime can be saved in a sandbox so that the changes can be isolated and validated before being published into a full test environment. Changes done at design time are done in a development environment, and can also be deployed to a sandbox before being deployed into the full test environment.
The Manage Customizations dialog enables you to identify and examine where customizations have been made and for which layer, even when a page consists of several different components (some of them actually being another page). You can also use the Manage Customizations dialog to import customizations that others have done, or you can export your own customizations.
For more information about using the Manage Customizations dialog and sandboxes, see Chapter 2, "Understanding the Customization Development Lifecycle."
Note:
You can also create a complete Java EE application to supplement your Oracle Fusion applications. See the Oracle Fusion Applications Developer's Guide for more information.
All Oracle Fusion applications are based on Oracle Fusion Middleware. Most user interfaces are implemented using Oracle Application Development Framework (Oracle ADF) and standard Java technologies, such as the JavaServer Faces technology. The foundation of the applications are the service-oriented architecture (SOA) business processes. Business intelligence frameworks provide several reporting capabilities. Identity management works at every level to control access. Each of these areas of an application can be customized and extended to suit your business needs.
Additionally, Oracle Fusion applications are built using a common data model. Because of this commonality, when you make a customization in one area, that customization will be available to all objects in the application. For example, if you add an attribute to an object, you can easily add that attribute to the web-based view page, to an associated mobile page, and to any associated reports.
Within this guide, the term customize means to change a standard (existing) artifact. For example, you can add an attribute to an existing object or you can change what is displayed on a standard page. The term extend means to create a completely new artifact, such as a custom object.
For customizations and extensions, there are three basic scenarios:
Personalization
Runtime customizations and extensions
Design time customizations and extensions
The term personalization refers to the changes that every end user of the Oracle Fusion Applications product suite can make to certain artifacts in the user interface (UI) at runtime. These changes remain for that user each time that user logs in to the application. Personalization includes changes based on user behavior (such as changing the width of a column in a table), changes the user elects to save, such as search parameters, or composer-based personalizations, where an end user can redesign aspects of a page.
For composer-based personalizations, Oracle Fusion Applications includes Page Composer, which allows end users to change certain UI pages to suit their needs. For example, they can rearrange certain objects on a page, add and remove designated content, and save queries. Figure 1-1 shows the Partner Profile page in Page Composer. An end user can add other content to this page, or change the order of the current content.
Note:
By default, only certain personalizations are allowed. You can customize what can be personalized. For more information, see Chapter 10, "Configuring End-User Personalization."
Runtime customizations and extensions include those that a business analyst can make to an Oracle Fusion application at runtime using browser-based composers. These customizations and extensions are visible and usable by all or by a subset of Oracle Fusion Applications users. The types of runtime customizations and extensions range from changing the look and feel of a page, to customizing standard objects, adding a new object and associated pages and application functionality, changing workflows, defining security for new objects, and customizing reports. Figure 1-2 shows how you can customize the fields on a standard object using Application Composer, which is a runtime tool used to customize and extend certain Oracle Fusion Customer Relationship Management (Oracle Fusion CRM) applications.
For information about customizing and extending Oracle Fusion applications using runtime tools, see the Oracle Fusion Applications CRM Extensibility Guide, the Oracle Fusion Applications Common Implementation Guide, and the Oracle Fusion Applications Extensibility Guide for Business Analysts.
Design time customizations and extensions include more complex changes, such as creating a SOA composite application or creating a new batch job, and they require deployment into a runtime environment. These design time customizations and extensions are most often done by Java developers using Oracle JDeveloper (a comprehensive integrated development environment), as shown in Figure 1-3, or they may be done in other tools, such as Oracle SOA Composer. The customizations are then uploaded or deployed to a running instance of Oracle Fusion Applications. Developer-level extensions are covered in this book.
Oracle Fusion applications contain built-in customization layers that allow you to make customizations that affect only certain instances of an application. For example, the Sales application has a layer for job role. When you customize an artifact, you can choose to make that customization available only to users of a specific job role, for example, a sales representative.
Customizations you make are not saved to the base standard artifact. Instead, they are saved to an Extensible Markup Language (XML) file that is stored in an Oracle Metadata Services (MDS) repository. This XML file acts like a list of instructions that determines how the artifact looks or behaves in the application, based on the layer that is controlling the current context. The customization engine in MDS manages this process.
For example, say you want to customize the Sales home page by removing the Quick Create panel, but only for users with the Sales Representative role. Before you make your customization, you first select the layer in which to make your customization, in this case the role layer whose value is Sales Representative
. When you make your customization by removing that pane from the page, an XML file is generated with the instructions to remove the pane, but only in the role layer, and only when the value is Sales Representative
. The original page file remains untouched. The customization engine in MDS then stores the XML file in an MDS repository.
Now, whenever someone logs in to the application and requests an artifact, the customization engine in MDS checks the repository for XML files that match the requested artifact and the given context, and if there is a match, it layers the instructions on top of the base artifact. In this example, whenever the Sales home page is requested (the artifact) by someone who is assigned the role of Sales Representative (the context), before the page is rendered, the customization engine in MDS pulls the corresponding XML file from the repository, layers it on top of the standard Sales home page, and removes that pane. Whenever someone who is not a Sales Representative logs in (for example, someone with the role of Sales Manager), the XML file with your changes is not layered on top, and so the Quick Create panel is displayed.
Figure 1-4 shows how the customization XML file is applied to the base document and is visible only to a sales representative.
All users of Oracle Fusion applications can personalize certain pages using the Personalization menu. Users can move elements around on a page, hide elements, and even add available elements to their page. When they do this personalization, the customization engine in MDS creates an XML file specific to that user.
For example, say User 1 (who has the role of Sales Representative) personalizes the Sales home page. There will then be an XML file stored in the repository, noting the changes that user made. When User 1 logs in, as in the previous example, the customization engine in MDS pulls the XML file with the sales representative customizations from the repository and layers it on top of the standard Sales home page. In addition, the engine pulls the XML file with the User 1personalizations, allowing the user to see the personalization changes along with the Sales Representative changes. When other Sales Representatives log in, they do not see the User 1 personalization changes, as shown in Figure 1-5.
The exact customization layers available for an application depend on that application family (see the product-specific documentation from Oracle Enterprise Repository for Oracle Fusion Applications for details). However, all Oracle Fusion applications have the following customization layers:
Global layer: When customizations are made in the global layer, they affect all users of the application. This layer's XML files are added for everyone, whenever the artifact is requested. Customizations made to ADF Business Components in JDeveloper must be made in the global layer.
Site layer: Customizations made in the site layer affect users at a particular location.
User layer: The user layer is where all personalizations are made. Users do not have to explicitly select this layer. It is automatically selected when you use the Personalization menu.
These layers are applied in a hierarchy, and the highest layer in that hierarchy in the current context is considered the tip. Within the default customization layers, the global layer is the base layer, and the user layer is the tip. If customizations are done to the same object, but in different layers, at runtime, the tip layer customizations take precedence. For example, if you customize the label for a field in the site layer using Page Composer and customize the same label in the global layer using JDeveloper, the site layer customization will be displayed at runtime.
Because customizations are saved in these XML files, when you patch or upgrade your Oracle Fusion applications, the base artifacts can be updated without touching your changes. The base artifact is replaced, and when the application is run after the patch or upgrade, the XML files are simply layered on top of the new version. You do not need to redo your customizations.
Before you create customizations, you must select the layer to which you want your customizations to be applied. Most of the tools that you use to create your customizations provide a dialog where you can pick the layer for your customizations.
Oracle Fusion Applications provides several tools to enable you to customize and extend Oracle Fusion applications. With these tools, you can perform the following tasks:
Personalize and customize pages using Page Composer
Customize pages using Application Composer
Create and customize objects using Application Composer
Create business process flows for custom objects
Define security policies for custom objects
Add custom attributes to a business object
Customize reports and analytics
Perform design time customizations using JDeveloper
Customize and extend Oracle BPM Project Templates
Configure end-user personalization
Customize help
Customize the Oracle Fusion Applications skin
Translate custom text
For a more detailed description of the workflow you must follow when customizing and extending Oracle Fusion applications, see Chapter 2, "Understanding the Customization Development Lifecycle."
Tip:
When you extend Oracle Fusion applications, you may want those extensions to be configurable using Oracle Fusion Functional Setup Manager. For more information about creating setup flows for extensions, see the Oracle Fusion Functional Setup Manager User's Guide.
The user interfaces in Oracle Fusion applications are controlled by role-based authentication, meaning that the information presented in the UI, and what the user can do in the UI, depends on the role assigned to the currently logged-in user. For example, if you are assigned a role with an administrative privilege, when you log in to Oracle Fusion Applications, you will see an Administration menu, as shown in Figure 1-6. This menu allows you to do things such as customize a page for all users, or manage customizations.
Both personalization and customization use Page Composer to make changes to an application page. Using personalization, any user can drag and drop fields, rearrange regions, add approved external content, and save their favorite queries.
Using administration customization, you also use Page Composer to customize pages for other users. You can add fields, add validation, change defaults, rearrange regions, and add external content. Page Composer allows you to work in a WYSIWYG view, and, in some cases, Source view, as shown in Figure 1-7.
For more information about customizing pages, see the "Page Composer: Customizing Oracle Fusion CRM Applications" chapter in the Oracle Fusion Applications CRM Extensibility Guide and the "Editing a Page" chapter in the Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces.
If you want to extend or customize the Sales, Marketing, Customer Center, Trading Community Architecture (TCA), and Order Capture applications that are part of the Oracle Fusion CRM product family of Oracle Fusion Applications, you can use Application Composer to customize your pages, as described in the "Creating a Work Area: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide.
Note:
Only certain pages are available for customization. For a complete list, see the product-specific documentation from Oracle Enterprise Repository for Oracle Fusion Applications.
You access Application Composer by clicking the Application Composer link from the Navigator menu of Oracle Fusion Applications, as shown in Figure 1-8.
Application Composer allows business analysts to make more complex runtime customizations to Oracle Fusion CRM applications. In addition to customizing pages, business analysts can customize objects and all the artifacts that support them (such as fields, pages, buttons and links, security, server scripts, and saved searches), and can also extend Oracle Fusion applications by creating completely new objects and artifacts, as shown in Figure 1-9. For more information, see the "Defining Objects: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide.
When new objects are created, you often also create associated Work Area pages for those objects. You can add those pages to the navigator menu so that they can be accessed in the same way as standard objects. For more information, see the "Managing Menu Customizations: Highlights" section in the Oracle Fusion Applications Common Implementation Guide.
When you create a new object that is not a subclass of another object, you can also create a new object workflow to manage any business processes associated with it. For example, say you used Application Composer to create a marketing object and you want to create an associated approval flow. From within Application Composer, you can access Oracle Business Process Composer and create the process that defines that flow. For applications outside of Oracle Fusion CRM, you access Business Process Composer directly from the Navigator menu. For more information about using the Business Process Composer, see the "Customizing and Extending BPMN Processes" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts.
When you create a new object in Application Composer, you can define security policies for it. A security policy defines the end user's level of access to the data records of the object. For more information about creating security policies for custom Oracle Fusion CRM objects, see the "Securing Custom Objects: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide.
If you need to add an attribute to a business component in an application that is not one of the five Oracle Fusion CRM applications, you can often use flexfields. A flexfield enables you to define attributes on a business component and then apply business logic to them. For example, an airline manufacturer might require very specific attributes for their orders that are not provided by the out-of-the-box implementation of an order. Because a flexfield exists for the order business component, you can use it to create and configure the desired attribute. Flexfield configurations are stored in an MDS repository, and so are safe during patching and upgrading. You access flexfields from the Setup and Maintenance menu from the Administration menu. For more information about flexfields, see the "Flexfields: Overview" section in the Oracle Fusion Applications Common Implementation Guide.
Oracle Fusion Applications comes with a complete set of reports. You can customize these reports (for example, change the layout) to fit your particular business needs. Additionally, if you customize or create a business object, you can create a new report for that object. For more information, see the "Customizing Reports and Analytics" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts.
To customize or create business objects outside of the five Oracle Fusion CRM applications, or when required customizations cannot be made in one of the runtime composers, use JDeveloper. When you work in a JDeveloper environment, you create an application workspace that contains your changes and additions. When you create this application workspace, you do so in the Oracle Fusion Applications Developer role. Like Oracle Fusion Applications, JDeveloper uses roles to shape what you see and can do in the integrated development environment (IDE). Work done in a developer role is stored in actual projects with code that gets deployed to an environment. Use the Oracle Fusion Applications Administrator Customization role when customizing an existing standard object (as opposed to creating a new object). Work done in this role is saved to an XML file that gets deployed into an MDS repository, keeping your changes separate from the base code. For more information about how to set up your JDeveloper customization environment, see Chapter 3, "Using Oracle JDeveloper for Customizations."
Note:
You cannot create your own roles to define what you see and what you can do in JDeveloper.
Developers can use JDeveloper to create and customize view pages, business objects, task flows (reusable components that specify the control flow in an application), searches, and resource bundles. All customizations and extensions created in JDeveloper must be deployed to an environment. For more information about using JDeveloper to customize business objects and associated artifacts, see Chapter 4, "Customizing and Extending Oracle ADF Application Artifacts."
SOA composite applications are the foundation on which Oracle Fusion applications are built: they are the glue that holds all the different components together and they allow the different applications to work in a unified manner. SOA composite applications contain service components such as Business Process Execution Language (BPEL) process flows. These BPEL process flows provide communication between applications, additional human-based workflows, and business rules that determine the branching in those flows. Developers can customize existing SOA composite applications or create new ones using a mixture of JDeveloper and browser-based tools. Customized and extended SOA composite applications are all stored in MDS repositories. For more information, see Chapter 5, "Customizing and Extending SOA Components."
Some Oracle Fusion applications provide business process modeling (BPM) project templates that you can use to create BPM projects. BPM projects consist of SOA artifacts, such as business rules and human tasks, and Business Process Modeling and Notation (BPMN) processes. You can customize these project templates to suit your business needs. For more information, see Chapter 6, "Customizing and Extending Oracle BPM Project Templates."
When you create custom pages, you may want to make them personalizable, so that end users can change the page for themselves. For more information, see Chapter 10, "Configuring End-User Personalization." Also, when you make any type of customization or extension to Oracle Fusion applications, you might have to change the embedded help that appears on the screen. For more information, see Chapter 11, "Customizing Help."
You can customize the look and feel of Oracle Fusion Applications, such as change the colors or add a logo. For more information, see Chapter 12, "Customizing the Oracle Fusion Applications Skin."
Some customizations can be translated. For more information, see Chapter 9, "Translating Custom Text."
There are many scenarios for which you can customize Oracle Fusion applications. The following tables identify for each scenario the artifacts that you can customize or create in Oracle Fusion Applications, what tool you use, the type of user that can make the change, and whether the changes are stored in an MDS repository:
View page customizations: Table 1-1
Branding customizations: Table 1-2
Object customization: Table 1-3
Business process customizations: Table 1-4
Report customizations: Table 1-5
Analysis and dashboard customizations: Table 1-6
Oracle Enterprise Scheduler job customizations: Table 1-7
Security customizations: Table 1-8
Note:
Application Composer is available only if you want to make changes in the following Oracle Fusion CRM applications:
Marketing
Sales
Customer Center
Trading Community Architecture (TCA)
Order Capture
Note:
While you can customize view pages in Page Composer and Application Composer, only certain pages are configured to allow it. If the customization that you want to make is not available in Page Composer, then you must use JDeveloper to make the customization.
Table 1-1 View Page Customization Scenarios in Oracle Fusion Applications
Customization/ Extension |
Tool | Type of User | MDS? | Where to Find Information |
---|---|---|---|---|
Add, move, delete, show, or hide components on a page. |
Page Composer |
Business Analyst |
Yes |
"Building Pages" chapter in the Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces |
Change a page layout. |
Page Composer |
Business Analyst |
Yes |
"Changing the Page Layout" section in the Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces |
Create a site-level search for all users. |
Page Composer |
Business Analyst |
Yes |
"Editing a Page in Page Composer" section in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Customize a page title. |
Page Composer |
Business Analyst |
Yes |
"Editing a Page in Page Composer" section in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Customize a task list menu. |
Page Composer |
Business Analyst |
Yes |
"Editing a Page in Page Composer" section in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Customize popup window content. |
Page Composer |
Business Analyst |
Yes |
"Editing a Page in Page Composer" section in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Add fields, buttons, links, to a standard page (Oracle Fusion CRM). |
Application Composer |
Business Analyst |
Yes |
"Application Composer: Using the Application Composer" chapter in the Oracle Fusion Applications CRM Extensibility Guide |
Customize attributes for a flexfield on a page. |
Page Composer |
Business Analyst |
Yes |
"Flexfields: Overview" section in the Oracle Fusion Applications Common Implementation Guide |
Customize properties for UI components on a standard page. |
Page Composer |
Business Analyst |
Yes |
"Setting Component Properties" section in the Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces |
Customize properties for UI components on a standard page (Oracle Fusion CRM). |
Application Composer |
Business Analyst |
Yes |
"Editing an Object: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide |
Make UI components on a page personalizable. |
Page Composer |
Business Analyst |
Yes |
Section 10.3, "Configuring End-User Personalization for Components" |
Customize the UI Shell template. |
JDeveloper |
Developer |
Yes |
|
Customize the UI Shell template. |
Page Composer |
Business Analyst |
Yes |
"Editing the UI Shell Template Used by All Pages" section in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Define resource bundles. |
JDeveloper |
Developer |
Yes |
|
Make a custom page personalizable (custom pages created in Application Composer are customizable by default). |
JDeveloper |
Developer |
Yes |
Section 10.2, "Allowing Pages to Be Personalized by End Users in Page Composer" |
Customize onscreen text that is displayed when the end user mouses over a button or link. |
Page Composer |
Business Analyst |
Yes |
|
Customize onscreen help text. |
JDeveloper |
Developer |
Yes |
|
Change the look and feel of the entire application. |
JDeveloper |
Developer |
No |
Chapter 12, "Customizing the Oracle Fusion Applications Skin" |
Translate custom text. |
JDeveloper |
Developer |
Yes |
Table 1-2 Branding Customization Scenarios in Oracle Fusion Applications
Customization/ Extension |
Tool | Type of User | MDS? | Where to Find Information |
---|---|---|---|---|
Customize the UI Shell template. |
JDeveloper |
Developer |
Yes |
|
Customize the UI Shell template. |
Page Composer |
Business Analyst |
Yes |
"Editing the UI Shell Template Used by All Pages" section in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Change the look and feel of the entire application. |
JDeveloper |
Developer |
No |
Chapter 12, "Customizing the Oracle Fusion Applications Skin" |
Change the logo. |
JDeveloper |
Developer |
No |
Chapter 12, "Customizing the Oracle Fusion Applications Skin" |
Customize report layouts. |
Oracle BI Publisher |
Business Analyst |
No |
"Customizing Reports and Analytics" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Table 1-3 Object Customization Scenarios in Oracle Fusion Applications
Customization/ Extension |
Tool | Type of User | MDS? | Where to Find Information |
---|---|---|---|---|
Customize business objects. |
JDeveloper |
Developer |
Yes |
|
Customize objects (Oracle Fusion CRM). |
Application Composer |
Business Analyst |
Yes |
"Editing an Object: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide |
Add an attribute to a business object using flexfields (not Oracle Fusion CRM). |
Setup and Maintenance work area |
Business Analyst |
No |
"Flexfields: Overview" section in the Oracle Fusion Applications Common Implementation Guide |
Create business objects. |
JDeveloper |
Developer |
Yes |
|
Create objects (Oracle Fusion CRM). |
Application Composer |
Business Analyst |
Yes |
"Editing an Object: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide |
Add a business object page to the navigator menu |
Setup and Maintenance work area |
Business Analyst |
No |
"Managing Menu Customizations: Highlights" section in the Oracle Fusion Applications Common Implementation Guide |
Add custom object work area pages to the navigator menu (Oracle Fusion CRM) |
Application Composer |
Business Analyst |
No |
"Managing Menu Customizations: Highlights" section in the Oracle Fusion Applications Common Implementation Guide" |
Add validation to a business object |
JDeveloper |
Developer |
Yes |
|
Add validation to an object (Oracle Fusion CRM). |
Application Composer |
Business Analyst |
Yes |
"Groovy Scripting: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide" |
Customize saved searches for a custom object (Oracle Fusion CRM). |
Application Composer |
Business Analyst |
Yes |
"Saved Searches for CRM Objects: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide" |
Create searches for an object. |
JDeveloper |
Developer |
Yes |
Section 4.9, "Customizing or Creating a Custom Search Object" |
Create saved searches for a custom object (Oracle Fusion CRM). |
Application Composer |
Business Analyst |
Yes |
"Saved Searches for CRM Objects: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide |
Customize task flows for an object. |
JDeveloper |
Developer |
Yes |
|
Create task flows for an object. |
JDeveloper |
Developer |
Yes |
|
Customize object workflows for an object (Oracle Fusion CRM). |
Application Composer |
Business Analyst |
Yes |
"Object Workflows: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide |
Create object workflows for an object (Oracle Fusion CRM). |
Application Composer |
Business Analyst |
Yes |
"Object Workflows: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide |
Table 1-4 Business Process Customization Scenarios in Oracle Fusion Applications
Customization/ Extension |
Tool | Type of User | MDS? | Where to Find Information |
---|---|---|---|---|
Create a BPMN process in a BPM project. |
Business Process Composer |
Business Analyst |
Yes |
"Customizing and Extending BPMN Processes" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Create a BPMN approval process in a BPM project (Oracle Fusion CRM). |
Application Composer |
Business Analyst |
Yes |
"Customizing and Extending BPMN Processes" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Customize custom BPM projects. |
Business Process Composer |
Business Analyst |
Yes |
"Customizing and Extending BPMN Processes" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Customize custom BPM projects (Oracle Fusion CRM). |
Application Composer |
Business Analyst |
Yes |
"Customizing and Extending BPMN Processes" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Customize BPM project templates. |
Oracle BPM Studio |
Developer |
Yes |
Chapter 6, "Customizing and Extending Oracle BPM Project Templates" |
Customize a business rule (either an approval configuration and assignment rule or a nonapproval business rule), domain value map, or composite application endpoint property. |
Oracle BPM Worklist, Oracle SOA Composer, and Fusion Applications Control |
Developer |
Yes |
|
Merge the customizations from a previous revision of a SOA composite application into a new revision. |
Opatch |
Administrator |
Yes |
|
Customize a BPEL process or a mediator component, or add additional SOA components. |
JDeveloper |
Developer |
Yes |
Section 5.4, "Extending or Customizing Custom SOA Composite Applications" |
Table 1-5 Report Customization Scenarios in Oracle Fusion Applications
Customization/ Extension |
Tool | Type of User | MDS? | Where to Find Information |
---|---|---|---|---|
Create report layout. |
Oracle BI Publisher |
Business Analyst |
No |
"Customizing Reports and Analytics" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Customize report layouts. |
Oracle BI Publisher |
Business Analyst |
No |
"Customizing Reports and Analytics" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Customize style templates. |
Oracle BI Publisher |
Business Analyst |
No |
"Customizing Reports and Analytics" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Create a report. |
Oracle BI Publisher |
Business Analyst |
No |
"Customizing Reports and Analytics" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Translate a report. |
Oracle BI Publisher |
Business Analyst |
No |
"Customizing Reports and Analytics" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Create a report subject area (Oracle Fusion CRM) |
Application Composer |
Business Analyst |
No |
"Custom Subject Areas: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide |
Table 1-6 Analysis and Dashboard Customization Scenarios in Oracle Fusion Applications
Customization/ Extension |
Tool | Type of User | MDS? | Where to Find Information |
---|---|---|---|---|
Customize analytics. |
Reports and Analytics pane |
Business Analyst |
No |
"Customizing Reports and Analytics" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Customize and extend the Oracle BI repository (RPD file). |
JDeveloper, Oracle BI Administration Tool |
Developer |
No |
"Customizing Reports and Analytics" chapter in the Oracle Fusion Applications Extensibility Guide for Business Analysts |
Table 1-7 Oracle Enterprise Scheduler Job Customization Scenarios in Oracle Fusion Applications
Customization/ Extension |
Tool | Type of User | MDS? | Where to Find Information |
---|---|---|---|---|
Create jobs. |
JDeveloper |
Developer |
No |
Chapter 7, "Customizing and Extending Oracle Enterprise Scheduler Jobs" |
Customize jobs. |
Fusion Applications Control |
Administrator |
No |
Chapter 7, "Customizing and Extending Oracle Enterprise Scheduler Jobs" |
Submit jobs. |
Fusion Applications Control |
Administrator |
No |
Chapter 7, "Customizing and Extending Oracle Enterprise Scheduler Jobs" |
Submit jobs. |
JDeveloper |
Developer |
No |
Chapter 7, "Customizing and Extending Oracle Enterprise Scheduler Jobs" |
Table 1-8 Security Customization Scenarios in Oracle Fusion Applications
Customization/ Extension |
Tool | Type of User | MDS? | Where to Find Information |
---|---|---|---|---|
Add data security to a custom object. |
Manage Data Security task accessible from the Setup and Maintenance work area |
Developer |
No |
Section 8.4, "Defining Data Security Policies on Custom Business Objects" |
Opt into data security policies for custom objects. |
JDeveloper |
Developer |
No |
Section 8.5, "Enforcing Data Security in the Data Model Project" |
Grant access to application artifacts. |
JDeveloper |
Developer |
No |
Section 8.6, "Defining Function Security Policies for the User Interface Project" |
Grant access to custom objects (Oracle Fusion CRM). |
Application Composer |
Business Analyst |
No |
"Securing Custom Objects: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide |
Enable elevated privileges customization. |
Application Composer |
Business Analyst |
No |
"Securing Custom Objects: Explained" section in the Oracle Fusion Applications CRM Extensibility Guide |
All the business analyst tools are available from the navigator menu of Oracle Fusion Applications. However, for most of the design time tools, you must install and configure a version of JDeveloper that is certified for your Oracle Fusion Applications release. This version of JDeveloper, along with the necessary extensions for customizing and extending Oracle Fusion Applications, is in the release's Oracle Fusion Applications Media Pack, which is available from Oracle Software Delivery Cloud at http://edelivery.oracle.com
. After installing JDeveloper, they must set up their environment for customization and extending.
For procedures for installing JDeveloper and setting it up for extending (that is, for creating new objects), see the "Setting Up Your Development Environment" and "Setting Up Your JDeveloper Application Workspace and Projects" chapters in the Oracle Fusion Applications Developer's Guide.
For procedures for setting up JDeveloper for customizations, see Chapter 3, "Using Oracle JDeveloper for Customizations."