January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3518) Propagate generic type info on DMO

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3518?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-3518: ------------------------------------------ To show the popup for collection editor, generic-type information of the collection are required > Propagate generic type info on DMO > ---------------------------------- > > Key: DROOLS-3518 > URL: https://issues.jboss.org/browse/DROOLS-3518 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > Propagate generic-type information from PackageDataModelOracleImpl to AsyncPackageDataModelOracleImpl so to have them available client-side -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3518) Propagate generic type info on DMO

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-3518: ---------------------------------------- Summary: Propagate generic type info on DMO Key: DROOLS-3518 URL: https://issues.jboss.org/browse/DROOLS-3518 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Propagate generic-type information from PackageDataModelOracleImpl to AsyncPackageDataModelOracleImpl so to have them available client-side -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3399) [DMN Designer] Data Types - Disable the global "Save" button when edit mode is enabled

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3399?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3399: --------------------------------------- Story Points: 3 (was: 2) > [DMN Designer] Data Types - Disable the global "Save" button when edit mode is enabled > -------------------------------------------------------------------------------------- > > Key: DROOLS-3399 > URL: https://issues.jboss.org/browse/DROOLS-3399 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: DROOLS-3399.png > > > Disable the global "Save" button (from the editor) when edit mode is enabled (in a Data Type): > !DROOLS-3399.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3517) [DMN Designer] Data Types - Constraints - Constraint property

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3517?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3517: --------------------------------------- Tester: Jozef Marko Story Points: 3 > [DMN Designer] Data Types - Constraints - Constraint property > ------------------------------------------------------------- > > Key: DROOLS-3517 > URL: https://issues.jboss.org/browse/DROOLS-3517 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > Currently the _Constraint dialog_ infers the {{Constraint type}} based on the value. > - A new property ({{kie:constraintType}}) needs to be added in the in {{itemDefinition.allowedValues}} element. See how the DMN file will look like: > {noformat} > <?xml version="1.0" ?> > <dmn:definitions ...> > <dmn:itemDefinition id="_C9B6988F-0302" name="tNum" isCollection="false"> > <dmn:typeRef>number</dmn:typeRef> > <dmn:allowedValues kie:constraintType="range" id="_F7A1878D-A464"> > <dmn:text>(1..200)</dmn:text> > </dmn:allowedValues> > </dmn:itemDefinition> > <dmndi:DMNDI> > <dmndi:DMNDiagram></dmndi:DMNDiagram> > </dmndi:DMNDI> > </dmn:definitions> > {noformat} > - Update the {{DataType}} class with the new property (from {{ItemDefinition.allowedValues}}); > - Use the new property in the {{DataTypeConstraintModal}} class to load the right component (instead of inferring the type). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3517) [DMN Designer] Data Types - Constraints - Constraint property

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3517?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3517: --------------------------------------- Description: Currently the _Constraint dialog_ infers the {{Constraint type}} based on the value. - A new property ({{kie:constraintType}}) needs to be added in the in {{itemDefinition.allowedValues}} element. See how the DMN file will look like: {noformat} <?xml version="1.0" ?> <dmn:definitions ...> <dmn:itemDefinition id="_C9B6988F-0302" name="tNum" isCollection="false"> <dmn:typeRef>number</dmn:typeRef> <dmn:allowedValues kie:constraintType="range" id="_F7A1878D-A464"> <dmn:text>(1..200)</dmn:text> </dmn:allowedValues> </dmn:itemDefinition> <dmndi:DMNDI> <dmndi:DMNDiagram></dmndi:DMNDiagram> </dmndi:DMNDI> </dmn:definitions> {noformat} - Update the {{DataType}} class with the new property (from {{ItemDefinition.allowedValues}}); - Use the new property in the {{DataTypeConstraintModal}} class to load the right component (instead of inferring the type). was: Currently the _Constraint dialog_ infers the {{Constraint type}} based on the value. A new property ({{kie:constraintType}}) needs to be added in the in {{itemDefinition.allowedValues}} element. See how the DMN file will look like: {noformat} <?xml version="1.0" ?> <dmn:definitions ...> <dmn:itemDefinition id="_C9B6988F-0302" name="tNum" isCollection="false"> <dmn:typeRef>number</dmn:typeRef> <dmn:allowedValues kie:constraintType="range" id="_F7A1878D-A464"> <dmn:text>(1..200)</dmn:text> </dmn:allowedValues> </dmn:itemDefinition> <dmndi:DMNDI> <dmndi:DMNDiagram></dmndi:DMNDiagram> </dmndi:DMNDI> </dmn:definitions> {noformat} > [DMN Designer] Data Types - Constraints - Constraint property > ------------------------------------------------------------- > > Key: DROOLS-3517 > URL: https://issues.jboss.org/browse/DROOLS-3517 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > Currently the _Constraint dialog_ infers the {{Constraint type}} based on the value. > - A new property ({{kie:constraintType}}) needs to be added in the in {{itemDefinition.allowedValues}} element. See how the DMN file will look like: > {noformat} > <?xml version="1.0" ?> > <dmn:definitions ...> > <dmn:itemDefinition id="_C9B6988F-0302" name="tNum" isCollection="false"> > <dmn:typeRef>number</dmn:typeRef> > <dmn:allowedValues kie:constraintType="range" id="_F7A1878D-A464"> > <dmn:text>(1..200)</dmn:text> > </dmn:allowedValues> > </dmn:itemDefinition> > <dmndi:DMNDI> > <dmndi:DMNDiagram></dmndi:DMNDiagram> > </dmndi:DMNDI> > </dmn:definitions> > {noformat} > - Update the {{DataType}} class with the new property (from {{ItemDefinition.allowedValues}}); > - Use the new property in the {{DataTypeConstraintModal}} class to load the right component (instead of inferring the type). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3492) Create UX proposal to show/edit Test Scenario (Preview) global setting

by tao zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-3492?page=com.atlassian.jira.plugi... ] tao zhu edited comment on DROOLS-3492 at 1/14/19 8:00 AM: ---------------------------------------------------------- Hi[~danielezonca] [~aglass] I have created a simple demo for this task, please have a review~ https://redhat.invisionapp.com/share/JSPYJVUMAB7 was (Author: zhutaojiajia): [~danielezonca] [~aglass] please have a review the demo of this task, https://redhat.invisionapp.com/share/JSPYJVUMAB7 > Create UX proposal to show/edit Test Scenario (Preview) global setting > ---------------------------------------------------------------------- > > Key: DROOLS-3492 > URL: https://issues.jboss.org/browse/DROOLS-3492 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXD, UXTeam > Attachments: 11unnamed.png, TestScenario_Cheatsheet.png, TestScenario_TestEditor.png, TestScenario_TestReport.png, TestScenario_whole.png > > > As user I want to be able to see/edit editor global settings. > For instance DMN file linked to the scenario or the Session name of a Rule scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3517) [DMN Designer] Data Types - Constraints - Constraint property

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3517?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3517: --------------------------------------- Description: Currently the _Constraint dialog_ infers the {{Constraint type}} based on the value. A new property ({{kie:constraintType}}) needs to be added in the in {{itemDefinition.allowedValues}} element. See how the DMN file will look like: {noformat} <?xml version="1.0" ?> <dmn:definitions ...> <dmn:itemDefinition id="_C9B6988F-0302" name="tNum" isCollection="false"> <dmn:typeRef>number</dmn:typeRef> <dmn:allowedValues kie:constraintType="range" id="_F7A1878D-A464"> <dmn:text>(1..200)</dmn:text> </dmn:allowedValues> </dmn:itemDefinition> <dmndi:DMNDI> <dmndi:DMNDiagram></dmndi:DMNDiagram> </dmndi:DMNDI> </dmn:definitions> {noformat} was: Currently the _Constraint dialog_ infers the {{Constraint type}} based on the value. A new property ({{kie:constraintTyp}}) needs to be added in the in {{itemDefinition.allowedValues}} element. See how the DMN file will look like: <?xml version="1.0" ?> <dmn:definitions ...> <dmn:itemDefinition id="_C9B6988F-0302" name="tNum" isCollection="false"> <dmn:typeRef>number</dmn:typeRef> <dmn:allowedValues kie:constraintType="range" id="_F7A1878D-A464"> <dmn:text>(1..200)</dmn:text> </dmn:allowedValues> </dmn:itemDefinition> <dmndi:DMNDI> <dmndi:DMNDiagram></dmndi:DMNDiagram> </dmndi:DMNDI> </dmn:definitions> > [DMN Designer] Data Types - Constraints - Constraint property > ------------------------------------------------------------- > > Key: DROOLS-3517 > URL: https://issues.jboss.org/browse/DROOLS-3517 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > Currently the _Constraint dialog_ infers the {{Constraint type}} based on the value. > A new property ({{kie:constraintType}}) needs to be added in the in {{itemDefinition.allowedValues}} element. See how the DMN file will look like: > {noformat} > <?xml version="1.0" ?> > <dmn:definitions ...> > <dmn:itemDefinition id="_C9B6988F-0302" name="tNum" isCollection="false"> > <dmn:typeRef>number</dmn:typeRef> > <dmn:allowedValues kie:constraintType="range" id="_F7A1878D-A464"> > <dmn:text>(1..200)</dmn:text> > </dmn:allowedValues> > </dmn:itemDefinition> > <dmndi:DMNDI> > <dmndi:DMNDiagram></dmndi:DMNDiagram> > </dmndi:DMNDI> > </dmn:definitions> > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration component

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3021: --------------------------------------- Sprint: 2019 Week 02-04 > [DMN Designer] Data Types - Constraints - Enumeration component > --------------------------------------------------------------- > > Key: DROOLS-3021 > URL: https://issues.jboss.org/browse/DROOLS-3021 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: future.png, prototype.png > > > - When "Enumeration" is selected in the Constraints dialog, the following component must be loaded; > !prototype.png|thumbnail! > - The component contains a dynamic list to insert the possible values > - The input is a simple input without any validation > This component must be made considering that in the future, each kind of data will support a specific component (see the following example considering {{date}}): > !future.png|thumbnail! > ⚠️ This JIRA does not comprehends the widget that appears in the {{future.png}} file. This JIRA comprehends the only what appears in the {{prototype.png}} file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3517) [DMN Designer] Data Types - Constraints - Constraint property

by Guilherme Carreiro (Jira)

Guilherme Carreiro created DROOLS-3517: ------------------------------------------ Summary: [DMN Designer] Data Types - Constraints - Constraint property Key: DROOLS-3517 URL: https://issues.jboss.org/browse/DROOLS-3517 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Carreiro Assignee: Daniel José dos Santos Currently the _Constraint dialog_ infers the {{Constraint type}} based on the value. A new property ({{kie:constraintTyp}}) needs to be added in the in {{itemDefinition.allowedValues}} element. See how the DMN file will look like: <?xml version="1.0" ?> <dmn:definitions ...> <dmn:itemDefinition id="_C9B6988F-0302" name="tNum" isCollection="false"> <dmn:typeRef>number</dmn:typeRef> <dmn:allowedValues kie:constraintType="range" id="_F7A1878D-A464"> <dmn:text>(1..200)</dmn:text> </dmn:allowedValues> </dmn:itemDefinition> <dmndi:DMNDI> <dmndi:DMNDiagram></dmndi:DMNDiagram> </dmndi:DMNDI> </dmn:definitions> -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[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: --------------------------------------- Sprint: 2019 Week 02-04 > [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: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: future.png, prototype.png > > > - When "Range" is selected in the Constraints dialog, the following component must be loaded; > !prototype.png|thumbnail! > - The component contains only two raw input fields and two dropdowns; > - The component should be able to store only the min value > - The component should be able to store only the max value > - The component should be able to store the mix and the max value > This component must be made considering that in the future, each kind of data will support a specific component (see the following example considering {{date}}): > !future.png|thumbnail! > ⚠️ This JIRA does not comprehends the widget that appears in the {{future.png}} file. This JIRA comprehends the only what appears in the {{prototype.png}} file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2019