Message Hub Event

Description

The Message Hub Event trigger allows a flow to be initiated when a particular event is published on the Unit4 Message Hub by a specified source system. The triggering event on the Message Hub can be a generic event type, or an Enterprise document.

Usage

Configuration

The example below shows the Message Hub Event trigger configured to listen to events for the Project document version 1.0 published by the u4bw source system.

Message Hub Event Config

Input

The image above shows the input parameters required to configure the Message Hub Event trigger. The following parameters are required:

A valid source system name
The message type (generic event vs Enterprise document)
The event or document name
The version

Note: If the message type is Event and the event (name/version combination) does not exist, it is created when the flow is saved.

For a list of available Enterprise document types and versions, see Unit4 Ontology.

Note: The trigger only receives events from the tenant where the flow is installed.

For the u4bw and u4erp source systems, when Document is selected as the Message Type, only the two most recent Enterprise document versions are displayed to prevent the selection of obsolete versions. If an older version was previously selected, a Deprecated warning will appear, indicating that the selected Enterprise document version is no longer supported.

For the Event message type and other source systems, all existing versions are displayed.

Output

The output is the content of the event message. Typically this is an Enterprise document that matches the given event type.