FEEL playground: test DMN FEEL expressions online

An online tester for FEEL (Friendly Enough Expression Language), the expression language of the OMG DMN 1.6 decision standard. Evaluate FEEL and B-FEEL with a context for your variables. The interpreter runs in your browser, so nothing you type is sent anywhere.

loading engine…

Context: A FEEL context literal; the expression sees its entries as variables
Result
Language constructs and function library: click a name for full docs, or run its example directly

Test a FEEL expression before it goes into your decision table

Paste the expression, add the input data as a FEEL context such as {customer: {age: 34}}, and press Enter. You get the value this engine computes under DMN 1.6, or the error the engine reports when the expression does not parse. To debug an expression that returns null, change one part at a time until you find the input or path that causes it.

Use the FEEL / B-FEEL switch to compare the two dialects on the same input. A shared link opens the same expression, context and dialect, which helps when you ask a colleague or a forum why a rule misbehaves.

Need the details of a function? The FEEL function reference covers all 86 built-ins. Every example on those pages was computed by the engine that runs this playground.

FEEL reference

What is FEEL?

FEEL (Friendly Enough Expression Language) is the expression language defined by the OMG Decision Model and Notation (DMN) standard. It powers the conditions and outputs of DMN decision tables and literal expressions, and is executed by DMN decision engines and business rule platforms. FEEL is designed to be readable by business analysts while remaining precise enough for automated execution: it has first-class dates, times and durations, lists, contexts (structured records), ranges, and a rich built-in function library.

What is DMN?

Decision Model and Notation (DMN) is the OMG standard for modeling and automating business decisions: credit scoring, pricing, eligibility checks, routing rules. Decisions are modeled as decision tables and decision requirement diagrams; FEEL is the language used inside them. Decision table cells contain unary tests, conditions like < 10, [1..10] or value lists that are matched against the inputs. Because FEEL is a vendor-neutral OMG standard, an expression has the same meaning in every DMN engine that implements the same DMN version. Engines differ in which version and features they support. This playground evaluates FEEL as defined in DMN 1.6.

What is B-FEEL?

B-FEEL is the business-friendly dialect of FEEL introduced with DMN 1.6 (defined in chapter 11 of the specification). Standard FEEL propagates null through type errors, which can make a whole decision collapse to null. B-FEEL substitutes type defaults and converts mixed-type arithmetic, so decisions keep producing usable values: 1 + null yields 1, "total: " + 5 yields "total: 5", and 1/0 yields 0. This playground evaluates both dialects; use the FEEL / B-FEEL switch next to the expression input, or read every difference between FEEL and B-FEEL.

What is S-FEEL?

S-FEEL (Simple FEEL) is the restricted subset of FEEL the DMN standard defines for decision table cells: literals, comparisons, ranges and simple arithmetic, without functions or contexts. Every valid S-FEEL expression is also valid FEEL. A cell condition such as < 1000 has no value on its own, so test it with a value in front: 5 in < 1000 or 17 in [18..65).

How the playground works

The context editor below the expression supplies variables as a FEEL context literal; the expression sees its entries as variables, so customer.age * 2 works against {customer: {age: 34}}. Nothing is stored, so you can vary the context as often as you like to see how an expression behaves. The interpreter is a Java FEEL interpreter compiled to WebAssembly with GraalVM, and the syntax highlighting uses the interpreter's own lexer: what you see highlighted is exactly what gets parsed.

FAQ

How do I test a FEEL expression online?

Type it into the box at the top of this page and press Enter. If the expression uses variables, define them in the context editor as a FEEL context, for example {order: {total: 120}}. The result appears under the input. If the expression does not parse, you see the engine's syntax error message instead.

Why does my FEEL expression return null?

In standard FEEL, a type error does not raise an exception. It produces null, and null spreads through the rest of the expression: "total: " + 5 is null because you cannot add a string and a number. A mistyped path such as customer.agee is null too. Switch to B-FEEL to see the business-friendly result, or read how null works in FEEL.

What is B-FEEL?

B-FEEL is the business-friendly dialect of FEEL added in DMN 1.6. The grammar is the same. Where FEEL returns null for invalid input, B-FEEL returns a default: 1 + null gives 1 and "total: " + 5 gives "total: 5". See every difference.

Which DMN and FEEL version does it support?

FEEL as defined in OMG DMN 1.6, including all 86 built-in functions, the temporal types and B-FEEL. What changed between DMN 1.3, 1.4, 1.5 and 1.6 is listed on what changed in DMN 1.6.

Can I test decision table cells (unary tests)?

Yes. Write the cell as a test against a value, for example 17 in [18..65) or "gold" in ("gold", "silver"). The guide to unary tests and ranges shows every cell pattern.

Is my data sent to a server?

No. The FEEL interpreter is compiled to WebAssembly and runs in your browser tab. Expressions and context data stay on your machine. A shared link contains the expression and context in the URL, so do not share links that contain confidential data.

Is it free?

Yes. You can use it without signing up or creating an account.

What does FEEL stand for?

FEEL stands for Friendly Enough Expression Language. It is the expression language defined by the OMG Decision Model and Notation (DMN) standard, designed to be readable by business users while remaining precise enough for automated execution by decision engines.

Can I use these expressions in my DMN engine?

Yes. FEEL is a vendor-neutral OMG standard, so an expression is written the same way in every DMN engine that implements the same DMN version. Test it here, then paste it into your decision table or literal expression. Engines differ in which DMN version and features they support. B-FEEL and the newest built-in functions are part of DMN 1.6, so check which version your engine implements.

Who builds it, and which engine runs the expressions?

Nvaria GmbH, a Swiss consultancy for business process and decision automation. The engine is the Impulse FEEL interpreter, written in Java on GraalVM Truffle and compiled to WebAssembly. Syntax highlighting uses the same lexer, so what is highlighted is what gets parsed. More on the about page.

Engine: Impulse FEEL interpreter 0.9.1 (OMG DMN 1.6). Last updated .