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.

de-coupling processes

wslade

I have a process that receives some data and stores it.
I have a second process that will determine if there is enough data and will then perform a task.

Currently I am using a "Call activity" to invoke the second process.
However I would like to de-couple the two processes. That is I would like process A to run to completion irrespective of process B.

Will message driven beans solve this and is it correct that they are not supported in the designer?

Or should I result to using a timer on process B?

Find more posts tagged with

Comments

trademak

What you could do is using a async call activity. Then the other process is started, but your first process will continue independently.

Best regards,

wslade

My requirement is for process A to run to completion.

If I mark the callable process as asynchronous then the current executing thread will complete and process B will start in a different thread.

However process A will be 'blocked' on the callable activity until process B runs to completion. Then process A will complete.

At least this is what I believe I observed in my test.

frederikherema1

Can't you signal process A from process B? or do you want to "block" the calling-thread that starts process A until process B is complete? If this is the case, the only way is a call-activity I'm afraid. If not, signaling from process B will do the trick…