Skip Headers
Oracle® Communications Design Studio Modeling OSM Orchestration
Release 7.2.4
Go to Design Studio Help Home
Go to Table of Contents
Go to Feedback page

Go to previous page
Go to next page
Mobi · ePub

About Autogeneration of Order Component Control Data

When the OracleComms_OSM_CommonDataDictionary model project is in your workspace, Design Studio automatically generates control data structures for order components and associates them with the order provided the following conditions are met:

Note:

The following conditions reflect basic orchestration setup requirements for all orchestration-related cartridges. Order component control data is automatically created if you preconfigure your orchestration cartridges correctly.

If the preceding conditions are met, Design Studio automatically adds the following relevant data elements for control data to the Order Template tab of the order component specification:

Autogeneration of order component control data works as follows:

  1. You select an orchestration process as the default process to which an order is submitted (to create the orchestration order).

  2. Design Studio looks for the OracleComms_OSM_CommonDataDictionary model project in your workspace; if it does not exist, Design Studio prompts you to create it.

    If you agree to create the model project when prompted, Design Studio creates it in your workspace.

    The OracleComms_OSM_CommonDataDictionary model project contains the base ControlData structure and the data elements it references: base order item data elements and base function data elements.

  3. You associate the order component with the orchestration order.

  4. You add the order component to a fulfillment pattern that is part of the orchestration plan.

  5. Design Studio does one of the following:

    • If the ControlData structure does not exist for the order, the base ControlData structure is automatically included from the data schema of the OracleComms_OSM_CommonDataDictionary model project into the Order Template of the order and order component. The required orchestration data for the new order component is added to the structure as ControlData/Functions/Order_Component_Name.

    • If the ControlData structure already exists for the order, Design Studio updates the existing ControlData structure in the order with the required orchestration data for the new order component (creating the substructure ControlData/Functions/Order_Component_Name). Design Studio adds the structure to the Order Template tab of the order component.