Use the Data Schema editor OSM tab to define values for data elements that are associated with your OSM runtime system. See "Data Schema Editor" for information on the other tabs in the Data Schema editor.
| Field | Use |
|---|---|
| Significant Element | Specify whether the OSM server should consider the corresponding element during amendment processing. During amendment processing, the OSM system compensates only for task 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 (data schema), order template, and task-view levels. |
| Read Only | Specify to indicate that the data element is read only. This option applies only to tasks.
Note: If you are defining an attribute of a data structure definition element, do not use the Read Only check box to define the element as read only. Instead, deselect this check box and use the Behavior field to define a ReadOnly behavior for the element. |
| XML Type | Specify to indicate that the data structure definition is an XML data type. Structures defined as XML data types in the data structure definition can contain XML documents. |
| Maximum Numeric Digits | Enter the number of digits you want to allow in the OSM user interface for the corresponding element. This field is not available for edit if you define an OSM element mask for the corresponding field.
For data elements that inherit data from a base type, this field is read-only. |
| OSM Element Mask | Specify the string of characters used to define the format of the data in the field of the Task web client. When you create an OSM element mask, you can restrict user input for a field to a specific format. Use a mandatory mask character to create a field where a user must enter information in the appropriate format to complete the task.
For data elements that inherit data from a base type, this field is read-only. See "Using Masks" for more information. |
| Behaviors | Right-click to define behaviors for the corresponding data element. When you define behaviors at the Data Dictionary (data schema) level, the behavior can apply to all orders and tasks in which the data element appears.
Behaviors inherited from a base type are read-only. See "Defining Behaviors at the Data Schema Level" for more information. |