Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Link copied. Please paste this link to share this article on your social media post.
📖 Home Back
There are three independent flags on an alarmable object that control which alarms are disabled by logic, a schedule, or a user. If any of them are set then alarms are disabled. To find out which are set check the Alarm State in the View Dialog (right click on the object and select View).
ViewDialog-DisabledAlarms.PNGViewDialog-DisabledAlarms.PNG
As three distinct flags are set per alarmable object, alarms disabled by logic can only be re-enabled by logic, alarms disabled by a schedule can only be re-enabled by a schedule and alarms disabled by users can only be re-enabled by users.
All logic programs run as a special internal Logic user which has full access to everything, so which user is logged on will not change the behaviour of a logic program. If you want to prevent certain users from executing a logic program, set up security on the logic program.
Go: Home Back
There are three independent flags on an alarmable object that control which alarms are disabled by logic, a schedule, or a user. If any of them are set then alarms are disabled. To find out which are set check the Alarm State in the View Dialog (right click on the object and select View).
You cannot currently access these three properties directly using SQL or animations, instead they are used to create the derived Boolean property AlarmDisabled which is accessible
ViewDialog-DisabledAlarms.PNGViewDialog-DisabledAlarms.PNG
As three distinct flags are set per alarmable object, alarms disabled by logic can only be re-enabled by logic, alarms disabled by a schedule can only be re-enabled by a schedule and alarms disabled by users can only be re-enabled by users.
All logic programs run as a special internal Logic user which has full access to everything, so which user is logged on will not change the behaviour of a logic program. If you want to prevent certain users from executing a logic program, set up security on the logic program.
Go: Home Back
Author
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.