Order Editor Details Tab

Use the Order editor Details tab to define the order attributes that you use to associate the order with other entities, enabling the order to execute correctly in the OSM run-time environment. The following table describes the fields on the Order editor Details tab.

Field	Use
Extends	You can select an existing or create a new order to extend this order (the order's data is inherited) by clicking the Select button. To create a new order that this order would be an extension of, click New. After you have selected or created an order, click Open to access the Order editor. Click Clear (red X) to clear the selected value from the field. Order data extensibility enables you to leverage order data when building new, similar orders.
Lifecycle Policy	Select an existing or create a new lifecycle policy to control which order state/transaction combinations a role can perform for this order type. Every order you create within Design Studio must be associated with an order lifecycle policy.
Default Process	Select an existing or create a new process to which the order is submitted. When the selected default process is an orchestration process, Design Studio looks for the Data Dictionary project OracleComms_OSM_CommonDataDictionary, which contains definitions of common OSM structures such as control data, base order item data elements, base function data elements, and so on. If the Data Dictionary does not exist, you will be prompted to import it. After the Data Dictionary is imported, Design Studio automatically attaches base control data such as ControlData/Functions and ControlData/OrderItem from the imported Data Dictionary to the order.
Order Item	Identifies whether an order item specification is associated with the order through the following relationship: Order > Orchestration Process > Orchestration Sequence > Order Item Specification. If no process (or a provisioning process) is associated with the order, None is displayed. If an orchestration process is associated with the order but there is no association with an order item through the relationship path, No Order Item Configured is displayed.
Creation Task	Select an existing or create a new task to create and submit the order before the workflow begins. The creation task defines which subset of data is required to create the order. When at the creation task, an order has not been submitted to a process and has had no work completed. The creation task has two associated states, submit and cancel. Additionally, you can define statuses for the creation task on the Task editor States/Statuses tab. You need a creation task for any order creation (manual, automated, etc.). If you want to enable behaviors when creating an order, select manual tasks as creation tasks for an order. If the order associated with the creation task is defined as amendable (on the Order editor Amendable tab), do not include optional fields in the creation task as this can cause unexpected results. When including optional fields in the creation task, the original order is submitted with all optional fields left empty. The optional fields are later populated during task execution. When a revision order is submitted with the optional fields now populated, the system treats the optional fields on the revision as different instances of the fields from the ones populated on the original order and OSM triggers compensation. Note: You can automate order creation using the XML API or the web service interface. See OSM Developer's Guide for more information.
Order Source	Enter an order source for the order if you would like it to be different from the order name. In the order structure, there are separate fields for order source and order type. If you leave this field blank, both fields on the order will default to the order name when the cartridge is built. If you enter a value in this field, it will be used for the order source field, and the order name will continue to be used for the order type.
Order Source Description	Enter a description of the order source if desired. If this value is not entered, it will be defaulted to the order name when the cartridge is built. This description will be displayed in the Task web client.
Priority Range	Specify a minimum and maximum priority for the order to execute within. For example, if you specify a range of 5-7 and the order is created with a priority of less than 5, the priority value will be rounded up to 5. If the order is created with a priority of more than 7, the priority value will be rounded down to 7.
Realizes	If this order is a concrete implementation of a Functional Area from the PSR model, click Select to select the Functional Area. If a Functional Area has been defined for the order, you can click Open to open the Functional Area. This association can also be defined in the Functional Area. See "About Functional Areas" for more information.