Resultset Saved trigger

The Resultset Saved trigger starts a dataflow automatically whenever a selected resultset is saved. Unlike the Resultset Changed trigger, this trigger does not check whether the data has changed: it is raised every time the resultset is saved, even if the stored data is identical to the previous version.

How it works

• The trigger is linked to a single resultset.
• A resultset is saved by another dataflow using the Save Resultset node.
• Every save action raises this trigger.
• No comparison or change detection is performed.

Configuration

Setting	Required	Description
Resultset	Yes	The resultset to monitor. The trigger is raised every time this resultset is saved.

When to use it

Use the Resultset Saved trigger when a dataflow should always react to a save action, regardless of whether the data has changed.

Typical use cases include:

• Chaining dataflows where every save should trigger follow-up processing
• Auditing or logging save events
• Forcing recalculation or redistribution of data
• Driving downstream processes that depend on save actions rather than data changes

Notes & behavior

• The trigger is executed every time the resultset is saved.
• Identical data still triggers execution.
• A dataflow can contain only one trigger.

Tips

• Use this trigger when change detection is not required.
• Prefer Resultset Changed if unnecessary executions should be avoided.
• Do not use the Save Resultset node in the same dataflow as this trigger, as this can cause an execution loop.