BPM Human Tasks

From Hornbill
Revision as of 16:31, 14 December 2018 by Stevenb (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Home > Administration > Business Process Designer > BPM Human Tasks

Introduction

When creating a human task it is possible to define this in one or multiple languages, by default this will be English, however it is possible to create copies of the human task in any other languages enabled on your instance. This is a consideration where those who maybe assigned tasks are working in different languages, and they will receive the human task either in the default language or in the language defined in their profile if the human task is configured in the different languages.

Related Articles

BPM Human task info.png

Options

  • Display
This is simply the display name for the human task node in the business process designer, it will not appear on the human task
  • Title
This will appear as the title on the human task
  • Category
Set a category which will appear on the human task
  • Priority
Set a priority to indicate the priority of the task
  • Owner
The Owner is an important consideration, as they can be notified about the task in reminders, and will also have the ability to reassign the assignee if required. The Owner can be either a named user or a variable
  • User
Pick from a list of co-workers
  • Variable
In order to see see a list of possible variables like request owner, you will need to preceed the human task node with the Automated Task Node > Request Entity > Get Information > Request Details
  • Assign To
Choose who the human task will be assigned to, this can be a named user, group, role or variable.
  • User - Pick from a list of co-workers
  • Variable - In order to see see a list of possible variables like request owner, you will need to preceed the human task node with the Automated Task Node > Request Entity > Get Information > Request Details * Lifespan Settings
  • Role - This will be populated from the default roles and any custom roles defined on your instance. Any Users who are assigned the role will receive the human task, any notifications and will have the ability to complete the human task.
  • Group - This will be populated from the defined groups on your instance. Any Users who are members of the group will receive the human task, any notifications and will have the ability to complete the human task.* Task Details
  • Lifespan Settings - It is possible to set a start date, due date and expiry date for the task based on either a predefined value, or based on a variable like respond by or fix by from the parent request.
  • Start After - Set this to either X Days, X Hours and or X minutes after the creation of the Task, or base this on a variable like log date, resolve by, or fix by. If using the Variable option remember to preceed the node with the Automated Task Node > Request Entity > Get Information > Request Details
  • Due After - Set this to either X Days, X Hours and or X minutes after the creation of the Task, or base this on a variable like log date, respond by, or fix by. If using the Variable option remember to preceed the node with the Automated Task Node > Request Entity > Get Information > Request Details
  • Expires After - Expires is a valid outcome for a human task, and setting a value here will allow you to via a decision node following the task allow for branching based on an outcome not being selected but the task expiring.
Set this to either X Days, X Hours and or X minutes after the creation of the Task, or base this on a variable like log date, respond by, or fix by. If using the Variable option remember to preceed the node with the Automated Task Node > Request Entity > Get Information > Request Details
  • Task Details - Define the details for the human task, this can be a combination of text and if required variables from the parent request which the task is related too, this could be the summary or description fields, custom fields, or even answers to progressive capture questions - see more about inserting request variables here.
  • Task Options
  • Hide the completion Reason when completing the task - decide if the reason field is not required when completing the task via an outcome
  • Do not allow completion of the task unless it is 100% complete - this option becomes available if Checklists have been enabled on the task, and you do not want to allow the task to be completed whilst there are outstanding checklist items.
  • Decide if you want to display the Time Spent option to the user who is completing the human task
  • Manage Checklists - Optionally add checklists which need completing as part of the task
  • Outcomes - 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.
  • Capture Task Fields - Enable custom fields on the task
  • Set Stage Checkpoints - Optionally configure which stage checkpoints will be set on the completion of the task
Personal tools
Namespaces

Variants
Views
Actions
Navigation
Tools