Hello,
I face the following issue:
We are using CA Process Automation Service Pack 04.3.05 with two orchestrators. We also use Service Desk Manager 17.3.
There is a main-process (ID: 377745121), which is starting a detached subprocess (377745258). We are saving those hierarchic structures in a database. The detached subprocess is containing a manual task for our employees. So the subprocess is some time in waiting-state, while the main-process is running and listening for Finish-Events from the subproccess of him.
Furthermore there is a Change-Object in SDM. The main-process (ID: 377745121) is a result of setting this Change-Object in an active state.
If we like to discard this Change-Object we use a button in the frontend of SDM, which is also starting another process in SDM (Macro-function of SDM). The main-process gets aborted by some internal functions of SDM. And the new started process is for aborting the subprocesses.
In the processflow are webservice-functions which deliver the ROIDs of the subprocesses. But if I use this ID in the controlProcess-Webservice from PA, we get the following answer:
Die Aktion {0} für Prozess-ID "377745258" wurde in die Warteschlange gestellt. --> So the action got queued.If I check the subprocess-instance, the task-operator is "aborted", the errorhandler is active and the main-instance of this subprocess is "blocked". There is a screenshot in the attachments.
It is strange because it seems, that the controlProcess-call was able to abort the task but not the whole instance.
Thanks for help