Difference between Camunda 8 and 7

Hello, in my process, I have an action with a multi-instance that takes a list. I know that in Camunda 7, you can insert code in the execution listener to, for example, process a specific number of items from the list. However, I’ve seen that in Camunda 8, there is no execution listener. I wanted to ask if there is an alternative solution. Thank you very much for your help.

@anon64962691 , Camunda 8 doesn’t support delegation code or listeners, you need to handle it in separate activity like service task, etc.

1 Like

Hello, thank you. So, can’t we just write a condition in the sequence flow, or do we need a service action ?

If we’re talking about an exclusive gateway, you still can (and actually have to) model the conditions on the outgoing sequence flows.
The main difference between Camunda 7 and 8 (apart from the implementation of the engine itself) is, that you can only run it in a remote setup. This was actually already a possible setup with Camunda 7 and had nearly the same implications.
This means you cannot run the engine embedded and therefore there is no support for execution listeners or transactional behavior of the delegation code (as mentioned above).

I understand. In my process, I don’t have an exclusive gateway. What I want to convey is that before entering a sequentially multi-instance task, regardless of how many entries are in a list, only the first 5 entries in the list should always be processed. Is there a more efficient way to solve this in Camunda 8? I just wanted to ask if this could be done without a service task."

Okay. You can do that e.g. by using a feel expression with sublist for your input variable

Or you could also use a script task

Thank you so much. With the substring it worked.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.