Has anyone figured out a way to export a DMN file from the Decision Table in Appian?
We want Appian to be the source of the rules, but we need the DMN model so we can execute the logic on another offline system which must get the same results as if it were run on Appian.
Appian claims it uses DMN, but doesn't actually supply the DMN model...which seems odd.
Thanks.
Discussion posts and replies are publicly visible
Thanks for the responses so far.It's really a pity because the core promise of DMN is portability, transparency, and standardization of decision logic across platforms. The idea is that a DMN model written in one tool should be executable in another, thanks to its standardized XML format and use of FEEL.So it appears Appian's limitation includes: - DMN implementation is not designed for portability. - It’s not compliant with full DMN XML export, so you can’t move your decision logic to another DMN engine like Camunda or Drools. - It’s tightly coupled with Appian’s object model and security framework.
Unfortunately this means if portability is important to you (as it is for us), it pushes you away from using Appian as a central business rules platform.
Appian probably made that decision because a Decision Table in Appian can reference objects which are not available outside the platform.
Above, you wrote about some offline system. Can you share more details about your greater use case?