Attachments

When processing a task, it may be necessary for the user to add one or more components. These documents are called task attachments and are globally defined by task class.

In order to perform actions on attachments, the following permissions may be required:

• Add attachment: CREATE for the component class to be created
• Update the content of an attachment: UPDATE_CONTENT for the component class to be created
• Delete an attachment: DELETE_CONTENT

Note: These actions are not possible if the attachment definition is read-only.

Answers

When a user has finished filling in the necessary information for a task, they can select an answer from among those proposed. These answers enable a workflow to move in one of the proposed directions.

To apply a response to a task, the APPLY_ANSWER permission is required.

Assignment

To edit a task, the user must:

• have the right to update the task: UPDATE
• be assigned to processing the task

In order to assign a user to process a task, several means are available. From a technical point of view, all you need to do is fill in the task’s assignee field with the identifier of the user, group or team to which the task is assigned.

Appropriation

Appropriating a task means assigning it to oneself. A task cannot be appropriated if it has not been assigned to a user, or to one of the logged-in user’s teams. This type of assignment requires the APPROPRIATE permission.

It is also possible to assign a task to yourself that has already been assigned to another user if you have the APPROPRIATE_ALREADY_ASSIGNED permission.

Assignment

Assigning a task to a user consists in assigning a task from user A to user B. This type of assignment can be made even if the task is already assigned to another user.

This type of assignment requires the ASSIGN permission.