Order Item Specification Editor Order Template Tab

Use the Order Template tab to model the data that OSM requires for orchestration; this data is referred to as order item control data. You can drag data from the Dictionary view into the Order Template area, or you can right-click in the Order Template area to select data from the Data Dictionary dialog box.

The recommended data schema to use to model order item control data is the predefined data schema of the OracleComms_OSM_CommonDataDictionary model project. See "About the OracleComms_OSM_CommonDataDictionary Model Project" for information on creating this project in your workspace.

Note:

See "Order Item Specification Editor" for information about fields that appear on multiple Order Item Specification editor tabs.

Field	Use
Order Template	Add all of the data necessary to create orchestration plans that will include this order item. There is a minimum set of control data that you must define for a cartridge to build properly. For each order item, you must create a structure called ControlData, which contains a child structure called OrderItem. See "About Modeling Order Item Control Data" and "Modeling Order Item Control Data" for information on how to model the ControlData/OrderItem structure. The following are examples of data nodes you can model below OrderItem: itemName menuItemType productSpec size The data you add here contributes to the order template data (added to the order template of the order as read-only data).
Behaviors	(Optional) Define behaviors for each data node in the order template. Select a data node in the Order Template area to view the behaviors defined for the node or to create new behaviors. See "Working with Behaviors" for more information.

Field

Use

Order Template

Add all of the data necessary to create orchestration plans that will include this order item.

There is a minimum set of control data that you must define for a cartridge to build properly. For each order item, you must create a structure called ControlData, which contains a child structure called OrderItem.

See "About Modeling Order Item Control Data" and "Modeling Order Item Control Data" for information on how to model the ControlData/OrderItem structure.

The following are examples of data nodes you can model below OrderItem:

itemName
menuItemType
productSpec
size

The data you add here contributes to the order template data (added to the order template of the order as read-only data).

Behaviors

(Optional) Define behaviors for each data node in the order template. Select a data node in the Order Template area to view the behaviors defined for the node or to create new behaviors. See "Working with Behaviors" for more information.