Acquiring and Releasing Tasks

Task steps may be acquired by an operator if it has not already been acquired by another operator. Then, if required, an operator may release a task step so that it can be acquired by another operator.

Note: Operators must have authorization to perform certain actions in the Task List, which can be assigned to them in the Security Editor. They may, however, still view the contents in this area.

Setting Task Steps to be Acquired

Tasks can appear in more than one Task List. For this reason, workflows are automatically set up to ensure that the first request made that acquires a task step takes ownership of that task step until it is either completed or released. If two or more operators try to acquire a task at the same time, only one is able to start the task. Subsequent personnel receive a message stating that another operator has already acquired it. If more than one user is performing a preparatory task at the same time, such as filling in a form, the first operator to submit the form receives acknowledgment for having completed the task. In some circumstances, the task step is acquired as soon as data is entered in a form.

Task steps can be acquired in several ways, such as:
  • using the Jump, Cancel, or Manual Start features;
  • submitting or cancelling a form;
  • programmatically acquiring the step using the client method in the Forms Designer (not available in the mobile task lists); or
  • marking the subprocess to automatically acquire the task step, so that the first operator whose task list is populated with the task step will acquire it.