You must understand the implications of database writes in a secure environment when electronic signature is enabled. Unsigned writes do not prompt for electronic signature. However, you can trace the results of unsigned writes through the alarm system. This section discusses the behavior of unsigned writes, based on the tag's configuration. To learn how to configure a tag for unsigned writes, refer to Understanding Unsigned Writes.
Tag Configured to Reject Unsigned Writes
If the tag is configured to reject unsigned writes, the write is rejected and this type of message is written to the alarm system:
UNSIGNED WRITE REJECTED: <tag name> cannot be written without electronic signature by <logged-in user name>
Tag Configured to Accept and Log Unsigned Writes
If the tag is configured to accept unsigned writes and to log the event, the write is accepted, and this type of message is written to the alarm system:
UNSIGNED WRITE ACCEPTED: <tag name> was written without electronic signature by <logged-in user name>
Tag Configured to Accept Unsigned Writes
If the tag is configured to accept unsigned writes, but not to log the event, the write is accepted, and this type of message is written to the alarm system:
<tag name> set to <new value> by <node>::<logged-in user name>
