This demonstration shows how to create a child object in Application Composer. The child object we are creating appears as a subtab in the runtime application.
Child objects do not have a separate work area, and their records are deleted when you delete the parent object records.
In this demonstration, we will create a child object, called activity. At runtime, users will create activities to record what they did to resolve the issues in a trouble ticket.
This is the first in a series of related demonstrations on creating a child object in Application Composer. These demonstrations cover:
1. Creating a child object
2. Adding a long text field to a child object
3. Adding a fixed choice list field to a child object
4. Adding a subtab to display the child object records
5. Testing the subtab in the runtime application
Steps:
Here is a trouble ticket to show you what the finished child object will look like to the user.
Step 1The child object will appear on a subtab that we will create in a related demonstration.
Step 2Activities capture the tasks the organization takes in response to the issues in the trouble ticket.
Step 3The activity child object is made up of four fields.
- Activity Name
- Creation Date
- Description
- Status
Step 4Activity Name is added automatically when you create the child object.
Step 5Creation Date is provided by Oracle and available for display in every custom object.
Step 6Description is a long text field we will create in a related demonstration.
Step 7Status is a fixed choice list field that we will show you how to create in another demonstration.
Step 8To create a child object, begin by navigating to the Application Composer and selecting the application where the parent object was created.
The trouble ticket is part of the Sales application.
Step 9Click the Trouble Ticket link.
Step 10Click the Create Child Object button on the far right.
Step 11The Create Custom Child Object window appears.
Step 12In the Display Label field, enter a name for the object. Enter "Activity".
Step 13The application will fill in the rest of the fields for us, so we are done.
Step 14Click the OK button.
Step 15The application populates the rest of the fields and creates the object.
Step 16The Plural Label field is not used for creating a child object, so we can ignore it.
Step 17Activity Name is the label for the field where users enter a brief summary of the activity.
Step 18The Activity child object is now listed among the custom objects.
In related demonstrations, we will add fields to this object and create a subtab for it on the work area of its parent object, the trouble ticket.
Step 19This completes the demonstration of creating a child object in Application Composer.