Oracle Fusion — Sandbox (Application Composer — Basic Concepts and creation of Objects) — Part1
Greetings, Oracle Enthusiasts!
In today’s blog, we delve into the realm of Application Composer, a powerful tool enabling us to tailor customizations to meet specific business requirements.
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 functions as a design-time tool that operates in real-time. This implies that you can seamlessly access Application Composer from within any application. You can implement your modifications, and witness the majority of these alterations instantly manifest without necessitating a sign-out and sign-in process.
This tool grants the ability to make data model adjustments that were once exclusively within the capacity of application developers.
For instance, effortlessly crafting a new object along with its associated fields, then generating fresh user interface pages where said object and fields are accessible to users.
Operating as a real-time design tool, Application Composer facilitates navigation directly from any application to effect changes promptly and observe most modifications taking effect immediately, eliminating the need to log out and back in. (However, end users need to sign out and sign back in after you publish your sandbox for them to see your changes. More on sandboxes will be detailed later in this topic.)
Note: To view real-time changes, always utilize the Navigator to navigate to the altered runtime page. Afterward, return to Application Composer to continue modifications. In essence, when adjusting and testing application changes, maintain usage within a single tab. Multi-tab usage is not supported by Application Composer.
Application Composer finds utility in configuring Oracle’s Sales and Fusion Service, as well as Supply Chain Management and Project Management applications.
Do note that Application Composer is not compatible with iPad devices.
Simplifying application alterations for non-developers, Application Composer harnesses a set of standardized design patterns and wizards to obscure the intricacies of application modification. Your focus remains on the business-required application adjustments — such as extending object models and modifying layouts — and Application Composer handles the creation of underlying object components.
By leveraging Application Composer, you’re enabled to carry out application changes such as the following:
- Amend objects by appending new fields or fabricating entirely new objects.
- Forge relationships based on foreign keys between two objects.
- Adapt user interface pages by exposing freshly created fields for an object, or erect entirely new operational areas for custom objects.
- Present object relationships in the form of subtabs on pages.
- Devise application logic like triggers, validation rules, and workflows for an individual object or multiple objects.
- Implement functional and data-level security protocols for custom objects.
- Activate objects for customized reporting.
It’s important to note that for these changes to become visible to end users, the process entails publishing your sandbox initially. Following this, end users need to log out and log back in.
Further details regarding sandboxes will be elaborated upon later in this discussion.
Let’s commence with the initial configurations:
Step 1: Activate a Sandbox (Configuration->Sandbox) and opt for the tool ‘Application Composer.’ Proceed to create and access the sandbox.
Moving on to the next step:
Step 2: Navigate to Tools -> Application Composer, then choose the desired Application (CRM Cloud or ERP and SCM Cloud).
Step 3: Click the “Add” button and complete the provided details as follows:
Here are the guidelines for filling in the details:
- Display Label: This label serves as a user-friendly name for an object. It’s not only the default page title within the object’s work area but also helps identify the object.
- Plural Label: The plural label becomes the title of the object’s work area and plays a role in regional search and saved searches on the object’s runtime overview page.
- Record Name Label: Use this field to determine the display label for an object’s RecordName attribute. This attribute stores user-entered record names. For instance, if you’re creating an object named “invoice,” you might use “Invoice Id” as the Record Name Label, which users would employ to uniquely identify each invoice record.
- Record Name Data Type: Choose between Text or Automatically Generated Sequence. The latter allows for specifying a sequence format like “SR-{0000000}-{YY}{MM}{DD}” resulting in values like “SR-0000123–110725” for July 25, 2011, with a sequence value of 123.
- Prevent Duplicate Values: By checking this box, you prevent users from inputting duplicate record names. Note that selecting this option enables case sensitivity assessment.
- Object Name: The object’s internal identifier, which should be unique across mainline code and existing sandboxes. If you’ve used it before in a sandbox, you can reuse it after deleting other sandboxes where it was used. Display names can be reused across sandboxes, but the uniqueness constraint applies to internal names.
- Description: Provide a comprehensive description of the object.
These details will help you define and customize your object effectively.
Step 4: Upon filling out the aforementioned details, your outcome would resemble the following:
Step 5: In the progression, you have the option to generate Custom Fields.
Step 6. Select the field type and create your fields one by one.
Now, you can proceed by crafting Custom Fields tailored to meet your specific requirements. Feel free to input all the necessary details as per your needs.
By following this approach, you can generate the necessary fields to your desired extent. Now, let’s move on to creating the pages.
Ultimately, you can proceed to publish the sandbox.
The custom object will become visible within the “Other” tab. Upon record creation, the appearance will be as depicted below.
You can access the backend specifics by utilizing the Metadata Manager report or by executing SQL queries.
Q1- select * from adf_extensible_table_usage where context_column_value like ‘Test123’ — — and table_id = 300000119852947
Q2- select * from adf_extensible_table
So, for this table_name is MKT_REF_ENTITIES, you can utilize the following query to retrieve the data:
select * from MKT_REF_ENTITIES where attribute_category like ‘Test123%’
Similar information can be obtained using the Metadata Manager Report, which is accessible outside the sandbox environment.
Click on Application Composer
Subsequently, proceed to select “Metadata Manager.”
An Excel file will be generated, which you can then download. The format will resemble the following example.
#oraclefusion #applicationcomposer
