The following API changes were introduced in Ignition version 7.6.0.

New Alarming System

The alarming system has been completely reworked in 7.6. Alarms are now executed centrally, through the AlarmManager provided in the gateway context. This new manager allows you to access the state and history of alarms, subscribe to events, and create new alarms.

Change in terminology: "Alerting" -> "Alarming"

To align better with industrial standards, the term "alarming" is now preferred for the core features in this version of Ignition. "Alerting" generally refers to alarming that is specific to a particular operator's preferences and settings. Therefore, the term may be used occasionally, but this version of Ignition doesn't offer any particular "alerting" features by this definition.

Alert Bus removed

The alert bus previously was the mechanism by which different parts of the system received alert events. This system has been removed. Now, if a sub-system is interested in alarm events, it can subscribe through AlarmManager#addListener. That method, which takes a new QualifiedPath, subscribes to everything at or below the path. Therefore, a system can subscribe to all events by passing a null or empty path

Pipelines & Notification Profiles

Alarm notification is now handled through the powerful and dynamic pipeline system. The actual notification is handled through the AlarmNotificationProfile extension point type, meaning that modules can implement new types of notification.

Global Project

There is a new "project" available through ProjectManager#getGlobalProject for resources that apply to the entire system. This new global project is used like other projects, the only difference being that the resources are shown in the designer regardless of the individual project being edited.

Extensible Expression Functions

Modules can now add functions to the expression language through the ExpressionFunctionFactory passed into the new configureFunctionFactory(...) function on module hooks.

Drivers now conform to the standard ExtensionPoint pattern

The driver system has changed quite a bit in order to remove unnecessary sub-patterns and adhere more closely to the design of other parts of Ignition. Driver module authors will need to adapt their code. The following are the key changes:

Authentication Profiles have become User Sources


Upgraded Platform Libraries