About retentive attributes

Retentive attributes for ViewApp NameSpaces differ in how they behave from other Application Server objects and from InTouch retentive tags. The table below compares the runtime behavior of retentive attributes/tags for:

• ViewApp NameSpace retentive attributes

• Application Server retentive attributes. This includes retentive attributes for application and system objects such as:

  • User Defined objects

  • Analog Device/Discrete Device objects

  • Area objects

  • WinPlatform objects

• InTouch retentive values

  ViewApp NameSpace Retentive Attribute Values	Application Server Objects Retentive Attribute Values	InTouch Tag Retentive Values
  Retentive attribute values are saved when the ViewApp is closed. The saved value is loaded to the ViewApp when it is reopened. If more than one instance of a ViewApp is open, values for the last ViewApp that is closed will overwrite all previous values for the other ViewApps.	Values for retentive attributes are saved to disk every 10 seconds. Retentive attribute values are preserved across deployments. When an object is undeployed, the last saved value is restored at the next deployment	Retentive tag values are retained when the application stops, and are loaded when the application starts again. WindowViewer uses the retained valued as the initial tag value when it restarts, but does not write the value to the I/O device. I/O values are only updated after the I/O Server scans the device.