2Before You Begin

This chapter contains the following:

Get Started with Application Composer

Before you begin, read this chapter to learn about Application Composer, how to access the tool, and how you can test the application changes you make once you're done.

This chapter includes:

  • A brief introduction to Application Composer, and how to access the tool

  • What you need to test your changes

  • How to let administrators assign themselves the job roles they need for testing

  • How to assign yourself any additional job roles required for testing

You should also be familiar with how to work with sandboxes. See the Configuration Life Cycle chapter in the Configuring and Extending Applications guide.

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.

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.

Application Composer is supported for use only in English. Additionally, 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.

To learn more about sandboxes, see the related topic Overview of Sandboxes.

Accessing Application Composer

Access Application Composer from any application 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.

This is a screenshot of the main Overview page
in Application Composer.

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.

    This is a screenshot of the Common Setup pane in
Application Composer.

What's Required for Testing Configurations in the Sandbox

If you're creating configurations for a specific job role or creating your own custom objects, then you must be provisioned with additional job roles to view and test those configurations in the sandbox. You can enable the testing of both types of configurations using the steps described in this section.

What's Required for Role-Specific Configurations

If you're creating configurations for a specific job role in either Application Composer or Page Composer, then you must assign yourself that same job role to be able to test the configurations in the sandbox. For example, if you're creating your own page layout for the Sales Manager job role, then you must have the Sales Manager job role to view and test the layout. If you later create a different layout for salespeople, then you must deprovision the Sales Manager job role and provision yourself with the Sales Representative job role instead.

What's Required for the Objects You Create

If you're creating your own objects, then you must assign yourself the Custom Objects Administration (ORA_CRM_EXTN_ROLE) role. The application automatically generates this object role the first time you create an object in the application. Unless users have this role, they can't view or test the objects they create.

Setup Overview

  1. While signed in as a setup user or the initial user you received when you signed up with Oracle, edit the role-provisioning rule for sales administrators and add the required job roles. Here is a summary of the steps:

    1. In the Setup and Maintenance work area, use the following:

      • Offering: Sales

      • Functional Area: Users and Security

      • Task: Manage HCM Role Provisioning Rules

    2. Search for all role-provisioning rules containing the Sales Administrator job role.

    3. For each rule, you add the job roles required for testing. Selecting the Self-requestable option makes it possible for individual users to assign themselves each job role when needed.

    4. If you're creating custom objects, then you must also add the Custom Objects Administration role. You must select both the Self-requestable and the Autoprovision option for this role. This object role is required for all objects you create, so you want to provision it automatically for future to sales administrators.

  2. Sales administrators, who are resources with the Sales Administrator job role, navigate to the Resource Directory and assign themselves the job roles they need. Setup users, who are not resources, can edit their own user records in the Manage Users work area and assign themselves the roles there.

    For details on how resources can assign themselves job roles in the Resource Directory, see the Assign Yourself an Additional Job Role topic.

Enable Sales Administrators to Test Configurations in the Sandbox

Modify the security role-provisioning rules to make it possible for administrators to assign themselves the job roles they need for testing custom configurations in the sandbox. For viewing and testing the custom objects they create, administrators must have the Custom Objects Administration (ORA_CRM_EXTN_ROLE) role. To test job role-specific configurations, they must have the same job role. In this example, we are looking at sales administrators.

Modify the Provisioning Rule for Sales Administrators

  1. Sign in as a setup user or the initial user you received when you signed up with Oracle.

  2. In the Setup and Maintenance work area, use the following:

    • Offering: Sales

    • Functional Area: Users and Security

    • Task: Manage HCM Role Provisioning Rules

  3. On the Manage Role Mappings page, search for the role mapping for sales administrators:

    1. In the Search region, click the Role Name list and select the Search link.

    2. In the Search and Select window, enter Sales Administrator in the Role Name field and click Search.

    3. Select the role name and click OK.

    4. Click Search.

  4. On the Manage Role Mapping page, click Search.

    The Search Results display the mappings with the Sales Administrator job role.

  5. Click the mapping name of each mapping and make the following edits:

    1. In the Associated Roles region, click Add Row (the plus sign icon) and add the job roles required for testing.

    2. For each job role, select the Requestable and the Self-requestable options and deselect Autoprovision. You don't want the job roles assigned to the sales administrators automatically.

    3. If you're creating your own objects, then you must also add the Custom Objects Administration role. The application automatically generates this object role the first time you create an object. For this job role select all of the options: Requestable, Self-requestable, and Autoprovision. All users creating their own objects must have this role.

    4. Click Save and Close.

  6. When you have added the job roles to all the provisioning rules, click Done.

Assign Yourself Additional Job Roles Required for Testing

Administrators can use this procedure to assign themselves the roles they need to test role-specific modifications in the sandbox. For example, if you're a sales administrator testing UI modifications for sales managers, you must assign yourself the Sales Manager job role. If you're creating your own custom objects, you must assign yourself the Custom Objects Administration role, if this role isn't already assigned to you. The Custom Objects Administration role is required for testing your objects in the sandbox.

Note: You can only assign yourself job roles that are made self-requestable in the role-provisioning rules created by a setup user. A setup user has the privileges to create other users and manage application security.
  1. Navigate to the Resource Directory.

  2. Select View Resource Details from the Actions menu in your record.

    Screenshot of portion of a sample Resource Directory
page with the Actions menu open
  3. On the Resource page, c.ick the Roles tab.

  4. Click Add Role.

  5. In the Add Role window, search for the role you want to use for testing by name or partial name, select it, and click OK.

    For testing objects you created, you must add the Custom Objects Administration role.

    Note: Available roles include only those that were set up as self-requestable during provisioning rule setup.

    The application returns you to the Resource page and displays the requested role in the Roles Requests region.

  6. You can remove a role you no longer need for testing by selecting it and clicking Remove.

  7. Click Save and Close.

    The new role becomes available for your use in a few minutes, pending the completion of a background process. The role displays in the Current Roles region the next time you navigate to this page.