[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration option component
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3021:
---------------------------------------
Attachment: (was: enumaration-component.png)
> [DMN Designer] Data Types - Constraints - Enumeration option component
> ----------------------------------------------------------------------
>
> Key: DROOLS-3021
> URL: https://issues.jboss.org/browse/DROOLS-3021
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> - When "Enumeration" is selected in the Constraints dialog, the following component must be loaded in the dialog;
> !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
[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration option component
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3021:
---------------------------------------
Description:
- When "Enumeration" is selected in the Constraints dialog, the following component must be loaded in the dialog;
!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.
was:
- When "Enumeration" is selected in the _Base Component_, the _Enumeration component_ must be loaded;
- The _Enumeration component_ is an input that creates "tags" when the user presses "Enter", the UI component must look like this:
!enumaration-component.png|thumbnail!
- The field (for creating a tag), must show the appropriated widget for each type of data (Number, Day/Time Duration, Year/Mos Duration, Date/Time, Date, Time);
- When the user clicks in a tag, it must be removed.
- When the user clicks in the Data Type "Save" button, the values (tags) must be persisted in the Data Type.
> [DMN Designer] Data Types - Constraints - Enumeration option component
> ----------------------------------------------------------------------
>
> Key: DROOLS-3021
> URL: https://issues.jboss.org/browse/DROOLS-3021
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: enumaration-component.png
>
>
> - When "Enumeration" is selected in the Constraints dialog, the following component must be loaded in the dialog;
> !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
[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 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.
was:
- When "Range" is selected in the Constraints dialog, the following component must be loaded in the dialog;
!prototype.png|thumbnail!
- The component contains 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.
> [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 in the dialog;
> !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
[JBoss JIRA] (WFCORE-4274) SuspendResumeTestCase fails sometimes
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFCORE-4274?page=com.atlassian.jira.plugi... ]
Yeray Borges reassigned WFCORE-4274:
------------------------------------
Assignee: Yeray Borges
> SuspendResumeTestCase fails sometimes
> -------------------------------------
>
> Key: WFCORE-4274
> URL: https://issues.jboss.org/browse/WFCORE-4274
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 8.0.0.Beta2
> Reporter: Richard Opalka
> Assignee: Yeray Borges
> Priority: Major
> Fix For: 8.0.0.Beta3
>
>
> [INFO] Running org.wildfly.core.test.standalone.suspend.web.SuspendResumeTestCase
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.076 s <<< FAILURE! - in org.wildfly.core.test.standalone.suspend.web.SuspendResumeTestCase
> [ERROR] testSuspendResume(org.wildfly.core.test.standalone.suspend.web.SuspendResumeTestCase) Time elapsed: 1.046 s <<< FAILURE!
> org.junit.ComparisonFailure: expected:<SUSPEND[ED]> but was:<SUSPEND[ING]>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.wildfly.core.test.standalone.suspend.web.SuspendResumeTestCase.testSuspendResume(SuspendResumeTestCase.java:116)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
--
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 component contains 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 have a specific component:
!future.png|thumbnail!
was:
- 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
> [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 component contains 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 have a specific component:
> !future.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3020) [DMN Designer] Data Types - Constraints - Expression option component
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3020?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3020:
---------------------------------------
Comment: was deleted
(was: A comment with security level 'Red Hat Employee' was removed.)
> [DMN Designer] Data Types - Constraints - Expression option component
> ---------------------------------------------------------------------
>
> Key: DROOLS-3020
> URL: https://issues.jboss.org/browse/DROOLS-3020
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: edit-decision.png, expression-component.png
>
>
> - When "Expression" is selected in the Constraints dialog, a textarea 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!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[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:
-----------------------------------
Labels: drools-tools (was: )
> [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 reassigned DROOLS-3019:
------------------------------------------
Assignee: Daniel José dos Santos (was: Guilherme Carreiro)
> [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 in the dialog;
> !prototype.png|thumbnail!
> - The component contains 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
[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 component contains 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.
was:
- When "Range" is selected in the Constraints dialog, the following component must be loaded in the dialog;
!prototype.png|thumbnail!
- The component contains 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 have a specific component:
!future.png|thumbnail!
> [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 component contains 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
[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:
---------------------------------------
Story Points: 3 (was: 5)
> [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 in the dialog;
> !prototype.png|thumbnail!
> - The component contains 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