Properties View Order Data Tab

Use the Properties view Order Data tab to access and edit the information defined for the corresponding data element at the order template level. You can right-click any attribute in the Order editor Order Template field and select Open Properties View to open the Properties view Order Data tab. The following table describes the fields on the Properties view Order Data tab.

Field	Use
Name	The system displays the name of the node as defined in the Data Dictionary. The name of the node is not available for edit on this tab. You can edit the value in the Display Name field in the Data Schema editor Details subtab to edit the manner in which the element displays in the Task web client.
Path	The system displays an XPath expression to define the location of the node in the Data Dictionary.
Contributing Template	Displays the parent structure when the selected structure has been extended from a base structure. During order creation, you can base new orders on the functionality of an existing order by using the extend feature. When you extend an order, the extended order inherits all of the data, tasks, rules, and behaviors of the parent order. You can add new data and behaviors to each of the new orders to create unique order templates and behavior functionality. To implement changes to the inherited data, you edit the data in the parent order, and Design Studio automatically implements those changes among all of the extended orders.See "About Order Extensions and Inheritance" for more information. Additionally, the contributing template can reflect that the data node was contributed by an order component.
Data Dictionary	The system displays the name of the data schema (within the Data Dictionary) in which the node is defined.
XML Type	Select to signify that the structure is an XML data type. Structures defined as XML data types in the Data Dictionary can contain XML documents. Note: Before you use XML data types, copy all relevant schema (XSD) files into the cartridge project. Use the Java perspective Package Explorer view to copy the schema files into the dataDictionary folder. Note: This feature is not available in releases prior to OSM 7.0. See the Eclipse Java Development User Guide for more information about the Java perspective.
Significance	By default, a node inherits significance from its parent. At the order level, you can define the significance as Not Significant if you do not want to use the node during amendment processing. During amendment processing, the OSM system compensates only for order instances that use significant data elements as inputs. If an element is not specified as significant, the system updates the order only with the changed data (no compensation is required). Data significance is supported at the Data Dictionary, the order template, and the task levels.
Ignore rollback during undo	There may be data on an order or task that you want to exclude from rollback in cases when the order or task is running in undo mode. For example, you may want to retain data related to status messages when a task rolls back during a fallout scenario where the status messages may contain important troubleshooting information. If you set this value for a structure, all child structures and elements also ignore rollback during the undo execution mode. You typically set this value for data generated during order processing, for example, with external fulfillment state updates, external processing states updates, or status nodes for external response messages. Oracle recommends that you not set this value for data from the upstream system, for example, from the original order. Oracle recommends that when you set this value, you also set the significance value to Not Significant. Note: Do not set this value for ControlData fulfillment state and processing state elements because OSM calculates these elements based on data received from external system where Ignore rollback during undo is appropriate to set.