Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.13.5.GA, IBM BAMOE 8.0.5.GA
Affects Version/s: 7.13.2.GA
Component/s: jBPM Runtime UI
Labels:
- bamoe-verified
Environment:

RHPAM 7.13.2

Blocked:
False
Blocked Reason:
None
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.13.5.GA
Steps to Reproduce:
Hide

Build and deploy the kjar using the attached project.

Note: The process contains only a human task node.

Start it through
POST/server/containers/{containerId}/processes/{processId}/instances

Abort it through
DELETE/server/containers/{containerId}/processes/instances/{processInstanceId}

Open the diagram from business-central.

Actual result

You would see the human task node is still marked as RED.

Expected result

Human task node is highlighted as a current node - BLUE.
Show
Build and deploy the kjar using the attached project. Note: The process contains only a human task node. Start it through POST /server/containers/{containerId}/processes/{processId}/instances Abort it through DELETE /server/containers/{containerId}/processes/instances/{processInstanceId} Open the diagram from business-central. Actual result You would see the human task node is still marked as RED. Expected result Human task node is highlighted as a current node - BLUE.
[QE] How to address?:
---
[QE] Why QE missed?:
---
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Links:

A customer created a process instance and then they aborted it using the Rest API:
/server/containers/{containerId}/processes/instances/{processInstanceId}

They found that for the same application, one bpmn flow is working as expected (current node ) and the other bpmn flow is displayed as a stuck node with RED color and the process instance with an "aborted" stage. They're suspecting that the issue is reproducible on the flows which have an async event node.