[
https://issues.jboss.org/browse/DROOLS-2750?page=com.atlassian.jira.plugi...
]
Jozef Marko updated DROOLS-2750:
--------------------------------
Description:
As a citizen developer, I want to build my decision logic with as small effort as
possible. Especially I want to build the *valid* expressions with minimal interaction with
the designer. For this reason the designer should fill in default values/symbols into
cells where possible. This should help with DMN designer getting started experience.
In this epic we should discuss where is possible to fill some default values/symbols into
expression cells.
h3. Context
I think no appropriate default value exists. Maybe with exception of the last row?
h3. Literal Expressions
My proposal would be:
- empty cell, if it is valid value for literal expression cell, if not
- value according to the column data type, 0 for number, today for date ...
h3. Decision table
- symbol *-* due to trisotext samples
h3. Function
Really not sure
h3. Relation
Really not sure
h3. Invocation
Really not sure
[~manstis] [~tirelli] [~tari_manga] could you please put your thoughts into comments? I
filed this epic to follow agile process. Not saying something from description will
happen. However if we will agree on some default values we can then file separate tasks
for this epic. I f we agree it is not good idea, we will close the epic.
h2. Manual Acceptance test
Note: Proposed after discussion in this jira
- Autogonerated top level decision table, input is structure (/)
- Nested decision table, for example as context entry (/)
- Adding columns/rows (/)
was:
As a citizen developer, I want to build my decision logic with as small effort as
possible. Especially I want to build the *valid* expressions with minimal interaction with
the designer. For this reason the designer should fill in default values/symbols into
cells where possible. This should help with DMN designer getting started experience.
In this epic we should discuss where is possible to fill some default values/symbols into
expression cells.
h3. Context
I think no appropriate default value exists. Maybe with exception of the last row?
h3. Literal Expressions
My proposal would be:
- empty cell, if it is valid value for literal expression cell, if not
- value according to the column data type, 0 for number, today for date ...
h3. Decision table
- symbol *-* due to trisotext samples
h3. Function
Really not sure
h3. Relation
Really not sure
h3. Invocation
Really not sure
[~manstis] [~tirelli] [~tari_manga] could you please put your thoughts into comments? I
filed this epic to follow agile process. Not saying something from description will
happen. However if we will agree on some default values we can then file separate tasks
for this epic. I f we agree it is not good idea, we will close the epic.
h2. Manual Acceptance test
Note: Proposed after discussion in this jira
- Autogonerated top level decision table, input is structure
- Nested decision table, for example as context entry
[DMN Designer] Default cell symbols
-----------------------------------
Key: DROOLS-2750
URL:
https://issues.jboss.org/browse/DROOLS-2750
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Affects Versions: 7.9.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Priority: Minor
Labels: drools-tools
As a citizen developer, I want to build my decision logic with as small effort as
possible. Especially I want to build the *valid* expressions with minimal interaction with
the designer. For this reason the designer should fill in default values/symbols into
cells where possible. This should help with DMN designer getting started experience.
In this epic we should discuss where is possible to fill some default values/symbols into
expression cells.
h3. Context
I think no appropriate default value exists. Maybe with exception of the last row?
h3. Literal Expressions
My proposal would be:
- empty cell, if it is valid value for literal expression cell, if not
- value according to the column data type, 0 for number, today for date ...
h3. Decision table
- symbol *-* due to trisotext samples
h3. Function
Really not sure
h3. Relation
Really not sure
h3. Invocation
Really not sure
[~manstis] [~tirelli] [~tari_manga] could you please put your thoughts into comments? I
filed this epic to follow agile process. Not saying something from description will
happen. However if we will agree on some default values we can then file separate tasks
for this epic. I f we agree it is not good idea, we will close the epic.
h2. Manual Acceptance test
Note: Proposed after discussion in this jira
- Autogonerated top level decision table, input is structure (/)
- Nested decision table, for example as context entry (/)
- Adding columns/rows (/)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)