Audit question in Multi client project

Considerations when using WinCC Audit on Multi-Client Applications

Multi-Clients are a special type of client that display selected portions of up to twelve WinCC server applications. There are limited capabilities for configuration in these projects, since there is no Alarm Logging, Taglogging, or User Archive Editors. Likewise, there is no runtime data stored in a multi-client project database.

Notes:

• Configuration auditing and document control can be performed on Multi-clients.
  


• Runtime auditing and Operator Actions auditing on the local multi-user project are not possible due to the multi-client architecture. Multi-clients do not support scripts and have no runtime data.
  


• When accessing a WinCC Server application graphics page from a multi-client, Operator Actions on standard objects (IO fields, Check boxes, Option boxes, Sliders, and Drop down lists) will record the audit in the server application’s Alarm Logging (MSArcLong) database.
  


• When accessing a WinCC Server application graphics page from a multi-client, custom Operator Activities functions will not work, due to the remote scripting limitations of the multi-client.

  ---