[JBoss JIRA] (DROOLS-3272) [DMN Designer] Data-type dialog: Improve support for adding multiple fields
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3272?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-3272:
---------------------------------------
based on the demo today from [~karreiro], as long as we add information on the UI about the keyboard shortcuts, we can close this ticket as resolved.
> [DMN Designer] Data-type dialog: Improve support for adding multiple fields
> ---------------------------------------------------------------------------
>
> Key: DROOLS-3272
> URL: https://issues.jboss.org/browse/DROOLS-3272
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> Requested by [~tirelli]
> {quote}
> When adding fields on the Data Types dialog, I would like to add multiple fields without having to click "add field below" after each one. Also, when I add a field, it shouldn't force me to click "edit" to set the name of the field.
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3484) Data type constraints: Date range Include/Exclude actions.
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3484?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3484:
-------------------------------------
[~karreiro] I created this jira so we can follow-up on your button idea, and also brainstorm any alternatives.
> Data type constraints: Date range Include/Exclude actions.
> ----------------------------------------------------------
>
> Key: DROOLS-3484
> URL: https://issues.jboss.org/browse/DROOLS-3484
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want the ability to define constraints for the Date data type, that enable me to specify if the start and end value is included/excluded in a selected date range.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3445) Data type constraints: Date
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3445?page=com.atlassian.jira.plugi... ]
Liz Clayton resolved DROOLS-3445.
---------------------------------
Resolution: Done
[~tirelli] [~karreiro] I'm marking this specific jira as resolved, but opened a new one specifically to address the range inclusion and exclusions: https://issues.jboss.org/browse/DROOLS-3484
> Data type constraints: Date
> ---------------------------
>
> Key: DROOLS-3445
> URL: https://issues.jboss.org/browse/DROOLS-3445
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3484) Data type constraints: Date range Include/Exclude actions.
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3484?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3484:
--------------------------------
Description:
Background
Persona: Business analyst or Rules practitioner
Use Cases:
As a user I want the ability to define constraints for the Date data type, that enable me to specify if the start and end value is included/excluded in a selected date range.
Verification conditions:
* Scrum team and PO review.
was:
Background
Persona: Business analyst or Rules practitioner
Use Cases:
* From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
* From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
Functional considerations/ pre conditions:
* Consider interaction in light of Property panel and consistency.
* Underscore the notion of one-off constraints.
Verification conditions:
* Scrum team and PO review.
> Data type constraints: Date range Include/Exclude actions.
> ----------------------------------------------------------
>
> Key: DROOLS-3484
> URL: https://issues.jboss.org/browse/DROOLS-3484
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want the ability to define constraints for the Date data type, that enable me to specify if the start and end value is included/excluded in a selected date range.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3484) Data type constraints: Date range Include/Exclude actions.
by Liz Clayton (Jira)
Liz Clayton created DROOLS-3484:
-----------------------------------
Summary: Data type constraints: Date range Include/Exclude actions.
Key: DROOLS-3484
URL: https://issues.jboss.org/browse/DROOLS-3484
Project: Drools
Issue Type: Story
Components: DMN Editor
Reporter: Liz Clayton
Assignee: Liz Clayton
Background
Persona: Business analyst or Rules practitioner
Use Cases:
* From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
* From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
Functional considerations/ pre conditions:
* Consider interaction in light of Property panel and consistency.
* Underscore the notion of one-off constraints.
Verification conditions:
* Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3445) Data type constraints: Date
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3445?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3445:
-------------------------------------
[~tirelli] [~karreiro] Given that the demo seemed to go well, I'm going to mark this jira as resolved and make a follow-up jira specifically to address the Include/Exclude element for the Range.
> Data type constraints: Date
> ---------------------------
>
> Key: DROOLS-3445
> URL: https://issues.jboss.org/browse/DROOLS-3445
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3474) Create HTML and CSS for List/Map data objects
by Amy Glass (Jira)
[ https://issues.jboss.org/browse/DROOLS-3474?page=com.atlassian.jira.plugi... ]
Amy Glass commented on DROOLS-3474:
-----------------------------------
[~srambach] It looks really good -- getting close!
[~zhutaojiajia] Regarding #7, I believe we need to allow the delete icon to remain visible so that the user knows the capability is there without having to discover it by hovering over that row. I checked with a couple of people on the patternfly team and this is their recommendation as well. This approach is typical and is used in a number of other places in our apps.
> Create HTML and CSS for List/Map data objects
> ---------------------------------------------
>
> Key: DROOLS-3474
> URL: https://issues.jboss.org/browse/DROOLS-3474
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Amy Glass
> Assignee: Sarah Rambacher
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Rectangle.png, firefox.png
>
>
> Provide HTML and CSS for the designs in Drools-3098.
> Will first provide HTML structure, and follow up with CSS styling.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (WFLY-11353) Classes for newer versions are not loaded from Multi-Release-JARs in WARs
by David Lloyd (Jira)
[ https://issues.jboss.org/browse/WFLY-11353?page=com.atlassian.jira.plugin... ]
David Lloyd commented on WFLY-11353:
------------------------------------
bq. Another potential workaround probably would be to rely on the JRE's system properties.
Unfortunately not; the trouble is that VFS is loading class resources in a different way than JarFile does (internally exploding the classes into a filesystem location (yes there's a good reason for this)), and thus it's VFS that needs to be fixed.
bq. But it may work, if the modules are loaded via the standard JRE classloader.
It will work, but not because of this. MR JAR handling is not actually directly related to the class loader at all; rather, it is a characteristic of JarFile. If I were to explode a WAR onto the file system, and use the same standard JDK URLClassLoader to load it, it would not behave in an MR JAR compliant fashion.
"Normal" non-WAR deployments do use JarFile (if I recall correctly; it would bear testing though); and, JBoss Modules' default resource loaders definitely use JarFile in the correct way to support MR JARs (this is thoroughly tested).
> Classes for newer versions are not loaded from Multi-Release-JARs in WARs
> -------------------------------------------------------------------------
>
> Key: WFLY-11353
> URL: https://issues.jboss.org/browse/WFLY-11353
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 14.0.0.Final, 15.0.0.Final
> Environment: Java 9+
> Reporter: Daniel Schwering
> Priority: Major
> Attachments: buggywar.src.zip, buggywar.war, multireleaselib-0.0.1-SNAPSHOT.jar, multireleaselib-0.0.1-SNAPSHOT.jar, multireleaselib.src.zip, multireleaselib.src.zip
>
>
> 1
> down vote
> favorite
> Since Java 9 there are Multi-Release JARs ([MRJARS|https://openjdk.java.net/jeps/238]) that allow different classes for different Java versions to be included in one JAR file. I was surprised when a Wildfly 14 running on Java 11 executed Java-8-code in a JAR included in a WAR although the JAR was a MRJAR with code for Java 11. That JAR included as a dependency for a regular Java SE project is running different code depending on the running JRE, but when included in a WAR, the Java-11-code seems to be ignored.
> Is that expected behavior for a webserver, as Java EE 8 does not explicitly require Java 9 (which introduced MRJARs) but only Java 8?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3483) Import UX components and refinements.
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3483?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3483:
--------------------------------
Description:
"Support use of 'imported' data-types". DMN supports referencing other DMN files and importing types from that into the diagram being authored.
Based on card view design option, detail new elements required to support this workflow including:
* Import components panel: Filter components by BKMs, decisions...
* micro-interaction on Import tab, wrt cards.
* Canvas node actions related to imported components.
was:
"Support use of 'imported' data-types". DMN supports referencing other DMN files and importing types from that into the diagram being authored.
Based on card view design option, detail new elements required to support this workflow including:
* Import components panel.
* micro-interaction on Import tab, wrt cards.
* Canvas node actions related to imported components.
> Import UX components and refinements.
> -------------------------------------
>
> Key: DROOLS-3483
> URL: https://issues.jboss.org/browse/DROOLS-3483
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> "Support use of 'imported' data-types". DMN supports referencing other DMN files and importing types from that into the diagram being authored.
> Based on card view design option, detail new elements required to support this workflow including:
> * Import components panel: Filter components by BKMs, decisions...
> * micro-interaction on Import tab, wrt cards.
> * Canvas node actions related to imported components.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3483) Import UX components and refinements.
by Liz Clayton (Jira)
Liz Clayton created DROOLS-3483:
-----------------------------------
Summary: Import UX components and refinements.
Key: DROOLS-3483
URL: https://issues.jboss.org/browse/DROOLS-3483
Project: Drools
Issue Type: Task
Components: DMN Editor
Reporter: Liz Clayton
Assignee: Liz Clayton
"Support use of 'imported' data-types". DMN supports referencing other DMN files and importing types from that into the diagram being authored.
Based on card view design option, detail new elements required to support this workflow including:
* Import components panel.
* micro-interaction on Import tab, wrt cards.
* Canvas node actions related to imported components.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months