And this is my issue about Business Rule Task.
When I start process, it stopped at Business Rule Task.I passed the variables called “Temperature” and “Activity” when process started.
Camunda 7 and Camunda 8’s most fundamental difference is that Camunda 8 uses a new process engine - Zeebe. The engine is what executes the BPMN, but the DMN engine and modeler are more or less unchanged.
But as you’ve obviously noticed, there are something on how BPMN integrates with DMN. They both use business rule task as the integration point but how the output is death with is a big change. Zeebe uses JSON as it’s native data structure and C7 didn’t. This will actually end up making things a lot easier when returning variables back.
Thank you for your reply, as swift as a rocket.The problem I encountered is actually like this: I created a DMN, and I also deployed it to Zeebe. However, when my process runs, the Business Rule Task does not execute. I have some guesses: first, it might be that my DMN input is incorrect. Second, there might be a problem with my DMN deployment. Third, there might be an issue with my Zeebe. I am investigating, and now that I have provided more information, I hope you can help me analyze.
My DMN model designs two input variables just like shown in the picture about DMN. And I put variables called the same name into process as below code:
It seems I can only paste two links; I apologize as I’m really not familiar with the community, so I’ve posted them on my GitHub. If it’s not enough, I will provide more information.
Oh my friend, it seems my DMN indeed has issues; this website is really fantastic. It appears to have detected that there are undefined inputs in my DMN. Perhaps I should continue to work in this direction.
The model looks good to me, was able to get it working with one change.
The issue seems to be with decisionKey. You entered the name of the DMN file but not the ID. I’ve added screenshots of what i changed.
Oh,I’m so grateful for your reply! Without your hints, I might have spent much more time thinking. I didn’t expect the community’s response to be so fast, and my long-standing issue was resolved so quickly.