Description of problem: * This Bugzilla is raised for incorporating the following related feature requests in the future releases of BPMS 6.x . - Currently it is not possible for "WorkItemManager.abortWorkItem()" to pass parameters upon it's call. It can prove useful in scenarios like calling to "taskService.fail(..)" to pass on information like reason for the task to fail. ~~~ Right now a call to taskService.fail(task.getId(), "john", params); leaves no way to access params because they are not passed if work item was aborted (e.g. HT was failed). But it would be nice if we would be able to use the params in this case to e.g. specify why the task was failed. ~~~ The following "Feature Request" JIRA [1] captures this request in Community. - If the aforementioned request is incorporated it would be also good if we could have a dedicated variable like "TaskStatus" or "ExistStatus" to give users the access to the status of the Task when it is completed/failed etc. ~~~ It would be great if you could add a variable like "TaskStatus" or "ExitStatus" that contains the exit status of a HumanTask (e.g. "Completed", "Failed", "Error", "Exited", "Obsolete") lifecycle. Could be done the same way as "ActorId" is implemented to contain the actor for the completed task so that it can be assigned to a process variable. ~~~ The following "Feature Request" JIRA [2] captures this request in Community. [1] https://issues.jboss.org/browse/JBPM-4394 [2] https://issues.jboss.org/browse/JBPM-4393 Version-Release number of selected component (if applicable): - BPMS 6.0.2 How reproducible: - This is just a Feature Request and the features requested here do not exist in current release. Steps to Reproduce: 1. Not Applicable 2. 3. Actual results: - Not Applicable Expected results: - Not Applicable Additional info: - Not Applicable