GroupAlarm Changelog

Management and display of dynamically configurable objects. Rule-based alerts and conditional visualisations.

Secure real-time chat with end-to-end encryption: Now featuring improved message management, polls, reactions and enhanced user-friendliness.

If multiple alarms are active, the alarm monitor always switches to the alarm that was last modified. With this update, the monitor always displays the most recent alarm. If this is not desired, the split-screen view can be used.

Participants in an organization can be exported via CSV. Only the data that each participant has made available to administrators will be exported. The export is currently limited to 1,000 participants per export.

Information about the update to the Messenger within the GroupAlarm app.

When triggering tags, files keys can now also be specified.

To improve the configuration and monitoring of the IMAP trigger, new IMAP connections are now managed in the central connection manager.

The iCal export of your own calendar now contains the organiser including the organisation name. You can find the iCal URL for importing into other systems in the web app by clicking on your profile picture under "Events".

The Connection Manager now includes a native MQTT client. You can now connect MQTT-based devices and software directly, process incoming data in flows, and actively send messages back to brokers.

In the "Units Overview" and "Unit Feedback" monitor panels, you can now filter by the status of the units.

Alarm texts now automatically filter redundant URL components (https://, www.) and all path parameters. The text-to-speech output is restricted to the core domain (e.g., teams.microsoft.com) for improved clarity.

To ensure platform stability, GroupAlarm is introducing an initial API rate limit of 500 requests per minute. In the event of a block, you will receive an HTTP 429 response and can evaluate the Retry-After header.

You can now update the status and position of your units directly using dedicated Flow functions. This method is not only easier to set up, but also significantly faster and more reliable than using HTTP requests.

From now on, participants in new organisations will be alerted multiple times unless the organisational setting "Participants booked in an event can be alerted again" is deactivated.

Alarm templates can now be linked directly to tags without configuring a flow. The assigned templates are listed in the tag overview. For more complex logic, the tag trigger within the flows is still available.

Geofences in organizations can now extend up to 50 km.

The Cockpit App receives the "Trigger alarm" functionality from the Web App

Using flow triggers, organizations can react in real-time to changes in personnel readiness as soon as defined thresholds for labels are exceeded or fallen short of.

The "Participant list" panel shows the number of available participants and the coverage ratio for each label.

The new coverage metric indicates the actual availability of participants per label, relative to an individual minimum.

We fixed a bug where certain devices were triggered too late in specific configurations.

We have improved the e-invoice process (ZUGFeRD/X-Rechnung). The routing ID and order number can now be entered directly in the billing data.

Users who are authorised to edit participant labels can now also change the status of a pausable label in the cockpit.

Label Prioritization is no longer applied at the end of an alarm, but now occurs directly during the live alert process. This ensures a more efficient and faster alarm flow.

The new alarm preview function enables the exact simulation of configured alarm scenarios. This serves to validate complex rules that take into account availability, shift schedules and other time criteria.

Administrators can now not only assign pausable labels to participants, but also adjust their active status as required.

The external ID of the event has been added to the "Trigger alarm" function, so that it is no longer necessary to create an event in advance and then trigger the alarm in it.

Freely definable comments allow for more precise feedback from the alerted persons in addition to the YES/NO answers.

We're introducing a quota of 5,000 emails per month per organisation.

The severity levels for alarms can now be found in the Configuration → Alerting menu item, along with the alarm comments, and no longer in the organisation settings.

The "Load alarm data" and "alarm closed" functions now also provide the names of the participants in the feedback as well as the absolute feedback numbers to forward this feedback via Flow. The absolute feedback values are also available via the API.

With the first trigger in the new „Automatic tasks“ extension, up to five cronjobs can now be defined and used per organization.

To improve clarity, units can now be assigned to their own categories.

The GroupAlarm Cockpit is now also available for Windows and macOS.

The GroupAlarm Cockpit is now available in your web browser without installation at cockpit.groupalarm.com.

Multiple events can now be selected simultaneously (up to 50) and closed or archived in one step.

The status “Alarmed” can be set automatically for alarmed units/vehicles so that they can be displayed on the monitor, for example.

We have added the severity to the event name of the pager, which is now - if set - prefixed to the event.

The Cockpit app displays the status and location of units, available participants, and the incident log.

In addition to the quick actions, units can now also be flexibly selected and alerted using the cockpit app.

We now hide alarm data in the iOS app when a screenshot is taken. The familiar warning is also displayed.

Ongoing events can now be renamed using the API when a new alarm is triggered.

The new GroupAlarm Cockpit replaces the GroupAlarm QuickActions app with immediate effect.

The input forms have been optimised to focus on writing new entries

Wildcards in the filter help to quickly bind a large number of units to organizations. This is useful, for example, with the WDX3 interface, so that alarms only reach the relevant organizations.

We fixed a bug where a person was counted multiple times in multiple alarms when reporting the event's strength.

A new data type “Output as JSON” allows objects extracted from JSON to be further processed as such, e.g. when passing them via HTTP within another JSON string.

We have improved the documentation of the API interface createAlert. You can now check the available options within the optional content.

If a shift group is without participants (i.e. because of empty shift plans or paused labels), it will be skipped directly in future regardless of the configured waiting time.

900 characters are now available for sending messages to the F.R.E.D. pagers in the flow element "Send message to pager".

The GroupAlarm Trust Center provides information about our certifications, memberships, key subcontractors and implemented policies (trust.groupalarm.com).

A new flow trigger "Position change", which reacts to position changes of units, has been added.

The Unit Feedback panel has new filters, e.g. filter options by unit, name and sorting of entries.

The alarm monitor now displays the organizations involved in the alarm in a new panel, including alerted units and positive feedback.

Descriptions can now be added to individual flow functions for better documentation.

The reload interval for the I-Frame panel on the monitors is now adjustable so that the page is not reloaded every minute, causing an unsightly effect on the monitor.

Track the availability of individual pagers over a longer period of time.

You can now select the invoice format yourself between PDF, XRechnung and ZUGFeRD in GroupAlarm. You can find the setting in the billing section under invoice recipient.

To ensure the continued security and efficiency of our services, we are deactivating insecure protocols and removing rarely used APIs.

Flows can now be marked as private when inherited, so that no data (insights) can be viewed in the sub-organizations.

Participants can now access certain profile functions directly via the app, e.g. the pausable labels or the email notification when they accept an alert (for employers or similar).

The information on the alarm monitors is now provided in real time without periodic reloading (SSE).

Pauseable Labels are now available in the F.R.E.D. menu

We are introducing a filter for units so that WDX3 messages only show up in the associated organizations.

We implemented a new e-mail provider for data privacy reasons.

The strength report has been revised and displays the selected labels more clearly.

The connection manager organises and monitors the connection to third-party systems.

We are implementing freely configurable severities for events and alarms, which can be individually signalled in the apps.

GroupAlarm now sends reminders of upcoming appointments via app.

We have fixed a bug where participants with inherited permissions did not have access to newly created sub-organisations.

The layout of the quick actions on the organisation dashboard has been updated. In addition to improved behaviour on small screens, they can now be collapsed.

The document manager is now available to our customers as a new, powerful function that enables the centralised management of important documents and information.

New icons have been added to the quick actions. The larger selection ensures that the icons are better suited to different alarm scenarios.

Previously, only normal labels could be selected in the app when creating an alarm. With the new app versions, smart labels created in the organisation can now also be selected here.

The JSON parser in our Flows can now output lists instead of only single values.

It is now possible to update participant data via CSV. Previously, it was only possible to delete or update the data individually.

We have shortened the time in which a pager signals an open alarm after a new login. Open alarms are now checked and delivered immediately after logging into the system.

Old events and alarms can now be completely removed from GroupAlarm.

With this update, we are introducing a new beta feature: The automated email notifications.

We have introduced a new role that only authorises the assignment of labels to participants.

Simplify tag assignment to scenarios

If the pager is assigned to a participant, the participant name on the pager is now updated immediately. Previously, there was a waiting time of up to several hours.

From now on, we will automatically delete inactive organisations after three months.

GroupAlarm now supports the WDX-3 interface for connecting the ELS Cobra (ISE).

This update adds a chime and read aloud feature to the monitor.

GroupAlarm and the apps are now also available in French.

With this update, the monitor gets new layers, overlays and the option to display points of interest.

With this update, we update the existing DWD map layers and extend the layer selection with the addition of Weather warnings for inland lakes, Pollen hazard index, Lightning short-term forecast and Lightning density.

Immediately upon requesting an increased quota, 1000 executions are added so that (e.g. the flow) works again immediately.

Previously, organisations with inherited permissions were not available in the apps to trigger an alarm. This has been corrected so that all organisations authorised for alarm creation can now be selected.

With this update, we are improving the information in the alarm report.

The validity period of push notifications has been extended to 10 minutes. This means that alerts can be sent for longer in the event of short-term signal loss on mobile phones.

With this update we correct the behaviour of the externalEventID.

A new flow trigger "Status change", which reacts to status changes of units, has been added.

On the alarm display, the labels in the "Manpower report" panel are now displayed proportionally to the selected font size.

Other formats are now supported in addition to the GPS coordinate format.

In the participant list, it is now directly visible on which devices an alarm will be sent to a participant.

To make it easier to manage the participants in the shift schedules, the shift groups now also support synchronization with labels.

Set the general availability of a participant via the FRED pager.

Administrators can now configure the settings of the FRED pagers directly in GroupAlarm.

The pager table supports searching and sorting by specific columns.

The Flow gets a component to decrypt pgp-encrypted text.

A flow is triggered when a deadman or emergency alarm is dispatched from a pager.

Participants can now select or deselect accordingly configured labels in their profile.

A new option in the organization settings now allows to shorten the SMS text including event name to 160 characters. Previously, this option was only available for sending the alarm text.

Each participant can now see in their personal profile which labels have been assigned to them in which organization.

From now on, displays can be activated and better managed with a password.

Organizations can now enforce two-factor authentication for new participants.

For one-off appointments, you can optionally set a feedback deadline. Once the date has been reached, appointment invitations can no longer be changed.

Until now, the changelog was only available in German - from now on it will also be available in English.