[bug]: flow_globals.process_id is overwritten when starting a new process in a service task

[Hegyvari]

Flows for APEX version

23.1 (latest)

Oracle Database version

19c

Oracle APEX version

19.2 and lower (unsupported)

Have you used the BPMN-Linter in Flow Designer to Validate your Diagram?

Yes

What happened?

We have a process with a service task. The service task will start "subprocesses" for the current process, which involves calling the flows engine flow_start. At this moment the subprocess will start running and overwrite the global variable with its own process id. Once it stops whatever it is doing we get back to the main process which uses flow_globals.process_id to set a value in a message receive event and the value will not be the running process id but the one belonging to the subprocess.

The uploaded image is the part of the process which I have described.

I guess I will save this global before running the flow_start and restoring it after, maybe this is what the engine should also do as a fix.

Steps to reproduce

No response

Expected behaviour

have the actual running process id in this global variable.

[rallen2010]

Hi Krisztian - could you send me a copy of the diagram, or at least a bigger part of it. Richard Flowquest.consulting. There are definitely some limitations to send task/message throw and receive task /message catch in 23.1....

[Hegyvari]

Hello, I fixed it by storing/restoring the global value around my call to flow_start. ***@***.*** The messaging is a red herring, don`t let it distract you. If you create a diagram with a service task, start a new process from the service task and log the value of the flow_globals.process_id after the service task you should be able to reproduce this (I think). Regards, Krisztian De : Richard Allen ***@***.***> Envoyé : jeudi 15 février 2024 17:26 À : flowsforapex/apex-flowsforapex ***@***.***> Cc : Krisztian Hegyvari ***@***.***>; Author ***@***.***> Objet : Re: [flowsforapex/apex-flowsforapex] [bug]: flow_globals.process_id is overwritten when starting a new process in a service task (Issue #703) Hi Krisztian - could you send me a copy of the diagram, or at least a bigger part of it. Richard Flowquest.consulting. There are definitely some limitations to send task/message throw and receive task /message catch in 23.1.... — Reply to this email directly, view it on GitHub<#703 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWQYO24UKK5GNRLNFLUHPEDYTYZLLAVCNFSM6AAAAABDKPIFQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBWGQ4DSOBTGA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>