AnsweredAssumed Answered

No activity id on execution with boundary event

Question asked by schalmers on Jun 23, 2011
Latest reply on Oct 3, 2012 by jbarrez

We have a process with a receive task. When we want to signal this we query for the execution using the process key, activity ID and a variable value which helps to uniquely identify the process.

Our problem is that when we added a boundary timer event to the receive task the query no longer works since the activity id is no longer set on the process.

We had expected that adding a boundary event would not require any changes to the query.

Please could you confirm if this is correct behaviour or a bug?