nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Interflow Communication

mikebrown01

We have two flows that collaborate with each other. We have one process (Flow A) that progresses to a certain point and then
waits for a message from Flow B. Flow B sends a message to Flow A and then waits for a message back from Flow A.

An example is diagramed below.


Flow A:    

Start ———————–>   Message Catch Event ———————————->   Task ———-> End
                                                               /\                                                                                              |
                                                                |                                                                        sendMessage   |  
—————————————————————————————————————-  
                                                                |   sendMessage                                                                        |
                                                                |                                                                                               |
Start  —>  Parallel Gateway  —–>  Task  ———->   Parallel Gateway  ——> End                     |
                              |                                                                          /\                                                    |
                              |                                                                           |                                                     | 
                             +———-> Message Catch Event ———-+                                                     |
                                                                    /\                                                                                          |
                                                                     |                                                                                           |
                                                                    +————————————————-+
Flow B:

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

The problem with this, is even though the Message Catch Event (in Flow

is configured to always be set first,
the event is not yet in the database. So when Flow A tries to sendMessage to Flow B, it fails.

Is there a way to resolve this? Maybe there is a different way of handling flow interactions?

Find more posts tagged with

Comments

mikebrown01

Here is a link to an image for the flow since I failed at formatting in the original post.

<img>
https://s3.amazonaws.com/stuff.virtualbrown.com/FlowCom.2jpg
</url>

frederikherema1

The main issue is that your processes do NOT get persisted until they reach a wait-state. Since you're using script-tasks, these well be executed synchronously and the actual commit will happen later on. You can try making the script-tasks asynchronous, so the process-state is persisted right before they are executed.

Another question I have is about the start of the processes. In what order are they started, and how are they started?

mikebrown01

"The main issue is that your processes do NOT get persisted until they reach a wait-state"

ok. I thought that might be the issue here.

"You can try making the script-tasks asynchronous, so the process-state is persisted right before they are executed."

ok. Will give this a try.

"Another question I have is about the start of the processes. In what order are they started, and how are they started?"

Flow A is started before Flow B. Both flows are started programatically using runtimeService.startProcessInstanceByKey(…);

frederikherema1

Any chance of using a single process with a sub-process/call-activity? This might make things a bit more stable, although not 100% this would fit in the usecase you're trying to reach.

Try the async suggestion. If that doesn't work, maybe a detailed explanation of your use case might help…

mikebrown01

Ok setting the Task as Async is working! I had a little bit of a problem getting it to work because the JobExecutor was turned off in the config file :0