Some tasks are part of a process, but are not sequential in nature.
Typically, a process model can only have one start event, but can have multiple end events. All nodes in a process model should have an incoming flow with the exception of a Start event. Similarly, all nodes in a process model should have an outgoing flow with the exception of an End event.
Process Models that do not adhere to these rules are referred to as Quick Tasks.
A Quick Task is any attended activity that is activated and completed outside of fixed process flow. It can be enabled on any attended process activity (such as a User Input Task) or attended Appian Smart Service activities, by setting the Quick Task option on the activity properties.
Unlike regular tasks, a Quick Task can be activated without having been reached through the process flow. You can also add a Quick Task when editing a running process. Once activated, quick tasks can be run multiple times by all users permitted to complete them. Upon completion of a quick task, a new instance of the task is automatically generated, and all assignees can view and complete the Quick Task any number of times until the completion or termination of the process. To disable a quick task, set up an exception flow.
Quick Tasks that have been activated are displayed on the "Quick Tasks" tab of the Process Details view. This grid lists the task name, the date and time at which the task was enabled, and the users who have the right to view and complete the Quick Task. By default, the tasks displayed within the grid are sorted by Task Name in descending order, and this can be changed by selecting any of the column headers, upon which the data within the grid will be sorted by the corresponding column.
To view or complete a Quick Task, click the task name. After submission of a Quick Task, a new task instance is automatically generated and listed on the Process Details view. Quick Tasks that have not yet been activated do not appear on the Process Details view.
On This Page