How to handle User Task status (Completed, Failed, Obsolete, etc) in a BPMN2 process after performing operations on a User Task ?
Issue
- When any operation is performed on a
User Task
e.g.failed
after making aREST 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 aUser Task
which might have (Completed
,Failed
etc.) after any operation is performed on aUser Task
, so that a flow can be designed to counter that. For an example, place anOR
gateway behind aUser 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.