-
The spec says, on page 113:
```
[1, 2, 3, 4][item > 2] = [3, 4]
[ {x:1, y:2}, {x:2, y:3} ][x=1] = {x:1, y:2}
```
And:
> The filter expression is evaluated for each item in list, and a list c…
-
22 testcases listed in the attached file InvalidTestCases.txt are defining the function invocation return type using the Information Item of the Business Knowledge Model. This is wrong.
The specif…
-
This decision table results in the following dmn after exporting:
When importing this resulted dmn the decision table looks as follows:
-
The "Edit String Expression" dialog does not work for large tables and more than a few options.
### How to reproduce
1. Load the attached file Example.dmn (from Example.zip) in Camunda Modeler
2. "…
-
Bruce and Simon raised the issue that it is impossible to test a function by itself. Currently you have to create a model that uses the function, and pass input and output to the model. It is not im…
-
In the future we might want to support more editors for DMN 1.1 elements. Therefore dmn-js should not have the decision table modeler as a property but a list of editors that can edit a specific eleme…
-
Includes removing import/saveXML API and changing import to only import decision table instead of definitions.
-
On import, the modeler should generate DI for decisions if no DI exists. This ensures users can smoothly migrate from _only tables in DMN_ to _tables + DRD in DMN_.
nikku updated
6 years ago
-
The the grammar file, the names of a qualified name are separated by "->":
```
QualifiedName
= head:Name tail: (__ "->" __ Name)*
{
return new ast.QualifiedNameNode(build…
-
__Tasks__
* [x] dmn-js is integrated and does not break the modeler
* [x] basic operations (change detection, switching between dmn-js and XML work