Understanding Property Data Type Parameters
When you create or edit a property, you can configure the property parameters. The settings depend on the property and its data type. For example, string properties let you specify the minimum and maximum lengths of property values.
Many data types provide parameters for default values, minimum and maximum values, decimal precision, whether upper- or lower-case values are allowed, and so on. In addition, some data types let you configure a property to allow only values that you specify.
When creating a property manually or when registering a Universal application, select the template that corresponds to the data type of the property that you want to create (for example, Custom.Integer
).
Parameters for All Data Types
The parameters below can be set for all property data types.
Setting | Description |
---|---|
Default Type Note: This field is not available when you create a property during Universal application registration. Enter the specified value in Default Value or leave it blank if no default value is used. |
Specify whether or not the property has a default value.
|
Default Value |
If the property uses an Allowed Values list, select a default value from that list. Otherwise, enter a default value for the property. |
Rename on Update (Core.Name property
when the Default Type is Calculate and Store)
|
For Calculated and Stored name values, specifies that the name of the node should be recalculated and stored when the node is directly changed by a request action. See Calculating and Storing the Name of a Node. |
Rederive on Update (All properties that support a Default Type of Derived and Stored) |
For Derived and Stored property values, specifies that the
property value should be rederived and stored when the node is
directly changed by a request action. See Derived and Stored Properties.
Note: You cannot select Rederive on Update if Lock On Commit is enabled. |
Editable Note: This field is not available when you create a property during Universal application registration. After the property is created by the registration, you can access this field in the property parameters. |
Specify whether or not the property is able to be edited by users. |
Lock on Commit |
Specify that this property can only be updated on a newly added node. If this is enabled, after the request to add a node has been committed the value for the property is locked and can no longer be updated. Note: This option is available only when editing property parameters. Lock on Commit is available for node-level properties only. You cannot select Lock on Commit if Rederive on Update is enabled. Caution: Exercise caution when using Lock on Commit so that you don't unintentionally prevent users from being able to update a property that should be updated. For example, if you enable Lock on Commit on |
Inheritance |
The type of inheritance the property uses. See Inheriting Properties.
Note: You can override inheritance parameters at the application level only. |
Note:
For node data type properties only, the Default Value that you enter in conjunction with the Node Set, Allowed Node Types, and Selection criteria property parameters (see Node and Node List Data Type Parameters) will be converted to a node value as follows:
- If only one node is found then it is used as the property value.
- If more than one node is found, the first node in the order of the Allowed Node Types is used as the property value.
- If a node is found but it is not one of the allowed node types or does not meet the selection criteria, the string itself is used as the property value. You will be unable to validate the viewpoint with a string value in a node data type Default Values field.
- If no nodes matching the string and other property parameters are found, the string itself is used as the property value. You will be unable to validate the viewpoint with a string value in a node data type Default Values field.
For more information on parameters for specific data types, see: