Modify Task logic

Allows to modify (update) task in other available process.

There are two required requirements for modifying tasks via Modify Task logic:

• task must be in node with Waiting for Callback or Set State logic
• specify correct task reference in Modify Task logic

Task reference can be specified with:

• any system parameter of the current process. For example, {{root.ref}} or {{root.task_id}}
• any other parameter of the current task {{parameter_name}}
• constant. For example, config, ref etc.

Nodes in the gray box are added automatically for error handling.

Basic settings

Process - selection of a process for copying from "tree of folders". It can be found by its name or its ID or using the {{conv_id}} (parameter of the task).

Reference - the reference of a new task that is created in another process.

New task reference can be specified by:

• any system parameter. For example, {{root.ref}} or {{root.task_id}}
• any other task parameter {{parameter_name}}
• constant. For example, config, ref etc.

Copy all parameters - this option gives a possibility to copy all parameters to a new task.

Parameters

Button + Add "key-value" adds new parameter

Key - parameter name
Value can be specified by:

• constant
• {{parameter_name}} from task which name will be pasted
• any system parameter of the current process. For example, {{root.ref}} or {{root.task_id}}

If Copy all parameters flag is enabled, it is not required to add new parameters.

Otherwise be sure to add at least one parameter.

Additionally

Alert when there is tasks queue

Critical amount of tasks in the node.

Learn more about how it works here.

Limit the time of the task in the node

Time interval value at which task will go further through process in case if Copy task logic does not reply.

Learn more about how it works here.

Synchronous callback

Synchronous callback - checking this box enables modification of tasks synchronously. It means that tasks will be updated sequentially - strictly one after another.
With that, only the tasks located in Waiting for Callback logic nodes are modified. Thus, if the specified task is located in any node of a type other than Waiting for Callback at the moment of Modify Task work, the task will not be modified and the system will display the corresponding error.

Modify Task operation in asynchronous and synchronous modes

In asynchronous mode (default), after receiving a task from the Corezoid API, the Modify Task node performs the following checks for the task:

1. Checking for the task in the system:
   It is performed to find out if there is a task with the specified Reference number in the system. If no such task is found in the system, the current task is discarded, and the Modify Task node proceeds to process the next task received from the Corezoid API;

2. Checking for the availability of a Waiting for Callback/Set State node:
   It is performed to find out if there is an available Waiting for Callback or Set State node, to which the task can be sent after the processing. If such node is unavailable at the time of the check, the task is moved to one of the waiting queues*. When a queue waiting interval elapses, the task is retrieved from the waiting queue and the checks are performed for it again;

3. Checking for the expected database response after Modify Task execution:
   It is performed to find out if the database responds in the expected manner. If the expected response is received, the modification of the task in the database has been successful, and the task is processed further. If the expected response is not received, the task is moved to one of the waiting queues*. When a queue waiting interval elapses, the task is retrieved from the waiting queue and the checks are performed for it again.

After passing through all the steps, the task is moved to Waiting for Callback or Set State target node and processed further.

Working in synchronous mode is similar to working in asynchronous mode, except that two additional operations (2 and 5) are performed on the task:

1. Checking for the task in the system;
2. Blocking the task processing for the Corezoid API;
3. Checking for the availability of a Waiting for Callback/Set State node;
4. Checking for the expected database response after Modify Task execution;
5. Unblocking the task processing for the Corezoid API.

Types of error

Internal system error when copying

Not found task

Incorrect parameters

Failed to convert parameter

Inactive process

Access is denied

Task size overflow

Duplicate modification of the task

No callback logic in node with the task