View Dependencies at Object Level

Some UDOs are comprised of multiple parts. For example, to create a watchlist UDO, a user must first create an advanced query UDO, on which to build the watchlist threshold criteria. To approve a dependent UDO, both parts must have their statuses in sync.

The View Dependency form (W98700DA) provides detailed information of the object dependencies for UDOs such as watchlist, Composite Application Framework (CafeOne), composite page (Release 9.2.3), form extension (Release 9.2.3.3), orchestration (Release 9.2.5.3), and notification (Release 9.2.5.3).

Note: (Release 9.2.3.3) For form extension, you can only view dependency information about the orchestrations that are associated with events from the Associate Orchestrations wizard.

For example:

• For watchlist, you can view the information of the dependent query.

• For composite page, you can view the information of the UDOs or other general EnterpriseOne objects embedded in the composite page.

• For Composite Application Framework (CafeOne), you can view the information of the EnterpriseOne application embedded in the CafeOne layout.

• (Release 9.2.3.3) For form extension, you can view information about the dependent orchestrations that are associated with the form extension.

• (Release 9.2.5.3) For orchestrations and notifications, you can view information about the dependent components such as orchestrations, notifications, form requests, rules, and so on.

  Note: You can view dependency information of only the orchestration and notification components that were created in the Orchestrator Studio and you cannot view dependency information of the OMW objects associated with the orchestration components. For example, if an orchestration has a message request as one of its components and the message request has a link to an application that has a form extension associated with it, the form extension will not be displayed as a dependent object for the orchestration on the View Dependency form. However, the applications, personal forms, or watchlists that are directly specified in the message will be displayed as dependent objects.

Tutorial: Click here to view a recording of this feature.

To view UDO dependencies:

1. Navigate to Work with User Defined Objects (P98220U).

2. Search for and select the UDO for which you want view dependencies.

3. Click the Row button, select Advanced, and then click View Dependencies.

   Alternatively, access Object Management Workbench - Web (P98220W). In the Object grid, select the UDO for which you want view dependencies, and then from the More Row Actions drop-down menu, select View Dependencies. (Release 9.2.3)

   The View Dependency form displays.

4. The Calling Object field displays the system-generated number associated with the UDO that calls the dependent UDO.

5. You can further refine your search by entering the Object User and the Called Object information into the respective fields, and then clicking Find.

   If there is a dependent UDO, it displays in the grid.

   The following list describes the grid columns:

   • Calling Objects – The system-generation number that identifies the UDO that calls the dependent UDO. If you click the number in this column, EnterpriseOne provides the property information of the calling object.

   • Calling Description – The user-defined description of the calling UDO.

   • Calling Type – The user-selected UDO type of the calling UDO.

   • Called Object – The UDO that is called by the calling UDO.

   • Called Description – The user-defined UDO description of the called UDO.

   • Called Type – The user-selected type of the called UDO.

   • Object User – The user ID for the UDO creator.