Skip to main content
davidr0007
August 25, 2025
Question

Exporting Decision Table as DMN

  • August 25, 2025
  • 5 replies
  • 0 views

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.

5 replies

stefanhelzle0001
August 25, 2025

I do not know of a way to import/export DMN directly. Did you try to export a decision table like a normal application export and check the included XML?

davidr0007
August 25, 2025

It does not include the Decision Table in a DMN formatted XML file.

shubhama926776
August 25, 2025
Appian claims it uses DMN, but doesn't actually supply the DMN model...which seems odd.

Agree with you!
Appian uses DMN concepts/structure to design decision tables but does not support exporting the actual DMN model file.

Did you try to export a decision table like a normal application export and check the included XML?

The exported package cannot be read by other DMN engines or tools. It's Appian-to-Appian only.

davidr0007
August 25, 2025

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.

stefanhelzle0001
August 25, 2025

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?