Relevant only on workstations whereReadOnlyStation is set. Does not apply otherwise. A full discussion is provided in the topic, Read-Only Workstation.
This is a bitwise value that controls which application privileges are enabled at a read-only workstation. (This does not grant privileges that an operator does not have. Rather, it restricts the enabled privileges regardless of whether the signed-in user otherwise has those privileges. See also: StationMaskSys
The default system privilege mask for a read-only workstation does not grant the configuration privilege or the edit files privilege. If you configure the workstation you are using to be read-only, you will have no means to do further configuration at that workstation, or even to reverse that change. Your only recourse will be to move to another workstation on your system and use the Version Control system to reverse the change.
*******************************************************
*** DEFINING A WORKSTATION TO BE READ-ONLY ***
*** IS BEST DONE FROM ANOTHER WORKSTATION. ***
*******************************************************
(A remote connection using a VIC or Anywhere client does not count as working at another workstation. Do not proceed unless your application has a Client / Server Configuration)
If creating a StationMaskApp, you are advised to set the workstation property to match the name of the read-only station where it will be in effect. There is no default value for StationMaskApp.
Default:
Section: <SecurityManager-Admin>
Note that <SecurityManager-Admin> is a hidden section. You can create this property using the Application Configuration dialog, but you cannot edit it there.
Application privileges are numbered starting at 16, as shown in the Privileges dialog (Protect Pages and Output Tags) when Show Privilege Numbers is selected.
Bits are numbered starting at zero, and reading from the right to the left. Therefore, to discover which bits to set when creating StationMaskApp, you must subtract 16 from every application privilege as shown in the Privileges dialog. (Privilege 16 is bit 0, privilege 17 is bit 1.)
Using the StationMaskApp property to enable an application privilege that allows authorized operators to write through a protected I/O tag will have no effect. Read-only stations cannot write to I/O under any circumstances. Any privilege to allow I/O writes is meaningless at a read-only station.
