Recent releases have seen the uptake of elements of the Application Composer platform within products beyond Oracle Sales Cloud. This brief post introduces the functionality it offers developers and business analysts.
As part of the Oracle Product Requirements and Ideation Management product set from the Oracle Supply Chain family, the Oracle Innovation Management component offers a systematic approach to capturing, selecting and investing
in the right ideas and product concepts. This relatively new application product includes a distilled version of the Application Composer found in Oracle Sales Cloud to offer the same core set of extensibility features. The tool is actually known as Data Composer (or as the JEDI platform) and is the same foundation upon which Application Composer is built.
In Oracle Innovation Management the Data Composer feature provides access to a predefined set of Standard Objects and their fields. The Data Composers goal here is to support the creation of new fields (also known as attributes) on standard objects, and to support custom scripts to help meet specific business requirements.
If you edit one of the standard objects, you can see the field types (custom and standard) in two panels side-by-side. Here you can add custom fields and edit standard fields.
Through the "Edit Business Logic" button on the first screenshot you can add Groovy-based Validation Rules (on fields or objects), Triggers, and Object Functions. As you can see from the screen below, it's the same set of scripting features as in Application Composer for Sales Cloud.
Within the scripting support the triggers event points are simplified to just the three basic CRUD operations, as shown here:
Oracle Project Portfolio Management offers comprehensive project management features for organizations who operate based on discrete work cycles. The implementation of Data Composer here exposes the same feature set as above, with one addition - the creation of new custom objects - as illustrated by the enabled icon in the table below.
Here the landing page shows existing Standard and Custom Objects (note the Custom column in the table - none in this example however). There is also the same support for scripting via the same 'Edit Business Logic' button.
When compared with Oracle Sales Cloud's Application Composer you'll notice many differences here, such as no left-hand navigator region with object nodes like 'Pages', 'Actions/Links', and also no 'Common Setup' collection of features either (which contains things like run-time messages, object workflow, relationships, and security). So how these more limited Data Composer features used?
The answer is essentially within the ability to define new objects / fields and to add script-based customizations. It is the scripting that permits these new objects and fields to be included in the end-user functionality. Custom fields on standard objects can be shown/hidden using Page Composer and what they do at run-time depends on the scripting added.
It is through the use of scripting such as triggers added to standard objects where custom fields and custom object records can be validated, queried, added, updated, and deleted based on your business requirements. Therefore while custom objects created in Project Portfolio Management's Data Composer are not exposed as standalone pages, they can still be used by business logic and also reported upon.
If you've experience of using these two Data Composer implementations in your projects we'd love to hear your experiences in the comments below.