1. Using Innovation Management
  2. Relationships with Other Business Objects

Relationships with Other Business Objects

A relationship is a linked association from one business object to another. Establishing a relationship on one business object automatically creates a relationship on the other object back to the first.

There's no differentiation or hierarchy to relationships. The type of relationship being established is important for the user to assess dependencies, to track verification and validation, and fulfillment. Knowing if there's an impact coming from the object or if the object impacts another object, and if the object fulfills a required relationship all help the user know how to proceed with the innovation process.

Duplicating relationships with objects isn't possible.

Relationships Between Business Objects in Applications or Systems

Listed by application, relationships may be established between business objects from these applications or systems:

  • between business objects that were created in any of the Innovation Management modules, the Concepts, Proposals, or Ideas work spaces;

  • between an Innovation Management object and a Product Development item; or,

  • from an Innovation Management object to a business object in another compatible system, such as Agile Product Lifecycle Management.

A relationship link to an Innovation Management object opens that object in a new tab. A relationship link to an object in a configured compatible system, such as Agile Product Lifecycle Management opens in a new tab.

Note: For business objects outside Innovation Management to be available for relationship, the administrator must set up object types for compatible applications on your system. For instance, if Product Development is configured on your system, you must see Items on the list of types that are available on a search.

The current releases of Oracle Cloud Innovation Management (IM) and Oracle Agile Product Lifecycle Management (PLM) are certified for bidirectional relationships; properly configured on both sides, an Innovation Management business object can be viewed in PLM as well as PLM to Innovation Management. And since relationships are version-specific between Innovation Management (versions) and PLM (revisions); the version is maintained as part of the relationship.

New Version of Requirements on Relationships Tables

Given that you can establish relationships between business objects per the previous information, this list indicates the appearance of the "Has Changed" icon when one of the objects is modified and therefore exists in a "later version". Hovering your mouse over the Has Changed icon displays the tool tip "Modified in a later version".

There may be reasons that the original relationship - the relationship of an object with a particular version of another object - remains valid after one or the other object moves to a new version; so, the application don't automatically update, or change, the object in the Relationships table. It does, however, indicate that a later version now exists.

The Has Changed icon appears on the Relationships table of these business objects when modified and a new version exists:

  • Requirements that appear in any of the Innovation Management modules (on Concepts, Proposals, and Ideas work spaces);

  • Items from Product Development that are in relationship with requirements; or,

  • Requirements (from Innovation Management) and business objects from Agile PLM, which are in relationship, appropriately indicate a new version exists in each others' Relationships tables.

Related Topics