All workflow definitions need decision capabilities and will be delegated to some subsystem or external system.
I think decisioning is orthogonal enough to workflow (BPMN or SWF) that we shouldn't be too worried, as long as it is not coupled in any way and fully optional. Also, the complexity (or technical burden) introduced by any integration is probably not at a level that I think anyone needs to be overly concerned. Or at least we should ensure that any decision capability is optional, for the end-user, and the implementation is not creating any long term burden. I don't believe the proposal is going against anything I've said here. I do agree that I'm not sure DMN as a format is the best fit for SWF, and I know Matteo did some POC work showing a format that was more aligned. However, that work isn't available yet and is currently paused; we need to pick it back up again. In the meantime, as long as it's kept optional I have no concerns if there is community demand for DMN with SWF Mark On Mon, 15 Apr 2024 at 16:01, Tibor Zimányi <tzima...@apache.org> wrote: > Hi everyone, > > I noticed multiple discussions on Zulip and also a PR opened (1) about > executing DMN from Sonataflow. I am opening this thread (because I didn't > notice one), so we can discuss, if we want to do it. First of all, I want > to write, I am not against it. I just want us to be completely sure, that > it is what we want to do. Because from my perspective, it opens multiple > other discussions about the KIE workflow portfolio. One of them could be, > why we have two workflow engines in the KIE project, if we want to execute > all file types from everywhere (I read discussions on Zulip about DRL being > executed from Sonataflow too). It could imply, that we need a portfolio > consolidation and similar, because we are able to execute DMN and DRL from > the BPMN workflow engine. > > What are your opinions please? > > Best regards, > Tibor > > (1) https://github.com/apache/incubator-kie-kogito-runtimes/pull/3468 >
