3.1 KiB
{% assign title = "Execution Started Event" %} {% assign definition = site.data.data_mine.execution_started_event %} {% assign preposition = "an" %} {% assign plural = "s" %}
{% if include.heading != "" %} {{include.heading}} {{title}} {% endif %}
{% if include.icon != "no" %}
{% if include.table == "yes" and include.icon != "no" %}
{% if include.more == "yes" and include.content == "more" %}
Click to learn more about {{ title | downcase }}{{plural}}
{% endif %}{% if include.content != "no" %}
These references determine when a process is due for another run. By listening to the execution finished event of the process it depends on, it may wake up just in time to process the new batch of data the dependency has just delivered.
Bots form a sort of multi-branched execution sequence with an indeterminate number of dependencies. Every time the bot further down the tree of dependencies finishes a cycle, it triggers the execution of multiple bots listening to its execution finished event.
{% endif %}
{% if include.more == "yes" and include.content != "more" %}
Click to learn more about {{ title | downcase }}{{plural}}
{% endif %}{% if include.adding != "" %}
{{include.adding}} Adding {{preposition}} {{title}} Node
To add an execution started event, select Add Missing Items on the process definition node menu. Items that may be missing are created along with the basic structure of nodes required to define them.
{% include tip.html content="Remember that an execution started event must establish a reference to the appropriate execution finished event." %}
{% endif %}
{% if include.configuring != "" %}
{{include.configuring}} Configuring the {{title}}
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
{% endif %}
{% if include.starting != "" %}
{{include.starting}} Starting {{preposition}} {{title}}
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
{% endif %}
{% if include.more == "yes" %}