Oracle Fusion Technical

Application Composer
Application Composer is a browser-based configuration tool that enables business analysts and
administrators, not just application developers, to extend their applications.

Use Application Composer to extend certain applications by creating fields, objects, and
relationships between objects.

Here are some of the changes you can make using this tool.
• Modify objects by adding new fields or create entirely new objects.
• Create foreign key-based relationships between two objects.
• Modify user interface pages by exposing your newly created fields for an object, or create an
entirely new work area for your custom objects.
• Expose object relationships on pages in the form of subtabs.
• Write application logic, such as triggers and validation rules, for an object or for use across
multiple objects.
• Implement functional and data-level security for custom objects.
• Enable custom objects for reporting by creating custom subject areas.

Application Composer
• Browser based design and run-time tool used to extend object model changes and user
interface.
• Modify objects by adding new fields, or create entirely new objects.
• Create foreign key-based relationships between two objects.
• Modify user interface pages by exposing your newly created fields for an object, or create an
entirely new work area for your custom objects.
• Expose object relationships in the form of subtabs on pages.
• Write application logic, such as triggers, validation rules, and workflows, for an
• object, or for use across multiple objects.
• Implement functional and data-level security for custom objects.
• Enable objects for custom reporting.
• Application Composer to configure Oracle's Sales and B2B Service, Supply Chain
Management, and Project Management applications.
• · Application Composer is supported for use only in English
Differences Between Using Page Composer and Application Composer

Basis of Comparison Page Composer Application Composer

Configuring the page you're Configure a UI page you're viewing You make your configurations in
viewing and see your changes reflected Application Composer. You can then
immediately on that page. test your work by navigating to the
You can use Page Composer to make appropriate page.
changes to one page at a time. For Because you use Application
example, if you make a field required Composer to configure application
on the Edit Infolets page, the field isn't objects, if you make a field required, it
automatically required on the Create affects all interfaces where that field
Infolets page. appears.

Supported interfaces Application UI • Application UI

• Mobile
• Microsoft Outlook

Creating your own fields Not supported. You can add custom fields and entirely
and application objects new objects.

Creating saved searches Create and edit saved searches for Not supported.
users. The saved searches provide
saved search criteria to speed up
common searches. You can also use
them as filters in actionable infolets.

Tailoring your Supports different levels of Supports configurations by job role or

configurations for users configurations for application pages. for all users.
with different job roles

Configuring external-facing You must use Page Composer to You must use Application Composer
partner pages configure all external-facing partner to configure only for partner pages
pages, such as the partner registration internal to your organization, such as
page and the partner portal landing the partner Overview page.
page.
Define Objects
Using Application Composer, modify an application's object model so that you can track and store
any additional data you might need.
For example, add new fields to an existing object (standard objects), or create entirely new objects
(custom objects).
Standard objects are objects that are delivered with an application and made available to
Application Composer for application changes.
Custom objects are objects that you create using Application Composer.
You can create either top-level objects (objects without a parent) or child objects (objects created
in the context of a parent).
Create Custom Object Using Application Composer
Create a custom object if you want to track data about an object that's not already delivered with
your cloud service. After you create the object, you then add custom fields and design user interface
pages where your users can enter object records. There's no fixed limit on the number of custom
objects that you can create.
▪ On the main Overview page of Application Composer, select the Custom Objects node in the
object tree, or click the icon in the local area of the main Overview page.

▪ On the resulting summary table, click the New icon, or at the top of the object tree, click the
New icon.
 ▪ Complete the primary identifying attributes for a custom object:

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

b. Plural Label
The plural label is used as the title of the object's work area. The label is also used as the search string
in the regional search, as well as in the saved search on the object's runtime overview page.

c. Record Name Label

Use the Record Name Label field to specify the display label for the object's RecordName
attribute. The RecordName attribute stores the user-entered "name" of the record. For example, if
you're creating a custom object, Book. In the Record Name Label field for this object, you would
enter something like "ISBN Number." At runtime, for each new record, your users would use
the ISBN Number field to enter the book's International Standard Book Number (ISBN), which
uniquely identifies books published internationally.
Typically, this field is the object's primary user-recognizable identifier that runtime users drill down
on, from the landing page to the detail page. For example, at runtime, your users would click any
ISBN to drill down to review details about the book, such as book title and author.
 d. Record Name Data Type
Select either Text or Automatically Generated Sequence.
For record names of Text data type, the maximum length that users can enter is 32 characters. For
record names of Automatically Generated Sequence data type, the sequence number is based on a
display format which is up to 28 characters and has at least one number token: {0}.

e. Select the Prevent duplicate values? check box to prevent users from entering records
with duplicate names.
i. If the Prevent duplicate values? check box is selected, then the Treat "ABC"
and "Abc" as distinct values check box is enabled.
Select this check box if you want the assessment for duplicate records to be case sensitive.
f. Object Name
The object name is the internal name for the object.
g. Description
▪ Click OK.

Once your custom object is created, you must add fields and then create the UI pages where your
users can create actual records.
For both standard and custom objects, you can view and edit the following details:
• Fields
Add new fields to an object.
• Pages
Modify the pages on which an object appears.
• Actions and links
Add actions or links to pages.
• Server scripts
Write application logic that controls the behavior of an object's records.

For custom objects, you can also view and edit details to security. For example, you can
implement functional and data-level security for an object and its records.

Delete a Custom Object

Application Composer doesn't support the deletion of either standard or custom objects. If you no
longer need an object that was already published to the mainline metadata, optionally enter a note
in the description that the object is no longer used.
Fields
• Use Application Composer to extend your applications by adding new fields to both standard or
custom objects.
• The fields that you add to an object are custom fields.
• When creating a custom field, Application Composer provides a set of field types that you can
choose from. For example, you can create a check box field, or create a long text field.

Custom Object Creation > Create Fields

Click the Standard Fields or Custom Fields tabs to view the standard or custom fields available for
the object.
On the Standard Fields tab:
• Review the list of standard fields that are delivered for an object, and optionally modify the
display label and help text for a field.
• The list of standard fields includes all the fields that are delivered by Oracle for an object, as well
as system fields, which could include:

▪ CreatedBy
▪ CreationDate
▪ Id
▪ LastUpdateDate
▪ LastUpdatedBy
▪ RecordName

Note:
The custom objects that you create also contain these same system fields, among others.

On the Custom Fields tab:

Review the list of custom fields that you created specifically for your implementation, and create
new custom fields.
Add Fields to Objects
Note: An object can have a maximum of 625 fields.
To create a custom field:
▪ In Application Composer, select the object that you want to make changes to, then select the
object's Fields node.
▪ On the Custom Fields tab, click Action >> Create.

Application Composer provides a set of field types that you can choose from when
creating new fields:
▪ Check box
▪ Currency
▪ Date
▪ Datetime
▪ Dynamic choice list
▪ Fixed choice list
▪ Formula
▪ Long text
▪ Number
▪ Percentage
▪ Record Type
▪ Text
▪ Select the type of field you want to create, and then specify the required field attributes to create
the custom field.

Example
Example Choice List - Fixed, Dynamic
https://www.youtube.com/watch?v=jzgqUOPyQv4
▪ After you create custom fields, you must expose those fields on the right user interface pages,
before your end users can see them.
Modify Application Pages Using Application Composer
To modify application pages using Application Composer:
▪ On the main Overview page in Application Composer, select an object and expand its
nodes.
▪ Click the Pages node and select the Application Pages tab.

Creation page
▪ Duplicate and modify page layouts for that object, as needed.

Standard objects are delivered with standard layouts. To modify a layout, duplicate the standard
layout for the following types of application pages:
• Landing page (list page)
• Creation page
 • Details page (edit page)
• Search and select dialog box

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

Details page
For more information
https://docs.oracle.com/en/cloud/saas/applications-common/24d/oacex/index.html
https://www.youtube.com/watch?v=THctLaTtlj8
REST API GET/POST Operations
https://www.youtube.com/watch?v=R3O7p2QbpXg
Custom Subject Area Creation – OTBI
https://www.youtube.com/watch?v=kStlD0yE1FM
Master Child Object & Attachment
https://www.youtube.com/watch?v=S_MEOv9K00c
Import Management
https://www.youtube.com/watch?v=bRosHR0t59s
BIP Report Using Groovy Script
https://www.youtube.com/watch?v=Rq9nusTcDvY