Engineering Tip
The only animated objects that allow security are:
-
- Button
- Text Input
- Function Key
When the class is configured with logging enabled (see Application -> Security Classes -> Class Name -> Log User Action), the message typed into the "Log Message" field is logged to the historian. What is not documented, are the keywords and special message formats that make this a truly useful feature.
All keywords are upper case and must begin with the % symbol:
%USER - Currently logged in user name
%VAL - Value of destination tag after the action
%OLD - Value of destination tag before the action
%CLASS - Security class that is assigned to this object
%ACTION - Action that was performed by this object
· · ON, OFF, TOGGLE, SET, ADD, SUB, FILE, QUIT, TOP, DRAW, ENABLE,
PAN, ZOOM, CHANGE, STOP, DRWTOP, MOM ON, or MOM OFF
%DATE - Date of action
%TIME - Time of action
The database stores the timestamp, user name, event keyword and message. An example of the logged data:
TMSTAMP OPERNAME EVNTYPE EVNTMSG
19980528161856 flink UPDINP TestTag was changed from 1 to 2
19980528161901 flink UPDTEXT New value typed 77
The EVNTYPE field allows the following event codes:
FAILTEXT - Failed to update text object
UPDTEXT - Updated text object (input text object)
UPDINP - Updated input object (button or fkey)
FAILINP - Failed to update input object
RTGSTART - Graphics task starting
RTGSTOP - Graphics task shutting down
SECVIOL - Operator failed to log in
SECLOGOUT - Operator logged out
SECLOGIN - Operator logged in
FAILLOGIN - Operator attempted to log in but failed
The security database does not roll-over automatically when using DB4HIST. To implement rollover, add the following line to the Database Schema table:
