Create and execute work
Create a task
Section titled “Create a task”- Open Tasks and choose the available create action.
- Select an active Task Definition. For Queue work, select an active Queue that admits the Definition.
- Fill in the Subject, participants and properties offered by the form. Due date, Context and a Responsible may be required, optional or unavailable according to the Definition.
- Complete the configured Input Data and any Working Data you may edit.
- Save. The new task is Idle; creation does not start execution.
If a response is lost, use the offered retry/check action for that same request. Do not submit a second copy while the first outcome is unknown.
Read and update information
Section titled “Read and update information”Input Data describes the requested work; Working Data records information collected while performing it. Their fields and edit permissions are configured independently. A field can be visible without being editable.
Use the edit control beside a property to change it. If someone has changed the task, reload the current values and reconcile the edit. A Context link opens only an object you may access. Instructions, when configured, supplies the Definition’s current guidance and permitted bound files.
Perform the work
Section titled “Perform the work”Use Change state for actions available to you. Assignment and execution are separate: assigning a Responsible or Executor does not start work.
| Action | Result |
|---|---|
| Start | Starts execution when the current actor, transition and capacity checks allow it. |
| Stop / Return to Idle | Ends the current execution segment and returns the task to Idle. |
| Pause / Resume | Records a pause and resumes permitted execution. Supply a reason when requested. |
| Block / Resolve block | Records an impediment and its resolution under the configured authority. |
| Postpone | Keeps the assignment and defers work for the Definition’s fixed delay, consuming a permitted postponement attempt. |
| Complete / Cancel | Finishes the task with an allowed Outcome and the required information. Done is terminal. |
After a postponement expires, background processing returns the task to Idle. It does not start it. An allowed early-return action can return to Idle or return and start after the usual Start checks. A due date passing does not complete a task.
Completion checks both the transition and Outcome permissions, then evaluates the Definition’s requirements against current data. Correct the reported fields or unmet requirements before trying again.
Change participants
Section titled “Change participants”Authorized users can change Owner, Responsible or Executor through the task’s assignment actions. Changing the performer of running work can stop the current execution as part of the same command. A block is retained where the command requires it; the new performer starts explicitly. Reasons and previous assignments remain in History.
Deactivating a Worker or removing their user link does not silently remove assignments. The old session loses the affected authority. A dispatcher or Task administrator must explicitly reassign or release the work; relinking the user does not create another Start event.
Collaborate and inspect history
Section titled “Collaborate and inspect history”Use the configured collaboration surface for comments and files. Content may belong to the task or its Context, and the linked object’s access rules still apply. A task role does not grant unrestricted access to Context content.
History records assignments, state changes, property changes and completion. Reading a notification or acknowledging a signal does not change that working cycle or complete the task.