We should test the project continuously via Travis CI.

We are talking about cells.

AT:

• I can specify the expressionLanguage of an inputEntry
• I can specify the expressionLanaguage of an outputEntry
• Uses correct url for FEEL

Defaults:

• inputEntry: FEEL
• outputEntry: Juel
  (-input expressions: Juel)

Migrated from: https://app.camunda.com/jira/browse/CAM-4695

It must be possible to set the expression language for input and output entries (all cells of the table body, except annotations)
Questions to answer
How does the workflow look like to open a combo-box where you can set the expression-language (context-menu on the cell, where to open the popup, styling, ...)
Design an indicator for cells which have an expression language set
Ideally, the indicator can listen to events (e.g. is a node in the DOM), so that you can open the combo-box edit when clicking on it.

Migrated from: https://app.camunda.com/jira/browse/CAM-4839

• Release the dmn libraries in order (How to release a library)
  • dmn-moddle
  • table-js
  • dmn-js
• Update the examples in dmn-js-examples
  • bump used dmn-js version
  • perform clean/install and test
  • update screenshots in Github
• Write blog post
• Spread the word

• Release the dmn libraries in order
  • dmn-moddle
  • table-js
  • dmn-js
• Release the bower-dmn-js packaging
  • check if bundle can be used (test/app/index.html opens in browser)
• Update the examples dmn-js-examples
  • bump used dmn-js version
  • perform clean/install and test
  • update screenshots in Github
• Release bpmn-io-demo
• Write blog post
• Spread the word

Currently the import fails with a cryptic error message.

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://www.omg.org/spec/DMN/20151101/dmn11.xsd" id="definitions" name="definitions" namespace="http://camunda.org/schema/1.0/dmn">
  <decision id="decision" name="">
    <decisionTable id="decisionTable">
      <output id="output1" label="Result" name="result" typeRef="string" />
      <rule id="row-624115199-1">
        <outputEntry id="LiteralExpression_090256m">        <text></text>
</outputEntry>
      </rule>
    </decisionTable>
  </decision>
</definitions>

See camunda/camunda-modeler#163 for details.

see bpmn-io/diagram-js#116

Migrated from: https://app.camunda.com/jira/browse/CAM-4740

We'll eventually adopt our in-house solution with docdown.

spike

May not be required

Migrated from: https://app.camunda.com/jira/browse/CAM-4696

This is comparable to the properties panel behaviour.

It will also make the shortcut CTRL+S more intuitive for the user

Preferably by drag and drop

The code is not very DRY in a lot of places.

The input expression popup overlaps the header of the current column.
This is not ideal because the user looses the context.

AT:

• the input expression popup does not overlap the current column

Note: if the popup is placed to the right of the column (like the datatype popup) it might not always fit on the screen

Migrated from: https://app.camunda.com/jira/browse/CAM-4380

Similar to bpmn-io/bpmn-js#495 this would issues with async API usage restrictions.

See forum post.

Reproduce:

• open the contextmenu on a mapping or type cell (that are the gray ones in the header)
• click on the left or right caret to add a new clause

Expected:

• a new clause is added at the specified position

Observed:

• nothing happens

Hint:

• It is okay not to open the ContextMenu on these cells (and possibly the whole header)

We need to change the namespace to the correct one

We need to offer a conversion for old models in the camunda modeler

The behavior of pressing the enter key should be:

• enter only: sets the focus to the cell below the currently focused one
• enter+shift: sets the focus to the cell above the currently focused one
• enter+ctrl (option for mac): adds a new text line within the focused cell

This is the behavior observed in google docs and openoffice

Migrated from: https://app.camunda.com/jira/browse/CAM-4224

Release dmn-js

• Release the dmn libraries in order (How to release a library)
  • dmn-moddle
  • table-js
  • dmn-js
• Update the examples in dmn-js-examples
  • bump used dmn-js version
  • perform clean/install and test
  • update screenshots in Github
• Write blog post
• Spread the word

In the dmn-io UI I can change the variable name of the input expression result, which I than can use in the input entry expressions. The default is {{cellInput}} and the attribute is currently name {{camunda:output}} which will hopefully change (see CAM-4862).

The new attribute name is {{camunda:inputVariable}}

Issue migrated from: https://app.camunda.com/jira/browse/CAM-4863

AT:

• When editing a cell for a clause with datatype string and allowed values, I see possible options when clicking in the cell
• While typing, only matching options are displayed
• When only one option remains, it is added to the cell in a typeahead behavior

Migrated from: https://app.camunda.com/jira/browse/CAM-4081

AT:

• In the datatype input dialog, if the same allowed value is entered twice, the fields are highlighted to indicate a warning
• when closing an input dialog that contains duplicate values, discard the duplicate (only save string once)

Migrated from: https://app.camunda.com/jira/browse/CAM-4367

Similar to bpmn-io/bpmn-js#445 we should open a lightbox on project logo click rather than directly jumping to the bpmn.io website.

See original post for details.

The cells of a table with many columns should always have a minimum width. If the table is too wide for the container with the minimum width, it should be horizontally scrollable.

See https://app.camunda.com/jira/browse/CAM-5237

We should add proper linting to the project.

AT:

• there exists a documented example showing how I can restrict editing in the DMN table editor
• in the example I can only change
  -- allowedValues ("add a new customer status")
  -- change the value of inputEntries and output entries
  -- everything else cannot be edited

Migrated from: https://app.camunda.com/jira/browse/CAM-4204

Currently the dmn-js internal icons have the class icon-dmn icon-foobar. We should change that to dmn-icon-foobar to avoid collisions with other fonts.

When copying a row while in simple mode, columns that have a boolean datatype always show the dropdown as empty instead of showing the correct value.

• Check package.json of dmn.io repositories for dynamic dependencies (esp. to moddle, moddle-xml and diagram-js)
• Update package.json of dmn.io repositories with release version 0.1.0
• Update screenshots of examples
• Create tag and Release
  • dmn_moddle
  • table-js
  • dmn-js
  • dmn-js-examples
• Write release blog post (should contain gif, links to camunda bpm 7.4.0-alpha1 release post, demo page and github)
• publish live demo at camunda.org/dmn/demo
• publish blog post
• spread the word (twitter, mailing list)

With the context menu, I can create a copy of a rules (above, below or at end - same semantic like create new).

Reproduce:

• goto demo.bpmn.io/dmn
• make the page scrollable (e.g. by making the browser window small)
• scroll down vertically
• with the scrollen page, click on the input expression cell

Expected:

• Overlay is opened at the cell

Observed:

• Overlay is opened to far above the cell

Seems like the column dragging in dmn-js falsefully assumes there is always a row.

Reproduce:

• Create new DMN diagram at demo.bpmn.io/dmn/new
• Try to drag column
• Check console

The logged JavaScript error is:

app.js:1592 Uncaught TypeError: Cannot read property 'cloneNode' of null
    Drag.createDragVisual @ app.js:1592
    Drag.updateVisuals @ app.js:1493
    (anonymous function) @ app.js:1447

Use stringify for text and html concatening instead of brfs

• add ability to create a description attribute of DMN
• align display of description with hide/show details mode

• html2canvas may be worth a try.

It is easier to edit:

• boolean (checkbox)
• strings (no hyphens)

I can still enter more complex expressions

AT:

• allowed values can be set for input expression (both script and expression variants)
• It is available for all input types, not just for strings Just for Strings

It is currently not possible to create combined DMN+... fonts because of the fact that the dmn-js logo is hardcoded in styles/dmn-mixins.less.

Making it a mix-in would give users the ability to redefine it, overriding the default. I.e.

.dmn-js-logo() {
  text-decoration: none;
  display: block;

  &:after {
    .dmn-font;
    text-align: right;
    font-size: 3em;
    color: @dmn-primary;
    .transition(color .218s ease);
    text-decoration: none;
  }
 .icon-dmn.icon-dmn-js;
}

Not sure it could give us a better integration story.