-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
Open Problems / Concerns (will be addressed by menge)
- We cannot set expression language everywhere (cf. tUnaryTest) it needs to be possile to use an arbitrary expression language everywhere
- Comma seperated lists of expressions (inputValues, outputValues)
- Extension Elements missing
Changes
- HTML Table style
- Href => Qname
- allowed values => input values & output values
- drop itemDefinitions
- Clarify: type references "camunda:string" or "feel:string"
New Features
- default output
–
Notes for sebastian.menski
- priority
- output order
- output values
- just do it
This is the controller panel for Smart Panels app
[CAM-4747] DMN 1.1 Issue
| Description |
Original:
Open Problems / Concerns (will be addressed by [~menge]) - We cannot set expression language everywhere (cf. tUnaryTest) - Extension Elements missing - Comma seperated lists of expressions (inputValues, outputValues) Changes - HTML Table style - Href => Qname - allowed values => input values & output values - drop itemDefinitions - Clarify: type references "camunda:string" or "feel:string" -- Notes for [~sebastian.menski] - priority - output order - output values - just do it |
New:
Open Problems / Concerns (will be addressed by [~menge]) - We cannot set expression language everywhere (cf. tUnaryTest) - Extension Elements missing - Comma seperated lists of expressions (inputValues, outputValues) Changes - HTML Table style - Href => Qname - allowed values => input values & output values - drop itemDefinitions - Clarify: type references "camunda:string" or "feel:string" New Features - default output -- Notes for [~sebastian.menski] - priority - output order - output values - just do it |
| Description |
Original:
Open Problems / Concerns (will be addressed by [~menge]) - We cannot set expression language everywhere (cf. tUnaryTest) - Extension Elements missing - Comma seperated lists of expressions (inputValues, outputValues) Changes - HTML Table style - Href => Qname - allowed values => input values & output values - drop itemDefinitions - Clarify: type references "camunda:string" or "feel:string" New Features - default output -- Notes for [~sebastian.menski] - priority - output order - output values - just do it |
New:
Open Problems / Concerns (will be addressed by [~menge]) - We cannot set expression language everywhere (cf. tUnaryTest) - Extension Elements missing - Comma seperated lists of expressions (inputValues, outputValues) - clauses have ids Changes - HTML Table style - Href => Qname - allowed values => input values & output values - drop itemDefinitions - Clarify: type references "camunda:string" or "feel:string" New Features - default output -- Notes for [~sebastian.menski] - priority - output order - output values - just do it |
| Description |
Original:
Open Problems / Concerns (will be addressed by [~menge]) - We cannot set expression language everywhere (cf. tUnaryTest) - Extension Elements missing - Comma seperated lists of expressions (inputValues, outputValues) - clauses have ids Changes - HTML Table style - Href => Qname - allowed values => input values & output values - drop itemDefinitions - Clarify: type references "camunda:string" or "feel:string" New Features - default output -- Notes for [~sebastian.menski] - priority - output order - output values - just do it |
New:
Open Problems / Concerns (will be addressed by [~menge]) - We cannot set expression language everywhere (cf. tUnaryTest) - Extension Elements missing - Comma seperated lists of expressions (inputValues, outputValues) Changes - HTML Table style - Href => Qname - allowed values => input values & output values - drop itemDefinitions - Clarify: type references "camunda:string" or "feel:string" New Features - default output -- Notes for [~sebastian.menski] - priority - output order - output values - just do it |
| Description |
Original:
Open Problems / Concerns (will be addressed by [~menge]) - We cannot set expression language everywhere (cf. tUnaryTest) - Extension Elements missing - Comma seperated lists of expressions (inputValues, outputValues) Changes - HTML Table style - Href => Qname - allowed values => input values & output values - drop itemDefinitions - Clarify: type references "camunda:string" or "feel:string" New Features - default output -- Notes for [~sebastian.menski] - priority - output order - output values - just do it |
New:
Open Problems / Concerns (will be addressed by [~menge]) - We cannot set expression language everywhere (cf. tUnaryTest) - Comma seperated lists of expressions (inputValues, outputValues) - Extension Elements missing Changes - HTML Table style - Href => Qname - allowed values => input values & output values - drop itemDefinitions - Clarify: type references "camunda:string" or "feel:string" New Features - default output -- Notes for [~sebastian.menski] - priority - output order - output values - just do it |
| Description |
Original:
Open Problems / Concerns (will be addressed by [~menge]) - We cannot set expression language everywhere (cf. tUnaryTest) - Comma seperated lists of expressions (inputValues, outputValues) - Extension Elements missing Changes - HTML Table style - Href => Qname - allowed values => input values & output values - drop itemDefinitions - Clarify: type references "camunda:string" or "feel:string" New Features - default output -- Notes for [~sebastian.menski] - priority - output order - output values - just do it |
New:
Open Problems / Concerns (will be addressed by [~menge]) - We cannot set expression language everywhere (cf. tUnaryTest) it needs to be possile to use an arbitrary expression language everywhere - Comma seperated lists of expressions (inputValues, outputValues) - Extension Elements missing Changes - HTML Table style - Href => Qname - allowed values => input values & output values - drop itemDefinitions - Clarify: type references "camunda:string" or "feel:string" New Features - default output -- Notes for [~sebastian.menski] - priority - output order - output values - just do it |