About Application Composer

Application Composer is a browser-based configuration tool that enables business analysts and administrators, not just application developers, to extend their applications. Make the type of data model changes which, in the past, could only be made by application developers.

For example, easily create a new object and related fields, then create new user interface pages where that object and its fields are exposed to users.

Application Composer is a design time at runtime tool, which means that you can navigate to Application Composer directly from any application, make your changes, and see most changes take immediate effect in real time, without having to sign out and sign back in. (For end users to see your changes, however, you must first publish your sandbox and then they must sign out and sign back in. Read more about sandboxes later in this topic.)

Note: To see your changes in real time, always use the Navigator to navigate to the runtime page that you changed. Then navigate back to Application Composer to continue making changes. In other words, when making application changes (and testing them), restrict your usage to a single tab. Don't work across multiple browser tabs, because Application Composer doesn't support this type of usage.

You can use Application Composer to configure Oracle's Sales and Fusion Service, Supply Chain Management, and Project Management applications.

Application Composer isn't supported for use with iPad devices.

Application Changes for Nondevelopers

Application Composer hides the complexity of modifying applications by leveraging a set of standard design patterns and wizards. You focus on the application changes that your business requires (object model extensions and layout changes, for example), and Application Composer creates the underlying object artifacts for you.

Using Application Composer, you can make application changes such as the following:

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.

Working in a Sandbox

To make most application changes, you should work in a sandbox. In fact, many functions in Application Composer aren't available until you enter into an active sandbox. You use sandboxes to make application changes and test them without impacting other users in the environment. Wherever possible, make changes to the application in a sandbox rather than making direct changes in the mainline environment.

Sandboxes set apart untested configuration changes from the mainline environment. This lets you test your changes in a sandbox first, before publishing it. After publishing, your changes become available in the mainline metadata, or other sandboxes after they're refreshed, so that everyone can see your changes. Mainline metadata is the primary branch of metadata a sandbox is published to. Note that end users must sign out and sign back in to see the changes from a published sandbox.

Tip: As a best practice for using sandboxes in Application Composer, follow the below sequence to make your application changes:

Publish a sandbox with model-level changes, like creating an object and creating relationships for that object.
Publish a sandbox with the UI-level changes for the object, like adding layouts, subtabs, etc.

This order can minimize conflicts while publishing your sandboxes.

To learn more about sandboxes, see Overview of Sandboxes.

Accessing Application Composer

Access Application Composer at runtime by using the Navigator menu, and selecting Application Composer under the Configuration category.

The first view of Application Composer is the main Overview page, which is the entry point into all your task options.

Getting Started

From the main Overview page:

Use the object tree to select the object you want to modify. Or, click the New icon to create a new object.
Use the links in main Overview page, also known as the local area, to select a task. Or, use the links in the Common Setup pane.