A group of actions that operate on tasks, i.e. objects stored in the Ta table.
Create new
This action is used to create a new task in the system. This action cannot directly change the value of the fields in the task. If you need to change the value of a field in a document, you must use the Change field value or Copy field value actions. A typical scheme for creating a task with setting field values is described at the end of this article.
In order to create a new task, you must specify a number of parameters. You can select these parameters from the drop-down fields in the action configuration.
User ID: The indicated user will be recorded in the system as the person creating the task.
Type ID: The type of task. You can select the type directly or indicate the field on the form where the task type is stored.
Company ID: You can either select the company from the dictionary or indicate a field on the form that contains the company.
Return: In this field you can indicate the field from the form, from which the process is started, to which, after the task is created, the ID of the newly created task will be saved. In order to use the task ID in copy actions or change field values, you need to store it on the form from which you create the task, create a technical field of the integer type and use this field to store the value of the ID of the created task. This field does not need to be visible on the document type, but it is important that it is active.
Copy field value
This is a non-standard action that is used to copy values of form elements between different types of objects in the NAVIGATOR system. In the current version, it allows you to copy values between Documents and Tasks. It can be used to copy within one type (e.g. from Document to Document) or between types (e.g. from Task to Document). It can be found in a separate action category: Field: Copy Field Value, but since it is closely related to task management it is also mentioned in this article.
A detailed description of the action can be found in the System Actions document: Fields
Change field value
This action allows you to change the value of the fields on the form. You only have to provide the ID of the task you want to change and user ID, who is going to be recorded as the person who modified the field.
In order to change the value of a field you must select this field from the drop-down list. Remember that the form must match the form of the task, which you want to change and define an expression which calculates the change. The expression is in the form of a SQL query that works just like other queries of this type in the system. You can use SQL functions and parameters. You can choose system variables as parameters.
Typical usage of task creation actions
In the NAVIGATOR system, the actions of creating new tasks and changing the values of the fields in the task are separated. You can’t create a task with fixed values in one action. You have to use two or more actions that are executed sequentially. A typical pattern of action usage is as follows:
Step 1:
Create an integer type field that will be used to store the ID of the created task. This is a technical field, it does not have to be visible for the user. It is important that it is active on the document type.
Step 2:
Create a workflow procedure and add an action that will create a new task of the appropriate type. Remember to indicate our technical field in the Return field. This will ensure that the ID of the newly created task is written to the document.
Step 3:
In the workflow procedure, create an action where you configure an action to change field values or copy field values. In the configuration, you need to specify the ID of the task (changing values) or the ID of the target (copying values). In this field, you insert a reference to our technical field from step 1, where you stored the ID of the created document.
Step 4:
When copying field values, you can specify the system variable System field: document ID as the source object ID. This will ensure that the source of the values to change the fields will be the document from which you ran the procedure.
Step 5:
You configure the values of the fields you want to change.
It is worth noting that you can only change the values of the fields in one action or copy those values from one form. Therefore, if necessary, you should define several actions to be executed sequentially, e.g. Create Task > Change Field Values > Copy Field Values (Form1) > Copy Field Values (Form2). Such a sequence will allow you to create a new task based on values from different places in the system.
Delete
An action used to remove tasks from the system. Only two parameters are required: ID of the task to be deleted and ID of the user who is deleting the document.
