Loading...

XML

Word

Printable

Docs QE Status:
NEW
QE Status:
NEW
Steps to Reproduce:
Hide

Create process

start node -> exit node

Create simple Case

Create sub-process inside Stage and set ad-hoc autostart to true

Set Called Element property to already created process

Build and Deploy Case

Start new Case instance via REST API

Find Case definition id: GET services/rest/server/containers/ {containerId}/cases/definitions
## POST /server/containers/{containerId}
/cases/
{caseDefId}
/instances

Note, that these headers must be used when calling POST:
Accept: application/xml
Content-Type: application/xml

Open Diagram of Case Management instance

Go to Manage -> Process Definitions in business-central

Click on View Process Instances, click on existing instance

See log/diagram
Show
Create process start node -> exit node Create simple Case Create sub-process inside Stage and set ad-hoc autostart to true Set Called Element property to already created process Build and Deploy Case Start new Case instance via REST API Find Case definition id: GET services/rest/server/containers/ {containerId}/cases/definitions ## POST /server/containers/{containerId} /cases/ {caseDefId} /instances Note, that these headers must be used when calling POST: Accept: application/xml Content-Type: application/xml Open Diagram of Case Management instance Go to Manage -> Process Definitions in business-central Click on View Process Instances, click on existing instance See log/diagram

Completed case is still active in business central, it can be only Aborted to fully finish it.

Actual Result:
In Case log we can see that Case is COMPLETED, but in Process Instance view it is still shown as ACTIVE

Expected Result:
Case will be fully COMPLETED

The same behaviour applies also for Ad-Hoc processes.