This article from InSource shows a workaround when you have an InTouch Read-only license attached to an application that is also set to Read Only, yet the application is still able to acknowledge alarms. This scenario is using InTouch Access Anywhere (but not specific to it) and using RDP (Remote Desktop Services).
- Author: Glenn Yancey
- Published: 12/15/2022
- Applies to: InTouch 2017 and higher
The same behavior occurs in an RDP session. So this is not ITAA specific. Alarms are being generated from the Console Session.
A Read Only application will prevent writes to IO Tags (but not Memory because that might be required to navigate within the app.). Also, if alarm provider app is a not read-only, you could ACK alarms.
E.g. For a ReadOnly App, Acknowledgements are prevented for \InTouch!System but not for \\<NonReadOnlyProvider\InTouch!System.
In that case the work-around is to disable the context sensitive menu on the alarm client as the use of a Remote Alarm provider is what was allowing us stil to acknowledge alarms on that console session from a user's session.