How to handle User Task status (Completed, Failed, Obsolete, etc) in a BPMN2 process after performing operations on a User Task ?

Solution Unverified - Updated -

Issue

  • When any operation is performed on a User Task e.g. failed after making a REST API call like /task/{taskId]/fail [1] , what is the best way to handle that in the process ? It seems when a task is failed the process instance just continues as if nothing happened. There might be user requirements so that it might be required to access the reason for a User Task which might have (Completed , Failed etc.) after any operation is performed on a User Task , so that a flow can be designed to counter that. For an example, place an OR gateway behind a User Task to take a path if the task was completed or a different path if the task failed.
  • Is there a built in feature in jBPM 6 to achieve that goal or is there any better way to do this in general ? Can the task finish status be mapped to a process variable somehow, etc.?

[1] jBPMRemoteAPI

Environment

  • Red Hat JBoss BPM Suite (BPMS)
    • 6.0.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content