You are using an intermediate condition catch event, which means that the process will stop there and wait for the condition to be evaluated. As far as I know conditions are not automatically evaluated. You’ll have to invoke RuntimeService#evaluateConditionalEvents to trigger the evaluation of the conditions.
Thanks , I tried in BPMN via skip feature and its working fine but wanted the same to be implemented the behavior in CMMN. Let me try to add RuntimeService#evaluateConditionalEvents and test.
Thanks @filiphr. Its working. Can I make some suggestion for the improvement
For BPMN Skip Tasks -> Can we have a checkout feature “Skip Enabled” in Flowable Modeler instead of creating variable " _ACTIVITI_SKIP_EXPRESSION_ENABLED " manually. This will avoid un necessary data generated in the HI_VARINST , RU_VARIABLE
For CMMN - Condition based task creation -> Any similar check box feature “Evaluate Conditional Events” in Flowable Modeler that will help to avoid writing this additional line of code
Hi , what is the solution please , i have already
execution.setVariable(“condition”,true);
runtimeService.evaluateConditionalEvents(execution.getProcessInstanceId());
but its does not working