Orchestration Fulfillment Pattern Editor Order Components Subtab

Use the Order Components subtab to select all of the order components to which an order item associated with the corresponding orchestration fulfillment pattern can be added when OSM creates an orchestration plan, to specify the time OSM can expect to process a single order item for the associated order component, to include any order items that do not share the same fulfillment pattern, and to add order items to an order component only when the condition evaluates to true.

Order Components

Use the Order Components area to select all of the order components to which an order item associated with the corresponding fulfillment pattern can be added when OSM creates an orchestration plan.

Field Use

Base Component

Functions

Search

Use these fields to limit the number of order components that appear in the Order Components area. The Order Components subtab displays all order component specifications defined in the workspace. Use Base Component to limit the display to a single root-level order component and its dependencies. Use Functions to limit the scope to executable order components (order components associated with a process). Enter a value in the Search field to search for a specific order component.

Order components list

Displays the order components that meet the criteria selected in the Base Component, Functions, and Search fields. A check preceding the order component indicates that it is an order component executed by the orchestration fulfillment pattern. You can right-click in this box and select any of the following functions:

  • Create New Order Component: Select this to create a new order component as a child of the selected order component. See "Creating New Order Component Specifications" for more information.

  • Create New Root Order Component: Select this to create a new order component that is not a child of another order component. See "Creating New Order Component Specifications" for more information.

  • Create Fulfillment State Mapping in Default Map: Select this to create a new fulfillment state mapping in the fulfillment state map entered in the Default Fulfillment State Map field on the Details tab. See "Creating New Fulfillment State Maps" for more information.

  • Create Fulfillment State Mapping: Select this to create a new fulfillment state mapping in a fulfillment state map of your choice. When you select it, an dialog box is displayed that allows you to select a fulfillment state map to contain the new mapping. See "Creating New Fulfillment State Maps" for more information.

When you select one of the options to create a new fulfillment state mapping, the orchestration fulfillment pattern and fulfillment mode criteria are entered by default in the new mapping. If all of the following conditions are met, the new mapping will also contain the order item, orchestration sequence, orchestration stage, and order component criteria.

  • The selected order component is produced by exactly one orchestration stage.

  • The orchestration stage is produced by a single orchestration sequence.

  • The orchestration sequence specifies an order item in its Order Item field.

You can make any changes you like to the default data values provided in the mapping.

Open

New

Select any order component in the list and click New to create and add a new order component to the list. Click Open to open the order component in the Order Component Specification editor.

Selected Order Components

For each order component you select in the Order Components area, you can also define its processing duration, whether the order items included in order components are associated by additional properties (such as component IDs), and the conditions that dictate whether the order items are added to the order component.

OSM uses either the orchestration fulfillment pattern selected order component duration or the order component specification duration, whichever is longer, to determine the start times for order components. See "Order Component Specification Editor Duration Tab" for more information.

If Use Calculated Start Date is enabled, the order component will not start until the calculated start date is reached. If the current date and time are greater than calculated start date, then the calculated start date is ignored.

If Use Calculated Start Date is disabled, the order component starts as soon as all preceding dependencies are resolved.

The calculated start dates are only used if there is sufficient time to meet the date. Otherwise, the order component begins immediately.

See "Order Component Specification Editor Details Tab" for more information about Use Calculated Start Date.

OSM uses several configured durations to calculate the start times for order components. See OSM Modeling Guide for more information.

Field Use

Duration subtab

Specify the time OSM can expect to process a single order item for the associated order component for this orchestration fulfillment pattern.

The Optimistic Processing Duration area contains information about the minimum expected duration. The Most Likely Processing Duration area contains information about the most likely expected duration. The Pessimistic Processing Duration area contains information about the maximum expected duration.

For each of the areas, do one of the following:

Order Item Associations subtab

Include order items that do not share the same orchestration fulfillment pattern in the order component.

Select an order component in the Order Components area and do any of the following:

  • Click Add to enter a name for a new order item association.

  • Click Select to select a previously created order item association to associate with the corresponding order component.

  • Click Remove to delete an order item association from the list.

You can select the following options in the Order Item Associations subtab:

  • Fulfillment Pattern

  • Matching Order Component ID

  • Property Correlation

By default, Fulfillment Pattern is selected. You can also group order items into an order component when those order items share a common component ID or property correlation. If you select Property Correlation, enter an XQuery expression to select the order item property. See "Orchestration Fulfillment Pattern Editor Orchestration Plan Tab" and "About Associating Order Items Using Property Correlations XQuery Expressions" for more information.

Conditions subtab

Provide a condition so that OSM adds order items to an order component only when the condition evaluates to true. Select an order component in the Order Components area and click Add to open the Add Condition dialog box, where you can specify a name for a new condition.

Click Select to open the Select a Condition dialog box, where you can select a previously created condition to associate with the corresponding order component.

Select any condition and click Remove to delete it from the list.

Select any condition from the Conditions list and enter the XQuery expression to run against the order item. See "Orchestration Fulfillment Pattern Editor Orchestration Plan Tab" and "About Order Item Specification Condition XQuery Expressions" for more information.

Point of No Return subtab

Associate a point of no return with one or more common fulfillment states for the currently selected order component. Select a point of no return from the list, and then select each of the fulfillment states to which that point of no return should apply. Note that a point of no return must be associated with each fulfillment state that can cause it. Selecting a parent fulfillment state indicates that a point of no return will also be set for the children of that fulfillment state. The list of points of no return is populated with the values listed in the Orchestration Fulfillment Pattern editor Details tab.