Microflow invoking message consumer
Message consumer that passes incoming messages to a specified Mendix microflow.
Message consumer that passes incoming messages to a specified Mendix microflow.
The message is mapped to the input parameters of the microflow as follows:
- Any message header with the same name (after removal of illegal characters) and type (after conversion) as one of the microflow parameters, is passed using that parameter.
- If Payload parameter is not set, the message payload is not passed at all.
- If Payload parameter is set and Pass payload as path is disabled, the message payload is passed using Payload parameter(if the payload type can be converted).
- If Payload parameter is set and Pass payload as path is enabled, the message payload is stored in a temp file and the path to this file (a string value) is then passed using Payload parameter.
Any temp files that are created are only guaranteed to exist while the microflow is running. After execution, the file will be deleted.
Microflow
Microflow name, which must be an existing Mendix microflow
Payload parameter
Specify the microflow parameter that should be used for passing the message payload to Mendix. Leave empty to disable passing the payload as a parameter.
Default: empty
If set, the parameter must exist in the microflow. If 'pass payload as path' is enabled this parameter must be of type String, otherwise the type should be that of the (expected) message payload.
Execute in transaction
Specifies whether to execute the microflow in a Mendix transaction or not.
Default: true
Pass payload as path
If set, the message payload will be stored in a temp file and the path (as a string) will be passed to the microflow. Else the message payload will be passed directly to the microflow.
Channel
Channel to consume messages from.
Required
Id
Name that uniquely identifies this flow component.
Required