Difference between revisions of "Dynamic Task Calls"
From PresenceWiki
(2 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
− | + | [[file:dynamic_task_call_node.png]] | |
Dynamic Task Call Node causes task execution to be delegated to a dynamically referenced Task. Unlike a [[Nested Tasks|Nested Task]] the name of the task is evaluated at run time based on a variable or column name. In order to reference a dynamic Task its name ''must'' be unique in the Presence installation. If the name is ambiguous an exception will be raised at runtime. The exception to this rule is if all instances of the Task with the same name are [[Deprecated]] except for one. | Dynamic Task Call Node causes task execution to be delegated to a dynamically referenced Task. Unlike a [[Nested Tasks|Nested Task]] the name of the task is evaluated at run time based on a variable or column name. In order to reference a dynamic Task its name ''must'' be unique in the Presence installation. If the name is ambiguous an exception will be raised at runtime. The exception to this rule is if all instances of the Task with the same name are [[Deprecated]] except for one. | ||
− | + | [[file:dynamic_task_call.png]] | |
{{Actions}} | {{Actions}} |
Latest revision as of 16:01, 19 August 2015
Dynamic Task Call Node causes task execution to be delegated to a dynamically referenced Task. Unlike a Nested Task the name of the task is evaluated at run time based on a variable or column name. In order to reference a dynamic Task its name must be unique in the Presence installation. If the name is ambiguous an exception will be raised at runtime. The exception to this rule is if all instances of the Task with the same name are Deprecated except for one.
Task Elements : Action Task Elements : Dynamic Task Calls