Difference between revisions of "Outcomes"
Jump to navigation
Jump to search
| (6 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/workflows/human-task#outcomes Hornbill Document Library]. | ||
| + | |||
| + | [[file:hornbill-document-library.png|Human Task Outcomes|link=https://docs.hornbill.com/servicemanager-config/customize/workflows/human-task#outcomes]] | ||
| + | <!-- | ||
| + | |||
<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__[[Main Page|Home]] > [[Administration]] > [[Business Process Designer]] > [[BPM Human Tasks]] > Outcomes | __NOTOC__[[Main Page|Home]] > [[Administration]] > [[Business Process Designer]] > [[BPM Human Tasks]] > Outcomes | ||
| Line 6: | Line 11: | ||
|style="width:73%"| | |style="width:73%"| | ||
== Introduction == | == Introduction == | ||
| − | Configure what possible options the user completing the human task can choose from when completing the human task. By default two are provided, Completed and | + | Configure what possible options the user completing the human task can choose from when completing the human task. By default two are provided, '''Completed''' and '''Not Completed'''. |
|style="width:5%"| | |style="width:5%"| | ||
| | | | ||
| Line 17: | Line 22: | ||
==Add Outcomes== | ==Add Outcomes== | ||
| − | Add a new Outcome using the Add New option | + | Add a new Outcome using the Add New option: |
| − | + | * Define the outcome value, a display name, and if the user completing the task is required to provide a reason when selecting this specific outcome. | |
| − | + | * Optional provide the outcome a display colour and make the outcome available in multiple languages. | |
| − | + | * Apply Settings to save. | |
| + | |||
| + | ==Optional Outcome Capture Fields== | ||
| + | [[File:BPM_Task_Outcomes.png|right|400px]] | ||
| + | It is possible that you may have a need to record additional information against the chosen '''Outcome''' of a task. In order to do this you can enable '''Outcome Capture Fields''', and use these to add additional fields to capture additional information when a specific '''Outcome''' is chosen on a task. | ||
| − | ==Enabling Outcome Capture Fields== | + | ===Enabling Outcome Capture Fields=== |
in the admin console navigate to Home > System > Settings > Advanced and enable the following setting: | in the admin console navigate to Home > System > Settings > Advanced and enable the following setting: | ||
| Line 52: | Line 61: | ||
==Manage Outcomes== | ==Manage Outcomes== | ||
| − | Edit Outcomes - To edit any of the above values for an existing outcome click the edit icon next to the outcome you wish to edit | + | * '''Edit Outcomes''' - To edit any of the above values for an existing outcome click the edit icon next to the outcome you wish to edit |
| − | Delete an Outcome - To remove an outcome option click the trash can icon next to the outcome you wish to delete. | + | * '''Delete an Outcome''' - To remove an outcome option click the trash can icon next to the outcome you wish to delete. |
==Using Outcomes== | ==Using Outcomes== | ||
| Line 59: | Line 68: | ||
* Expiry Outcome - It is not required to add a specific expiry outcome, this will be automatically enabled if you have configured an Expires After in the lifespan settings. | * Expiry Outcome - It is not required to add a specific expiry outcome, this will be automatically enabled if you have configured an Expires After in the lifespan settings. | ||
* Using Outcomes and or outcome capture fields to branch in the business process - If you require different behaviour in your business process depending on the outcome of the human task or based on answers to capture fields tied to a chosen outcome, use a Decision node directly after the human task and use the outcomes defined in the task as the decision branch options. | * Using Outcomes and or outcome capture fields to branch in the business process - If you require different behaviour in your business process depending on the outcome of the human task or based on answers to capture fields tied to a chosen outcome, use a Decision node directly after the human task and use the outcomes defined in the task as the decision branch options. | ||
| − | + | --> | |
| − | [[Category: | + | [[Category:HDOC]] |
Latest revision as of 22:40, 29 May 2024
This document can now be found at its new location in the Hornbill Document Library.
