Advanced event settings
Breadcrumbs: Navigation > Events > Event > Advanced Settings Auth Groups. Auth groups If an event is assigned to one or multiple auth groups, only responsible users which belong to that auth group ca…
Breadcrumbs: Navigation > Events > Event > Advanced Settings
Auth Groups
Auth groups | If an event is assigned to one or multiple auth groups, only responsible users which belong to that auth group can see and modify those events in EMS. Note: users with admin or tenant role have permission to see and modify all events, irrespective of the auth group. |
Arm / Disarm event
Allow disarm event | If active, the event can be disabled. Note: only users with the permission "allow disarm event" configured in the User Settings can perfom this action. |
With code | If defined, this code is required to disable the event. |
Max deactivation (Hours) | The max. timespan in hours for which the event can be disabled. |
Event when disarm | If defined, the selected info event will be activated when the event is disabled. |
Quick activation
Quick activation | This setting defines the options how an episode can be started from the s.GUARD applications: Icon - episode can be started by clicking on the event icon, as well as by using the "activate event" button Whole item - episode can be started by clicking anywhere on the event tile, as well as by using the "activate event" button Disabled - episode can only be started by using the "activate event" button |
Custom configuration
External Code | To be used if the event is used to communication with an i.SITE transmitter connected via an Edge Device: 1 - normal paging message 3 - timesync message |
Follow up
Add Follow up setting | Click to add additional rules for "follow up" events. |
If | The condition under which a follow up event will be triggered: One user must confirm - As soon as one recipient confirms, the follow up event will be triggered All must confirm - As soon as the required number of confirmations defined in the event settings has been reached, the follow up event will be triggered Event duration time is over - if the episode is terminated because the timeout has been reached, the follow up event will be triggered Event stopped - if the episode is terminated, the follow up event will be triggered. The reason for the termination of the episode is not relevant. Always - as soon as the episode is started, the follow up event will be triggered too. |
Target event | The event which shall be triggered as follow-up |
Transfer initial info | If enabled, the content of the ~message~ placeholder will be transferred to the follow up event. |
Transfer activator info | If enabled, the activator of the inital event will be transferred to the follow up event. For follow up events of loneworker or watchdog episodes, this will only lead to the activator name being displayed as activator in the event log. For all other events, the activator will be completely transferred to the follow up event and treated as such. E.g., if the follow up event is a conference call, the activator will be included in that conference call. |
Transfer recipients info | This setting defines which recipients will be transferred to the follow up event: None - No recipients are transferred Recipients who confirmed - All users that have confirmed the initial event are transferred Recipients who reacted - All users that have reacted to the initial event, i.e. who have confirmed or rejected, are transferred Recipients who rejected - All users that have rejected the initial event are transferred Recipients who didn’t react - All users that have not reacted at all to initial event are transferred All recipients - All users from the initial event are transferred |
Watchdog
Watchdog events are used to monitor the connectivity between a third party system and s.GUARD.
Warning event | The event which shall be triggered if the watchdog event is not activated within the delay timeframe. |
Channel | This defines the channel which shall be monitored by the watchdog: API - episode activation via API EMAIL - episode activaton via incoming e-mail VOICE - episode activation via incoming phone call SMS - episode activation via incoming SMS PUSH - episode activation via s.GUARD applications |
Delay (Minutes) | Timeframe in which the watchdog event shall be triggered at least once |
Example:
If the EMAIL channel shall be monitored, the third party system is configured to send an e-mail once per hour, containing a subject which is configured on the watchdog event as activating key text.
In that case, the radio control of the EMAIL channel is switched on and the delay is set to 70 minutes to account for some delays.
If 70 minutes have passed since the event has been triggered via e-mail for the last time, an episode of the "warning event" will be activated to inform the person in charge of the connection interruption.
Event settings
Text / Images / Audio
