If one has a BusinessRuleTask and this task uses the asyncBefore flag then this is a wait-state. If the implemenation of the task is e.g. external then the mocked behavior can be defined by using waitsAtBusinessRuleTask.
In my situation the BusinessRuleTask is implemented by DMN, so actually there is no need to define any mocked behavior because DMN is execute by Camunda. But due to the asyncBefore flag camunda-platform-scenario is aborting and asks me to use waitsAtBusinessRuleTask for that task.
camunda-platform-scenario recognizes this special situation for BusinessRuleTasks using DMN as implemenation and does not ask to configure the scenario using waitsAtBusinessRuleTask.
Actual behavior
If one has a BusinessRuleTask and this task uses the
asyncBefore
flag then this is a wait-state. If the implemenation of the task is e.g.external
then the mocked behavior can be defined by usingwaitsAtBusinessRuleTask
.In my situation the BusinessRuleTask is implemented by DMN, so actually there is no need to define any mocked behavior because DMN is execute by Camunda. But due to the
asyncBefore
flag camunda-platform-scenario is aborting and asks me to usewaitsAtBusinessRuleTask
for that task.So, I need to add this
to make camunda-platform-scenario run through it.
Expected behavior
camunda-platform-scenario recognizes this special situation for BusinessRuleTasks using
DMN
as implemenation and does not ask to configure the scenario usingwaitsAtBusinessRuleTask
.