[JBoss JIRA] (DROOLS-3513) [DMN Designer] Literal expression boxes can not be changed in height
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3513?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3513:
-----------------------------------
Story Points: 3
Sprint: 2019 Week 02-04
> [DMN Designer] Literal expression boxes can not be changed in height
> --------------------------------------------------------------------
>
> Key: DROOLS-3513
> URL: https://issues.jboss.org/browse/DROOLS-3513
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Thomas Mantegazzi
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: image-2019-01-14-09-12-40-849.png
>
>
> If a more complex logic is inputed in a literal expression, it might be thate the literal expression becomes more than a few lines. At the moment it is not possible to resize the heignt of the literal expression box.
> !image-2019-01-14-09-12-40-849.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3019) [DMN Designer] Data Types - Constraints - Range component
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3019?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3019:
---------------------------------------
Attachment: future.png
prototype.png
> [DMN Designer] Data Types - Constraints - Range component
> ---------------------------------------------------------
>
> Key: DROOLS-3019
> URL: https://issues.jboss.org/browse/DROOLS-3019
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: future.png, prototype.png
>
>
> - When "Range" is selected in the Constraints dialog, the following component must be loaded in the dialog;
> !prototype.png|thumbnail!
> - The field is a simple textarea without any validation;
> - The constraint type and the value (form the input field) must be set in the Data Type.
> Prototype:
> !expression-component.png|thumbnail!
> - When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
> - The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
> - The constraint type, the min. and the max values must be must be set in the Data Type.
> h2. Acceptance Test
> h3. Default data type
> - Able to store just min
> - Able to store just max
> - Able to store both min and max
> - Max can not be lover than min and vice versa
> - Can not put string to where number expected
> - Try to put conflicting value into table cell
> h3. Custom data type
> - Min max ui input fields not visible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3019) [DMN Designer] Data Types - Constraints - Range component
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3019?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3019:
---------------------------------------
Attachment: (was: prototype.png)
> [DMN Designer] Data Types - Constraints - Range component
> ---------------------------------------------------------
>
> Key: DROOLS-3019
> URL: https://issues.jboss.org/browse/DROOLS-3019
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> - When "Range" is selected in the Constraints dialog, the following component must be loaded in the dialog;
> !prototype.png|thumbnail!
> - The field is a simple textarea without any validation;
> - The constraint type and the value (form the input field) must be set in the Data Type.
> Prototype:
> !expression-component.png|thumbnail!
> - When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
> - The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
> - The constraint type, the min. and the max values must be must be set in the Data Type.
> h2. Acceptance Test
> h3. Default data type
> - Able to store just min
> - Able to store just max
> - Able to store both min and max
> - Max can not be lover than min and vice versa
> - Can not put string to where number expected
> - Try to put conflicting value into table cell
> h3. Custom data type
> - Min max ui input fields not visible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3019) [DMN Designer] Data Types - Constraints - Range component
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3019?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3019:
---------------------------------------
Description:
- When "Range" is selected in the Constraints dialog, the following component must be loaded in the dialog;
!prototype.png|thumbnail!
- The field is a simple textarea without any validation;
- The constraint type and the value (form the input field) must be set in the Data Type.
Prototype:
!expression-component.png|thumbnail!
- When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
- The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
- The constraint type, the min. and the max values must be must be set in the Data Type.
h2. Acceptance Test
h3. Default data type
- Able to store just min
- Able to store just max
- Able to store both min and max
- Max can not be lover than min and vice versa
- Can not put string to where number expected
- Try to put conflicting value into table cell
h3. Custom data type
- Min max ui input fields not visible
was:
- When "Range" is selected in the Constraints dialog, the following component must be loaded in the dialog;
- The field is a simple textarea without any validation;
- The constraint type and the value (form the input field) must be set in the Data Type.
Prototype:
!expression-component.png|thumbnail!
- When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
- The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
- The constraint type, the min. and the max values must be must be set in the Data Type.
h2. Acceptance Test
h3. Default data type
- Able to store just min
- Able to store just max
- Able to store both min and max
- Max can not be lover than min and vice versa
- Can not put string to where number expected
- Try to put conflicting value into table cell
h3. Custom data type
- Min max ui input fields not visible
> [DMN Designer] Data Types - Constraints - Range component
> ---------------------------------------------------------
>
> Key: DROOLS-3019
> URL: https://issues.jboss.org/browse/DROOLS-3019
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: prototype.png
>
>
> - When "Range" is selected in the Constraints dialog, the following component must be loaded in the dialog;
> !prototype.png|thumbnail!
> - The field is a simple textarea without any validation;
> - The constraint type and the value (form the input field) must be set in the Data Type.
> Prototype:
> !expression-component.png|thumbnail!
> - When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
> - The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
> - The constraint type, the min. and the max values must be must be set in the Data Type.
> h2. Acceptance Test
> h3. Default data type
> - Able to store just min
> - Able to store just max
> - Able to store both min and max
> - Max can not be lover than min and vice versa
> - Can not put string to where number expected
> - Try to put conflicting value into table cell
> h3. Custom data type
> - Min max ui input fields not visible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3019) [DMN Designer] Data Types - Constraints - Range component
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3019?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3019:
---------------------------------------
Attachment: prototype.png
> [DMN Designer] Data Types - Constraints - Range component
> ---------------------------------------------------------
>
> Key: DROOLS-3019
> URL: https://issues.jboss.org/browse/DROOLS-3019
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: prototype.png
>
>
> - When "Range" is selected in the Constraints dialog, the following component must be loaded in the dialog;
> - The field is a simple textarea without any validation;
> - The constraint type and the value (form the input field) must be set in the Data Type.
> Prototype:
> !expression-component.png|thumbnail!
> - When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
> - The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
> - The constraint type, the min. and the max values must be must be set in the Data Type.
> h2. Acceptance Test
> h3. Default data type
> - Able to store just min
> - Able to store just max
> - Able to store both min and max
> - Max can not be lover than min and vice versa
> - Can not put string to where number expected
> - Try to put conflicting value into table cell
> h3. Custom data type
> - Min max ui input fields not visible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3019) [DMN Designer] Data Types - Constraints - Range component
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3019?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3019:
---------------------------------------
Attachment: (was: edit-decision.png)
> [DMN Designer] Data Types - Constraints - Range component
> ---------------------------------------------------------
>
> Key: DROOLS-3019
> URL: https://issues.jboss.org/browse/DROOLS-3019
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: prototype.png
>
>
> - When "Range" is selected in the Constraints dialog, the following component must be loaded in the dialog;
> - The field is a simple textarea without any validation;
> - The constraint type and the value (form the input field) must be set in the Data Type.
> Prototype:
> !expression-component.png|thumbnail!
> - When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
> - The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
> - The constraint type, the min. and the max values must be must be set in the Data Type.
> h2. Acceptance Test
> h3. Default data type
> - Able to store just min
> - Able to store just max
> - Able to store both min and max
> - Max can not be lover than min and vice versa
> - Can not put string to where number expected
> - Try to put conflicting value into table cell
> h3. Custom data type
> - Min max ui input fields not visible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3019) [DMN Designer] Data Types - Constraints - Range component
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3019?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3019:
---------------------------------------
Description:
- When "Range" is selected in the Constraints dialog, the following component must be loaded in the dialog;
- The field is a simple textarea without any validation;
- The constraint type and the value (form the input field) must be set in the Data Type.
Prototype:
!expression-component.png|thumbnail!
- When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
- The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
- The constraint type, the min. and the max values must be must be set in the Data Type.
h2. Acceptance Test
h3. Default data type
- Able to store just min
- Able to store just max
- Able to store both min and max
- Max can not be lover than min and vice versa
- Can not put string to where number expected
- Try to put conflicting value into table cell
h3. Custom data type
- Min max ui input fields not visible
was:
- When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
- The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
- The constraint type, the min. and the max values must be must be set in the Data Type.
h2. Acceptance Test
h3. Default data type
- Able to store just min
- Able to store just max
- Able to store both min and max
- Max can not be lover than min and vice versa
- Can not put string to where number expected
- Try to put conflicting value into table cell
h3. Custom data type
- Min max ui input fields not visible
> [DMN Designer] Data Types - Constraints - Range component
> ---------------------------------------------------------
>
> Key: DROOLS-3019
> URL: https://issues.jboss.org/browse/DROOLS-3019
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> - When "Range" is selected in the Constraints dialog, the following component must be loaded in the dialog;
> - The field is a simple textarea without any validation;
> - The constraint type and the value (form the input field) must be set in the Data Type.
> Prototype:
> !expression-component.png|thumbnail!
> - When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
> - The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
> - The constraint type, the min. and the max values must be must be set in the Data Type.
> h2. Acceptance Test
> h3. Default data type
> - Able to store just min
> - Able to store just max
> - Able to store both min and max
> - Max can not be lover than min and vice versa
> - Can not put string to where number expected
> - Try to put conflicting value into table cell
> h3. Custom data type
> - Min max ui input fields not visible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3019) [DMN Designer] Data Types - Constraints - Range component
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3019?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3019:
---------------------------------------
Summary: [DMN Designer] Data Types - Constraints - Range component (was: [DMN Designer] Data Types - Constraints - Simple range option component)
> [DMN Designer] Data Types - Constraints - Range component
> ---------------------------------------------------------
>
> Key: DROOLS-3019
> URL: https://issues.jboss.org/browse/DROOLS-3019
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: edit-decision.png
>
>
> - When "Simple" is selected in the _Base Component_, two fields (Min. and Max.) must be loaded in the _Base Component_;
> - The fields must have the appropriated widgets for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
> - The constraint type, the min. and the max values must be must be set in the Data Type.
> h2. Acceptance Test
> h3. Default data type
> - Able to store just min
> - Able to store just max
> - Able to store both min and max
> - Max can not be lover than min and vice versa
> - Can not put string to where number expected
> - Try to put conflicting value into table cell
> h3. Custom data type
> - Min max ui input fields not visible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2286) [DMN engine] Java Object in DMNContext not working properly with Filter function.
by Thomas Mantegazzi (Jira)
[ https://issues.jboss.org/browse/DROOLS-2286?page=com.atlassian.jira.plugi... ]
Thomas Mantegazzi closed DROOLS-2286.
-------------------------------------
Works fine thx.
> [DMN engine] Java Object in DMNContext not working properly with Filter function.
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-2286
> URL: https://issues.jboss.org/browse/DROOLS-2286
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.4.1.Final, 7.5.0.Final
> Reporter: Thomas Mantegazzi
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: FilterJohns.dmn, FilterOnObjectListBug.java
>
>
> When trying to evaluate a FEEL expression like:
> {code:java}
> personList[name = "John"]
> {code}
> by inserting into the _DMNContext_ a _Java Object_, the _DMN engine_ doesn't seem to be able to fetch the _name_ field from the object. This doesn't happen if instead of _Java Objects_ we insert a Map.
> While trying to debug, it seems that the problem is happening in the following method of _FilterExpressionNode_.
> {code:java}
> private void evaluateExpressionInContext(EvaluationContext ctx, List results, Object v) {
> try {
> ctx.enterFrame();
> // handle it as a predicate
> ctx.setValue( "item", v );
> // if it is a Map, need to add all string keys as variables in the context
> if( v instanceof Map ) {
> Set<Map.Entry> set = ((Map) v).entrySet();
> for( Map.Entry ce : set ) {
> if( ce.getKey() instanceof String ) {
> ctx.setValue( (String) ce.getKey(), ce.getValue() );
> }
> }
> }
> Object r = this.filter.evaluate( ctx );
> if( r instanceof Boolean && ((Boolean)r) == Boolean.TRUE ) {
> results.add( v );
> }
> } finally {
> ctx.exitFrame();
> }
> }
> {code}
> Also attatched java and DMN test files that showcases the issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months