Property template properties (More tab - Float)
The More tab on the properties page for property templates defined as
data type float is described below. Float properties are stored internally
as 64 bits.
- Value Required
- Assign this attribute to properties which must have a value. The user cannot leave a property with this attribute blank or an error results when the property is saved.
- Persistence
- Set the persistence for a single-valued property by selecting one of two
choices:
- Transient - Property values are visible to Event Actions but otherwise
discarded.
- System Table - Property values of a float data type are stored in the
system-defined table, ListOfFloat, in the object store database. The default
is persistent in the System Table.
Set the persistence for a multi-value property by selecting one of three
choices:
- Transient - Property values are visible to Event Actions but otherwise
discarded.
- System Table - Property values of a float data type are stored in the
system-defined table, ListOfFloat, in the object store database. The default
is persistent in the System Table.
- Own Table - Property values are stored in their own indexable table in the
object store database, allowing you to create your own index(es) for
searching. The table name consists of “u_” followed by the SymbolicName of the
property.
Once you set the persistence, you cannot change it.
- Hidden
- Assign this attribute to property templates that
are used by the system, but not by the end user. This attribute provides
a hint to the application not to display the property. If the application
does provide the user with access to a property defined as hidden, the
user can do anything with the property that they could do with an unhidden
property.
- Settability
-
- Read only - Users cannot enter a value for properties with this attribute.
Use this attribute for properties that currently have a default value,
but might have different values in the future, or for properties that
have a constant value within all instances of the class.
- Read/Write - Users can view and change values.
- Settable only before checkin - The value can be set only before the
object is checked in.
- Settable only on create - If the value for this attribute is True,
the user cannot change the value once it has been saved in the database.
An example of a property that could be Settable Only When Created is
Entry Date. Once you set a value for this attribute, you cannot change
it.
- Category
- Use this optional string property to group related properties together for sorting purposes. For example, you could enter the name of the AddOn XML file that was used to import the property into the object store. When displaying property templates in Enterprise Manager's Property Templates node or when displaying the results of an Enterprise Manager search for property templates, you can sort properties based on the value of this property.
- Minimum Value
- Use this attribute to limit the minimum value. The
lowest value allowed is -1.7E308. If you make a change to this attribute,
the change will propagate to all subclasses where the current value is
less than the new value or where a value is not set.
- Maximum Value
- Use this attribute to limit the maximum value. The
highest value allowed is +1.7E308. If you make a change to this attribute,
the change will propagate to all subclasses where the current value is
greater than the new value or where a value is not set.
- Default Value
- Use this attribute if you want to provide the user
with a default value for the property. You cannot set this value if the
property is a multi-value.