[JBoss JIRA] (DROOLS-4205) DMN: UI enhancements for Data Type editor
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4205?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4205:
--------------------------------------
Epic Name: Data Type UI Enhancements (was: Data Type UX)
> DMN: UI enhancements for Data Type editor
> -----------------------------------------
>
> Key: DROOLS-4205
> URL: https://issues.jboss.org/browse/DROOLS-4205
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> *User Story*
> As a practitioner I want to be able to:
> * select an existing data type
> * create a simple or structured data type
> * create a “compound” (or complex) data type, easily.
> *
expand/collapse views of compound data types, so that I can___
> *
navigate between levels in a compound data type, so that I can___
> * edit an existing data type
> * remove an existing data type
>
…so that I can use the data type when creating a decision related asset.
> Requested UI enhancements, based on feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)
> * NESTING ISSUES ARE HIGH PRIORITY
> - Fix Dropdown menu labeling (Structure)
> - Weird tooltip on Structured row.
> - It wasn’t clear wasn’t what was nested, and looking for drag-n-drop to nest and reorder.
> - Finding “Structure” in the dropdown - was separate, blue and at the bottom. Terminology.
> - Nested data types, - all 3 used the field already open, but confusion about adding additional rows. Kebab didn’t work so well. Terminology for kebab menu.
> - Due to the icon at the top level and no icons at the second level, the indenting of second level items is not very clear for users. Make sure the nesting is very clear at a glance.
> - Better way to add a new field that is always visible to the user and clear to use without having to go into a kabob menu
> RELATED SAVE INTERACTIONS (Save, Delete, Remove)
> - Inline editing of the content in the rows would make the experience nicer than having a whole row edit model
> - - It's not obvious that you have to select the "check mark" to commit the change.
> - After adding a new data type field, undo becomes available but instead of removing the field, it resets the field name and type to the defaults. Redo then becomes available but doesn't appear to do anything when clicked.
> OTHER:
> - “Constraint” link was confusing, but location was good.
> - In the dialog, “Add” wasn’t found too well. (Bug adding a null constraint.)
> - Questions around Save - should it not require Save at the row level.
> - It feels unnatural to have to click the "Constraints" to open the Constraints modal.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4205) DMN: UI enhancements for Data Type editor
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4205?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4205:
--------------------------------------
Description:
*User Story*
As a practitioner I want to be able to:
* select an existing data type
* create a simple or structured data type
* create a “compound” (or complex) data type, easily.
*
expand/collapse views of compound data types, so that I can___
*
navigate between levels in a compound data type, so that I can___
* edit an existing data type
* remove an existing data type
…so that I can use the data type when creating a decision related asset.
Requested UI enhancements, based on feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)
* NESTING ISSUES ARE HIGH PRIORITY
- Fix Dropdown menu labeling (Structure)
- Weird tooltip on Structured row.
- It wasn’t clear wasn’t what was nested, and looking for drag-n-drop to nest and reorder.
- Finding “Structure” in the dropdown - was separate, blue and at the bottom. Terminology.
- Nested data types, - all 3 used the field already open, but confusion about adding additional rows. Kebab didn’t work so well. Terminology for kebab menu.
- Due to the icon at the top level and no icons at the second level, the indenting of second level items is not very clear for users. Make sure the nesting is very clear at a glance.
- Better way to add a new field that is always visible to the user and clear to use without having to go into a kabob menu
RELATED SAVE INTERACTIONS (Save, Delete, Remove)
- Inline editing of the content in the rows would make the experience nicer than having a whole row edit model
- - It's not obvious that you have to select the "check mark" to commit the change.
- After adding a new data type field, undo becomes available but instead of removing the field, it resets the field name and type to the defaults. Redo then becomes available but doesn't appear to do anything when clicked.
OTHER:
- “Constraint” link was confusing, but location was good.
- In the dialog, “Add” wasn’t found too well. (Bug adding a null constraint.)
- Questions around Save - should it not require Save at the row level.
- It feels unnatural to have to click the "Constraints" to open the Constraints modal.
was:
*User Story*
As a practitioner I want to be able to:
* select an existing data type
* create a simple or structured data type
* create a “compound” (or complex) data type, easily.
*
expand/collapse views of compound data types, so that I can___
*
navigate between levels in a compound data type, so that I can___
* edit an existing data type
* remove an existing data type
…so that I can use the data type when creating a decision related asset.
UI enhancements, based on feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)
Address usability issues:
> DMN: UI enhancements for Data Type editor
> -----------------------------------------
>
> Key: DROOLS-4205
> URL: https://issues.jboss.org/browse/DROOLS-4205
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> *User Story*
> As a practitioner I want to be able to:
> * select an existing data type
> * create a simple or structured data type
> * create a “compound” (or complex) data type, easily.
> *
expand/collapse views of compound data types, so that I can___
> *
navigate between levels in a compound data type, so that I can___
> * edit an existing data type
> * remove an existing data type
>
…so that I can use the data type when creating a decision related asset.
> Requested UI enhancements, based on feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)
> * NESTING ISSUES ARE HIGH PRIORITY
> - Fix Dropdown menu labeling (Structure)
> - Weird tooltip on Structured row.
> - It wasn’t clear wasn’t what was nested, and looking for drag-n-drop to nest and reorder.
> - Finding “Structure” in the dropdown - was separate, blue and at the bottom. Terminology.
> - Nested data types, - all 3 used the field already open, but confusion about adding additional rows. Kebab didn’t work so well. Terminology for kebab menu.
> - Due to the icon at the top level and no icons at the second level, the indenting of second level items is not very clear for users. Make sure the nesting is very clear at a glance.
> - Better way to add a new field that is always visible to the user and clear to use without having to go into a kabob menu
> RELATED SAVE INTERACTIONS (Save, Delete, Remove)
> - Inline editing of the content in the rows would make the experience nicer than having a whole row edit model
> - - It's not obvious that you have to select the "check mark" to commit the change.
> - After adding a new data type field, undo becomes available but instead of removing the field, it resets the field name and type to the defaults. Redo then becomes available but doesn't appear to do anything when clicked.
> OTHER:
> - “Constraint” link was confusing, but location was good.
> - In the dialog, “Add” wasn’t found too well. (Bug adding a null constraint.)
> - Questions around Save - should it not require Save at the row level.
> - It feels unnatural to have to click the "Constraints" to open the Constraints modal.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4205) DMN: UX enhancements for Data Type editor
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4205?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4205:
--------------------------------------
Description:
*User Story*
As a practitioner I want to be able to:
* select an existing data type
* create a simple or structured data type
* create a “compound” (or complex) data type, easily.
*
expand/collapse views of compound data types, so that I can___
*
navigate between levels in a compound data type, so that I can___
* edit an existing data type
* remove an existing data type
…so that I can use the data type when creating a decision related asset.
UI enhancements, based on feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)
Address usability issues:
was:
As a practitioner I want to be able to:
* select an existing data type
* create a simple or structured data type
* create a “compound” (or complex) data type, easily.
*
expand/collapse views of compound data types, so that I can___
*
navigate between levels in a compound data type, so that I can___
* edit an existing data type
* remove an existing data type
…so that I can use the data type when creating a decision related asset.
> DMN: UX enhancements for Data Type editor
> -----------------------------------------
>
> Key: DROOLS-4205
> URL: https://issues.jboss.org/browse/DROOLS-4205
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> *User Story*
> As a practitioner I want to be able to:
> * select an existing data type
> * create a simple or structured data type
> * create a “compound” (or complex) data type, easily.
> *
expand/collapse views of compound data types, so that I can___
> *
navigate between levels in a compound data type, so that I can___
> * edit an existing data type
> * remove an existing data type
>
…so that I can use the data type when creating a decision related asset.
> UI enhancements, based on feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)
> Address usability issues:
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4205) DMN: UI enhancements for Data Type editor
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4205?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4205:
--------------------------------------
Summary: DMN: UI enhancements for Data Type editor (was: DMN: UX enhancements for Data Type editor)
> DMN: UI enhancements for Data Type editor
> -----------------------------------------
>
> Key: DROOLS-4205
> URL: https://issues.jboss.org/browse/DROOLS-4205
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> *User Story*
> As a practitioner I want to be able to:
> * select an existing data type
> * create a simple or structured data type
> * create a “compound” (or complex) data type, easily.
> *
expand/collapse views of compound data types, so that I can___
> *
navigate between levels in a compound data type, so that I can___
> * edit an existing data type
> * remove an existing data type
>
…so that I can use the data type when creating a decision related asset.
> UI enhancements, based on feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)
> Address usability issues:
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4205) DMN: UX enhancements for Data Type editors
by Elizabeth Clayton (Jira)
Elizabeth Clayton created DROOLS-4205:
-----------------------------------------
Summary: DMN: UX enhancements for Data Type editors
Key: DROOLS-4205
URL: https://issues.jboss.org/browse/DROOLS-4205
Project: Drools
Issue Type: Epic
Components: DMN Editor
Reporter: Elizabeth Clayton
Assignee: Elizabeth Clayton
As a practitioner I want to be able to:
* select an existing data type
* create a simple or structured data type
* create a “compound” (or complex) data type, easily.
*
expand/collapse views of compound data types, so that I can___
*
navigate between levels in a compound data type, so that I can___
* edit an existing data type
* remove an existing data type
…so that I can use the data type when creating a decision related asset.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4205) DMN: UX enhancements for Data Type editor
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4205?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4205:
--------------------------------------
Summary: DMN: UX enhancements for Data Type editor (was: DMN: UX enhancements for Data Type editors)
> DMN: UX enhancements for Data Type editor
> -----------------------------------------
>
> Key: DROOLS-4205
> URL: https://issues.jboss.org/browse/DROOLS-4205
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> As a practitioner I want to be able to:
> * select an existing data type
> * create a simple or structured data type
> * create a “compound” (or complex) data type, easily.
> *
expand/collapse views of compound data types, so that I can___
> *
navigate between levels in a compound data type, so that I can___
> * edit an existing data type
> * remove an existing data type
>
…so that I can use the data type when creating a decision related asset.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-12227) IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml
by Ondrej Kotek (Jira)
Ondrej Kotek created WFLY-12227:
-----------------------------------
Summary: IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml
Key: WFLY-12227
URL: https://issues.jboss.org/browse/WFLY-12227
Project: WildFly
Issue Type: Bug
Components: JCA
Affects Versions: 18.0.0.Beta1
Reporter: Ondrej Kotek
Assignee: Stefano Maestri
There is a warning during start with standalone-full*.xml:
{noformat}
12:19:04,432 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA
12:19:04,440 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
12:19:04,441 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 83) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
12:19:04,441 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020017: Invalid archive: file://RaActivatoractivemq-ra
12:19:04,486 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started
12:19:04,486 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra
12:19:04,492 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
12:19:04,493 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
{noformat}
For an automation checking the server log for issues, this WARN causes false positive. Hence, I set the Priority to Critical.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3805) All line separators in RHS in spreadsheet are escaped
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3805?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3805:
--------------------------------
Fix Version/s: 7.24.0.Final
> All line separators in RHS in spreadsheet are escaped
> -----------------------------------------------------
>
> Key: DROOLS-3805
> URL: https://issues.jboss.org/browse/DROOLS-3805
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 7.18.0.Final, 7.19.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools, support
> Fix For: 7.24.0.Final
>
>
> By DROOLS-3396, line separators in RHS are now escaped.
> https://github.com/kiegroup/drools/blob/7.18.0.Final/drools-decisiontable...
> However, it affects entire RHS so if you have multiple lines in ACTION, the result would be like this.
> Output from SpreadSheetCompiler:
> {noformat}
> rule "multiple lines in action_12"
> when
> $fact:Person(name == "John")
> then
> modify($fact){\n setAge(30),\n setAlive(false)\n}
> /* DEBUG */\nSystem.out.println(" ** " +drools.getRule().getName() + ", $fact = " + $fact);
> end
> {noformat}
> Error when building:
> {noformat}
> line 1:15 no viable alternative at character '\'
> line 1:29 no viable alternative at character '\'
> line 1:47 no viable alternative at character '\'
> line 2:13 no viable alternative at character '\'
> [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.63 s <<< FAILURE! - in org.drools.decisiontable.LineBreakXLSTest
> [ERROR] testMultipleLinesInAction(org.drools.decisiontable.LineBreakXLSTest) Time elapsed: 0.257 s <<< ERROR!
> java.lang.NullPointerException
> at java.lang.String.indexOf(String.java:1718)
> at org.drools.compiler.rule.builder.dialect.DialectUtil.rewriteModifyDescr(DialectUtil.java:631)
> at org.drools.compiler.rule.builder.dialect.DialectUtil.rewriteDescr(DialectUtil.java:580)
> at org.drools.compiler.rule.builder.dialect.DialectUtil.fixBlockDescr(DialectUtil.java:161)
> at org.drools.compiler.rule.builder.dialect.DialectUtil.fixBlockDescr(DialectUtil.java:119)
> at org.drools.compiler.rule.builder.dialect.asm.AbstractASMConsequenceBuilder.consequenceContext(AbstractASMConsequenceBuilder.java:57)
> at org.drools.compiler.rule.builder.dialect.asm.AbstractASMConsequenceBuilder.build(AbstractASMConsequenceBuilder.java:33)
> at org.drools.compiler.rule.builder.RuleBuilder.build(RuleBuilder.java:126)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.internalAddRule(KnowledgeBuilderImpl.java:1204)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addRule(KnowledgeBuilderImpl.java:1195)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileRulesLevel(KnowledgeBuilderImpl.java:1173)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileRules(KnowledgeBuilderImpl.java:1121)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileKnowledgePackages(KnowledgeBuilderImpl.java:946)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addPackage(KnowledgeBuilderImpl.java:937)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addPackageFromDecisionTable(KnowledgeBuilderImpl.java:371)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addKnowledgeResource(KnowledgeBuilderImpl.java:759)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:2288)
> at org.drools.decisiontable.LineBreakXLSTest.testMultipleLinesInAction(LineBreakXLSTest.java:53)
> ...
> {noformat}
> Escaping should be done only for literal String?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFCORE-2496) Functionality in WildFly to encrypt database passwords
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFCORE-2496?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFCORE-2496:
------------------------------------------
[~fjuma] I suspect this is now a duplicate but it ties in more closely with your task than with mine.
> Functionality in WildFly to encrypt database passwords
> ------------------------------------------------------
>
> Key: WFCORE-2496
> URL: https://issues.jboss.org/browse/WFCORE-2496
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 3.0.0.Beta7
> Reporter: Carlton Zachary
> Assignee: Farah Juma
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> Is it possible to add functionality to WildFly to encrypt a data source password when the data source is being created? Currently WildFly/EAP stores the password as plain text in the domain.xml/standalone.xml.
> Thanks
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months