Message (Input Agent)
This Input Agent is used to receive messages from the internal message bus. See also section MessageService.
It subscribes to a so-called Consumer Queue. A consumer queue is defined by a "Message context" and a "Message queue". As soon as data is sent to the subscribed Consumer Queue, it is received by the Input Agent and a job is started.
If multiple profiles listen to the same Message Queue, it is random which Input Agent accepts the data. Normally, unambiguity is achieved by setting the profile name when sending the message. If, however, you specify the profile name in a "Message" Response with a variable and the variable is empty at runtime, this is not the case.
Settings
(1) Existing queues: An existing queue (with context) can be selected. (2) and (3) will automatically be filled in.
(2) Message context: The message context of the message queue.
(3) Message queue: The name of the message queue.
In general, thematically matching profiles (about half a dozen at most) should be organised in their own context/queue.
A recipient profile with Input Agent Message also receives the variable values from the sender profile. To be able to receive the value of a variable of the sender profile, e.g. var__transfer, a variable with the same name and the prefix MSG_CALL_ must be defined in the recipient profile. So in this case MSG_CALL_var__transfer.
Note: In order to also have those variable values in the receiver profile available for a restart, the option Keep input information must be set in the extended settings of the receiver profile.