For the list of all supported Decision Insight downloads and releases, see the Downloads page.

Triggers

Prerequisites

A node using Triggers will create a message on data update/creation. Thanks to Decision Insight Messaging System (DIMS) , this message can be used by the same node (ex: alarm use case) or transmitted to any other nodes (ex: cockpit architecture) (secure; reliable and fast)

To works in any application nodes, Triggers will need:

About Triggers

In Axway Decision Insight (DI), you can produce a message when an instance is  created or updated.

For example you can create a trigger that listen updates on a Payment entity. The trigger will broadcast a message every time:

  • a payment is created
  • a payment is updated (the amount of a payment is updated, the state of a payment has changed, ...)

For every message, you can query the state of the updated instance at the event instant.

Finally this message is sent through Axway Decision Insight Messaging System in a given topic. Each topic can be read by one or several routing contexts.

Access the Triggers screen

To access the Triggers screen in DI:

  1. On the main menu, click the Data Integration icon .
  2. On the left menu, under Automations click Triggers.

The Triggers menu is only displayed for user with the system integration permission.

Create a trigger

Details of the trigger (1)

Once you're on the trigger screen, to create a trigger, provide the following information:

  • The trigger name
  • The entity on which the trigger is based
  • The DIMS connector where the messages are pushed
  • The topic in the DIMS connector where the messages are pushed


The Entity can be edited only once. To use another entity, create a new trigger instead.

Define the trigger rules (2)

The trigger sends a message through DIMS whenever an instance of the specified entity is updated.

Use trigger rules to configure which instance updates you want to monitor:

  • Instance creation
  • Attribute update

Trigger rules are aggregated and their number is unlimited. 


If multiple monitored updates happened at the same instant, only one message is sent.

Configure the trigger query (3)

In this area, define all the information that will be queried each time your trigger detects an instance update.

By default, the instance of the entity will be present in the message, as well as the transaction time and the valid time when the update occurs.


All attributes are requested at the update instant.

It is possible to query attributes that belong to another entity by following a path with a simple cardinality. The path and the attribute are queried at the update instant.

If two attributes have the same name, it is possible to use a different alias in the result message in order to correctly diffenciate them.

By default, two attribute with the same name will have a number added at the end of their aliases.

Messages

Message Format

Messages that are queued in a DIMS topic are formatted in JSON along with the following data :

Data Syntax Returned objects

Transaction time

"transactionTime"

Transaction time where the instance has been requested.

Instance

"instance"

Instance UUID corresponding to the requested instance.

validTime

"validTime"

Instant when the instance has been requested as Readable.

anyValue

"anyValue"

Values that have been requested in the trigger with a given alias.

metadata

"metadata"

Map containing additional information.

metadata:recomputing

"metadata": { "recomputing": true/false }

Recomputing is set to true if the query is triggered by a recomputing else false.


Receive Messages

Messages are received by configuring a route which is listening to the DIMS connector.

Related Links