Second Possibility - Message and Trigger

If you are only interested in triggering the subsequent profile and not in transferring the output data of the triggering profile, the subsequent profile (this profile has to be active) can also have a time-driven Input Agent.

images/download/attachments/21303730/Profilkette_Trigger_EN-version-2-modificationdate-1551933797000-api-v2.png

It should be noted that the option Content in profile 1 must be set to Trigger profile (the encoding does not matter).

The following profile receives its data via the executed time-driven Input Agent. The type of the Input Agent does not matter. You only have to select option Trigger/External call and another profile on page Times.

Note: There is a special case in profiles with time-driven Input Agents. You can trigger a subsequent profile there in the same way, but 'hard-wired'. Please note that in this case, variables with prefix MSG_CALL_ cannot be accessed in triggered profiles (variables are not yet initialised in the triggering profile in phase 1, see also section Variables), unless the triggering profile is also triggered by another profile. Its MSG_CALL_ variables can then be passed through.