Triggering a Bridging Transaction

A transaction with no trigger runs only when someone explicitly requests it. To automate a workflow, you point the transaction to one or more triggers, an alarm subscription, or both. Triggers are configured centrally in Workbench under Actions > Triggers and can fire on a date and time pattern, a data value change, an alarm, a database change, a file or folder change, or a Windows event. Learn more

Execute on a Trigger

When several triggers are listed on one transaction, each one that fires requests its own instance, and those instances run in parallel. This is what lets a single transaction serve many assets—one trigger per asset, each applying its own global alias themes. Check the transaction's Transaction Options setting if you intend the instances to overlap, because some values of that setting allow only one instance at a time. Learn more

Before you begin, create the transaction you want to trigger, and make sure the GENESIS Triggers Point Manager service is running.

To trigger a transaction from a trigger tag:

Open Workbench and in Project Explorer, expand your project > Actions > Triggers, and add the desired trigger. For example, to add a date and time trigger that fires every hour, expand the Date/Time Triggers node, double-click Hourly to open the configuration, and complete the settings.
Expand Bridging > Transactions, and select the transaction you want to automate.
Open the Transaction Execution tab. Under Specify the list of tags that can trigger a transaction execution, click + Click here to add new item.

Click (Click to add multiple tags) to open Data Browser and select several trigger tags at once.
In the new row, do the following:
1. In Tag, click and browse to your trigger under Actions > Triggers.
2. Select Enabled.
3. (Optional) Select Override Global Alias and enter the Global Alias Themes that this trigger should apply, so that the same transaction can act on a different asset for each trigger. Learn more
On the Transaction Settings tab, confirm that The transaction is enabled is selected and then click Apply.
Verify the automation by watching the transaction run. The @@LastExecuted and @@LastExecutedStatus points of the transaction update on each execution. Learn more

Execute on an Alarm

A transaction can also subscribe directly to the alarm server and run when a matching alarm changes state. This is the right approach when the workflow needs the fields of the alarm itself, because the alarm's attributes are exposed to the diagram as trigger variables such as {{triggerVariable:SourceName}}. Learn more

To trigger a transaction from an alarm:

Select the desired transaction and open the Transaction Execution tab.
In Alarm Settings, select Trigger transaction using alarm source.
(Optional) Select Override Global Alias Themes and enter the Global Alias Themes to apply.
In Filter Expression, enter the condition that selects the alarms allowed to start the transaction—for example, an expression that matches only alarms above a severity threshold.

Only fields that belong to all of the alarm sources in the subscription can be used in the filter.
Open the Alarm Subscriptions tab and click + Click here to add new item. For each subscription, set the Tag of the alarm source, the Min. Severity and Max. Severity, and the Alarm Type.

Subscribing to an entire alarm server means every state change of every alarm it exposes starts a transaction. Subscribe to a specific area instead.
Select Click to configure fields and mapping to choose which server fields and virtual fields the subscription delivers to the diagram, and then click Apply.

Executing a Transaction on Demand

Every transaction also exposes an @@Execute point that starts it when a non-zero value is written to it. Browse for it in Data Browser under Bridging, and bind it to a button or a data entry object with DataEntry enabled to give an operator a manual start. Clients can also start a transaction—and supply parameter values—from the Bridging Viewer control. Learn more