[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration component
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3021:
-------------------------------------
[~karreiro] I tried to use enumerations with comma inside and they are parsed differently between reopening.
h2. Before saving
!Screenshot from 2019-02-01 08-54-00.png|thumbnail!
h2. After saving
!Screenshot from 2019-02-01 08-55-19.png|thumbnail!
Used asset: [^enums.dmn]
> [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: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2019-02-01 08-54-00.png, Screenshot from 2019-02-01 08-55-19.png, enums.dmn, 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)
6 years, 9 months
[JBoss JIRA] (DROOLS-3420) Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3420?page=com.atlassian.jira.plugi... ]
Klara Kufova updated DROOLS-3420:
---------------------------------
Description:
SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
Later, ask [~Rikkola] to move it on upper framework.
*ADDITIONAL IMPROVEMENTS:*
# When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# Change *Choose DMN asset* to *Choose a DMN asset*.
# The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
# The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# The fields *Package*, *Source type*, and *Choose DMN asset* should be marked with *{color:red}*{color}* (required fields).
was:
SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
Later, ask [~Rikkola] to move it on upper framework.
*ADDITIONAL IMPROVEMENTS:*
# When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
# Change *Choose DMN asset* to *Choose a DMN asset*.
# The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
# The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty.
> Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget
> -------------------------------------------------------------------
>
> Key: DROOLS-3420
> URL: https://issues.jboss.org/browse/DROOLS-3420
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Minor
>
> SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
> Later, ask [~Rikkola] to move it on upper framework.
> *ADDITIONAL IMPROVEMENTS:*
> # When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
> # Change *Choose DMN asset* to *Choose a DMN asset*.
> # The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
> # The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty. -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
> # The fields *Package*, *Source type*, and *Choose DMN asset* should be marked with *{color:red}*{color}* (required fields).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-3592) Undo/Redo regression on right panel
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-3592:
----------------------------------------
Summary: Undo/Redo regression on right panel
Key: DROOLS-3592
URL: https://issues.jboss.org/browse/DROOLS-3592
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
After naming/renaming of header, undo/redo does not restore correctly the right panel status.
Start this ticket after merging of DROOLS-3242, DROOLS-3357, DROOLS-3466, DROOLS-3485, DROOLS-3568
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration component
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3021:
--------------------------------
Attachment: Screenshot from 2019-02-01 08-54-00.png
> [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: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2019-02-01 08-54-00.png, Screenshot from 2019-02-01 08-55-19.png, enums.dmn, 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)
6 years, 9 months
[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration component
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3021:
--------------------------------
Attachment: Screenshot from 2019-02-01 08-55-19.png
> [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: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2019-02-01 08-54-00.png, Screenshot from 2019-02-01 08-55-19.png, enums.dmn, 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)
6 years, 9 months
[JBoss JIRA] (DROOLS-3021) [DMN Designer] Data Types - Constraints - Enumeration component
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3021?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3021:
--------------------------------
Attachment: enums.dmn
> [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: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: enums.dmn, 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)
6 years, 9 months