Thank you for the quick response.
I have more task events because I wanted methods to be invoked based on some business data as a condition.
For example I have the following “On Queue” task events:
- taskEvent1 with no condition that invokes 2 services (List of Simple Actions)
- taskEvent2 with condition1 (ex: timestamp1 not empty) that invokes 1 service
- taskEvent3 with condition2 (ex: agent1 not empty) that invokes another service
If you say that having just one task event is more efficient, then I can certainly make only one.
I have 2 followup questions however:
Are the services specified in the “Action List” for a task event going to be executed in the order they are displayed there.
What is better: to have a task event that invokes one service with all the processing logic you need or to have a task event that invokes 2 or more services where you break the processing logic into chunks as you like.
Thank you for the answers.