User`s guide

52 Creating FPM Templates
Application Layer Interoperability Guidelines for more information about
configuration property restriction flags.
• const_flag. The value of the configuration property cannot be changed.
Note: When you deploy the FPM on the SmartServer, the configuration
property is automatically set to be persistent. This means that the
configuration property’s default value is updated to match the current
value stored in the configuration property, and that configuration
property’s current value persists through reboots.
• device_spec_flg. The value of the configuration property is always
read from the device and can be modified independent of the LNS
database.
• mfg_flg. The configuration property value can only be changed when
the device is being licensed.
• obj_disabl_flg. The device must be disabled for the configuration
property value to be changed.
• offline_flg. The device must be offline for the configuration property
value to be changed.
• reset_flg. The device is reset after the configuration property value is
changed.
When a functional block implements a profile, each of the implemented
member configuration properties must specify at least those restriction flags
that are set in the profile. Restriction flags that are not set in the profile may
be set by the implementing property, unless this would cause an ambiguous
restriction flag set.
Applies To Specify the scope of the configuration property. The configuration property
can apply to the entire Functional Block or a network variable within the
functional profile template.
If the configuration property applies to the functional block, and the
functional block implements an inheriting type, the property will derive its
type from the principal network variable. A principal network variable must
be defined in this case.
If a configuration property is to apply to a specific network variable, select
the network variable from the Applies To list.