[DmnServiceTask] dmn table key as expression

[martin-grofcik]

Problem description: Cmmn/Bpmn dmnService task does not define dmnTable as an expression. Dmn reference must be a reference to existing dmn model in the application. Partially related issue is: https://forum.flowable.org/t/modeler-dmn-reference-lost-after-bpmn-import/8598 In the case when dmn table is not recognized in export/import of the individual process/case model the information is lost because reference does not exist. In this case we can store the information in dmn table key.

Solution proposal: Adding a new property Decision table key for dmnService tasks in modeler with export/import.

Alternative: Add expression to dmn model popup.

[martin-grofcik]

@tijsrademakers, @jbarrez : Is the pull request OK? Can it be merged to master? Do you see any issue in it?

[tijsrademakers]

@martin-grofcik, what happens if you fill-in both the decision table reference and the decision table key? Also if we do this, then we should do the same for the decision service reference.

[martin-grofcik]

Hi @tijsrademakers,

there is a precedence:

        // When decision table key is present, can be still overridden by decision table/service references
        String decisionModelKey = getPropertyValueAsString(PROPERTY_DECISIONTABLE_REFERENCE_KEY_DEFINITION, elementNode);

and tests: modules/flowable-cmmn-json-converter/src/test/resources/test.dmnTaskModelReferencePriority.json

Decision table key has the lowest prio. Always overriden by table/service references.

[tijsrademakers]

Hi @martin-grofcik, ok that's fine. Then I think the missing part is to do it also for the decision service reference.