Human Task

Overview

A work step that humans are in charge of. Generates an input form (Operating screen) automatically in accordance with the editing permission settings on Data Items. When the allocated operator fills out the form and finishes the Task, the token advances. Capable of supporting multiple branch outputs which can be chosen by the Operator upon finishing the Task, and a deadline can also be set.

Editing Permission

Capture

Deadline

Capture

Notes

• Capable of setting a deadline
  • Deadline times are displayed in Case Details and Lists and can be specified as a filter condition
• If you specify anything other than [No Deadline], the default will be set to “1 day after” the target time such as [Token Arrival]
  • When specifying a Date-type Data Item, set it to “1 day after 00:00 of (Date-type) (24 hours later)”
    • This behaves the same as in Ver.16.2 and earlier, where “If a Date-type is assigned to [Deadline], it will work at 23:59 of the relevant day”
    • If you select [Blank] in the [After days] dropdown, the operation will start at 00:00 on the specified date
    • If the calculated deadline falls on or after “2101-01-01”, it will be forced to change to “2100-12-31”
• When you turn on [toggle_on Expression], the settings will be expressed in EL expressions
  • Advanced settings are also possible by editing the EL expression
    • Example: processInstanceStartDatetime.addMonths(1).getFirstTimeInMonth() (00:00 on the first day of the month following the Case Start Datetime)
• Capable of advancing the token when the deadline is reached

Split

Capture

Notes

• Each row (transition condition) can contain multiple conditional expressions for Data Items. In this case, the token moves to the destination only if all the conditions are satisfied. That is, multiple expressions are evaluated as AND conditions.
• You can specify the same destination step in multiple rows (transition conditions). In this case, the token moves to the destination if any of the conditions are satisfied. That is, multiple transition conditions are evaluated as OR conditions.
• Spring Expression Language (SpEL) can be specified in the Split Condition settings
  • This is an advanced feature for engineers
  • E.g. #q_string?.startsWith('[test]'), #q_datetime < #now.addDays(-1), etc.

Auto Processing / Error Handling

Capture

Notes

• Capable of automatically recording the Task Operator, Task finished time, and so on to Data Items
• If there is no user corresponding to the operator setting, the task becomes an Error Task
  • Possible to abort the Error Task and advance the token

Email Notification / Icon

Capture

Notes

• The Task Operator (or candidates) can be notified by email about the arrival of a Case, etc.

See also

• R2012: Limits on the Workflow App Definition
• Your first step of Questetra BPM Suite
  • Chpt.2: Creating Simple App
  • Chpt.3: Creating Travel Request App
  • Chpt.4: “Splitting” by Condition
• Tutorial: Understanding How to Use Split Conditions
• M202: Set the Deadline for Each Step
• M203: Parallel, Single Split and Multiple Split
• What is the Difference between [My Tasks] and [Offered]?
• Is There Any Way to Automatically Finish a Task in My Tasks?
• Timer Intermediate Event (Boundary Type)
• Intermediate Error Catch Event (Boundary Type)