Auto Task Designer: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
This document can now be found at its new location in the [https://docs.hornbill.com/servicemanager-config/customize/service-manager-auto-tasks Hornbill Document Library]. | |||
[[file:hornbill-document-library.png|Auto Tasks|link=https://docs.hornbill.com/servicemanager-config/customize/service-manager-auto-tasks]] | |||
[[Category:HDOC]] | |||
<!-- | |||
<div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> | <div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> | ||
__NOTOC__ | __NOTOC__ | ||
{| style="width:100%" | {| style="width:100%" | ||
|[[Main Page|Home]] > [[Administration]] > Auto Task Designer | |[[Main Page|Home]] > [[Administration]] > Auto Task Designer | ||
|style="text-align:right;"|[[:Category: | |style="text-align:right;"|[[:Category:Configuration|Index]] | ||
|} | |} | ||
</div> | </div> | ||
| Line 10: | Line 16: | ||
|style="width:73%"| | |style="width:73%"| | ||
== Introduction == | == Introduction == | ||
The Auto Task Designer lets you define and build processes that can then be executed from custom button's on entity views from within Hornbill apps. Auto Task processes start | The Auto Task Designer lets you define and build processes that can then be executed from custom button's on entity views from within Hornbill apps. Auto Task processes start, execute and end, there is no concepts of stages, tasks, approvals or other nodes which would suspend a process. | ||
|style="width:5%"| | |style="width:5%"| | ||
| | | | ||
| Line 78: | Line 84: | ||
:* '''Start''' | :* '''Start''' | ||
::The Start Node indicates the starting point of the workflow | ::The Start Node indicates the starting point of the workflow. | ||
:* '''[[Hornbill Automation|Hornbill Automation]]''' | :* '''[[Hornbill Automation|Hornbill Automation]]''' | ||
| Line 93: | Line 99: | ||
:* '''[[Custom Expression Builder|Decision]]''' | :* '''[[Custom Expression Builder|Decision]]''' | ||
::These nodes can be used after a number of other nodes including | ::These nodes can be used after a number of other nodes including Automated tasks where multiple outcomes are possible. The Decision node can be used to facilitate the drawing of multiple outcome lines to other nodes, and for each outcome to be individually set. It is also possible to join decision nodes, to other decision nodes through the use of a '''No Match''' outcome. This caters for situations where multiple outcomes per decision are needed and not simply the three which are available from a single decision node. | ||
:* '''End''' | :* '''End''' | ||
:: | ::The Process will end. | ||
:* '''Abort''' | :* '''Abort''' | ||
::This node will end the workflow | ::This node will end the workflow. | ||
:* '''Start Parallel Processing''' | :* '''Start Parallel Processing''' | ||
| Line 142: | Line 148: | ||
==Groups== | ==Groups== | ||
A | A Process has the possibility of having a large number of nodes which can result in a very busy and difficult to follow workflow. A Group feature is available that allows you to group together a number of nodes which can then be minimized and viewed as a single Group container. The nodes within the Group can be displayed again by maximizing the Group container. | ||
:* '''Create a New Group''' | :* '''Create a New Group''' | ||
| Line 154: | Line 160: | ||
:* '''Locking a Group''' | :* '''Locking a Group''' | ||
:: When a group is unlocked, moving the group box over nodes will automatically add the nodes into the group. Locking the group box will prevent the adding of nodes to the group if the group box is moved over nodes on the canvas. | :: When a group is unlocked, moving the group box over nodes will automatically add the nodes into the group. Locking the group box will prevent the adding of nodes to the group if the group box is moved over nodes on the canvas. | ||
Latest revision as of 20:37, 5 June 2024
This document can now be found at its new location in the Hornbill Document Library.
