Jump to content

Runtime variables

Jack Adams

Recommended Posts


To make sure that the module is executed after the Runtime Variables task I would suggest you to add the Select Flow task that works as a kind of traffic light preventing the computation from continuing if all the tasks before it are not computed.





Flow computation will proceed only when both inputs (both the Data Manager and the Runtime Variables task) are correctly computed, so we can be sure that the Execute Rulex Flow File task is always executed next. Be sure to update the mapping in the Execute Rulex Flow File task, and define the input type in the Select Flow task.

Another solution could be exploiting priorities. If you right-click you can edit the priority on each task. Tasks with a higher priority value will be computed first. For example you can do this:


Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...