How You Configure and Extend Applications Using Application Composer

Use Application Composer to extend and configure the install base asset and asset group objects by creating fields, objects, and relationships between objects. This includes the ability to directly manage the Edit Asset, Create Asset Group, and Edit Asset Group pages.

Here are some changes you can make to the Asset Group object using the Application Composer tool:

  • Modify the Asset Group object by defining new configured fields.
  • Modify the Create and Edit Asset Group user interface pages by exposing your newly created fields for the object.
  • Implement functional and data-level security for configured objects.
  • Write Groovy scripts using the expression builder, which appears in many places as you modify existing objects
Note: The Application Composer tool also supports the creation of your own objects and child objects related to the Asset Group object. These objects can’t be exposed in the Create and Edit Asset Group pages. However, if created, they are automatically provisioned in the Asset Group REST API.

Here are the number of available extended attributes using application composer:

  • Text: 100

  • Number: 50

  • Date and time: 10

  • CLOB: 5

Note:
  • By default, a configured object and its records are visible and editable only to users with the configured Objects Administration (ORA_CRM_EXTN_ROLE) role. This role should be given to any user who's using Application Composer. Additionally, the UI pages you create for configured objects aren't visible to additional users unless you provide access in Application Composer using the object's Security node. Use the Security node to specify not only which job roles can access the UIs, but the levels of access. Provision data security for configured object records and restrict users who have privileges to view, update, or delete records. You can give access to all users or only to members of access groups, to owners of records or to an owner and his management hierarchy, and to user-defined roles.

  • It's generally expected that you will either use flexfields or Application Composer attributes to extend the Asset object. You can use both, but it's typically recommended to only use one method to extend this object. The Asset Group isn’t enabled for flexfields.

  • Application Composer attribute values for assets and asset groups are be defined and updated using the Edit Asset, Create Asset Group, and Edit Asset Group pages and their respective REST APIs. They're not supported for an asset or asset group through using the File-Based import.

For more details about Application Composer, refer to the Using Maintenance guide, the Implementing Manufacturing and Supply Chain Materials Management guide, or the Configuring Applications Using Application Composer guide.