[JBoss JIRA] (WFLY-10489) mod_cluster listener attribute is still called "connector"
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10489?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-10489:
----------------------------------
Description:
mod_cluster listener attribute name is still "connector" which is confusing.
The goal is to rename this to listener.
was:
mod_cluster listener attribute is still called "connector" which is confusing.
The goal is to rename this to listener.
> mod_cluster listener attribute is still called "connector"
> ----------------------------------------------------------
>
> Key: WFLY-10489
> URL: https://issues.jboss.org/browse/WFLY-10489
> Project: WildFly
> Issue Type: Enhancement
> Components: mod_cluster
> Affects Versions: 13.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> mod_cluster listener attribute name is still "connector" which is confusing.
> The goal is to rename this to listener.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (WFLY-10489) mod_cluster listener attribute is still called "connector"
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10489?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-10489:
----------------------------------
Description:
mod_cluster listener attribute name is still "connector" (from the Tomcat/JBoss Web days) which is confusing.
The goal is to rename this to listener.
was:
mod_cluster listener attribute name is still "connector" which is confusing.
The goal is to rename this to listener.
> mod_cluster listener attribute is still called "connector"
> ----------------------------------------------------------
>
> Key: WFLY-10489
> URL: https://issues.jboss.org/browse/WFLY-10489
> Project: WildFly
> Issue Type: Enhancement
> Components: mod_cluster
> Affects Versions: 13.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> mod_cluster listener attribute name is still "connector" (from the Tomcat/JBoss Web days) which is confusing.
> The goal is to rename this to listener.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (DROOLS-2564) [DMN Designer] Data-types: Grid: General
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2564?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2564:
--------------------------------
Description:
Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components.
h3. Manual Acceptance test
- Create two decision nodes
- Specify some expression for both
- Open expression editor for first
- Rename the decision node in properties panel
-- Check *<< Back to XXX* (/)
-- Check Expression header cell (x)
- Via navigation dock open second node expression
-- Check *<< Back to XXX* (/)
-- Check Expression header cell (x)
- Rename the decision node in properties panel
-- Check *<< Back to XXX* (/)
-- Check Expression header cell (x)
- Save and reopen diagram
-- Check names are stored (/)
was:
Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components.
h3. Manual Acceptance test
- Create two decision nodes
- Specify some expression for both
- Open expression editor for first
- Rename the decision node in properties panel
-- Check *<< Back to XXX*
- Via navigation dock open second node expression
-- Check *<< Back to XXX*
- Rename the decision node in properties panel
-- Check *<< Back to XXX*
- Save and reopen diagram
-- Check names are stored
> [DMN Designer] Data-types: Grid: General
> ----------------------------------------
>
> Key: DROOLS-2564
> URL: https://issues.jboss.org/browse/DROOLS-2564
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components.
> h3. Manual Acceptance test
> - Create two decision nodes
> - Specify some expression for both
> - Open expression editor for first
> - Rename the decision node in properties panel
> -- Check *<< Back to XXX* (/)
> -- Check Expression header cell (x)
> - Via navigation dock open second node expression
> -- Check *<< Back to XXX* (/)
> -- Check Expression header cell (x)
> - Rename the decision node in properties panel
> -- Check *<< Back to XXX* (/)
> -- Check Expression header cell (x)
> - Save and reopen diagram
> -- Check names are stored (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (DROOLS-2815) [DMN Designer] Make Expression Type dependent on Diagram Node
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2815?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2815:
-----------------------------------
Description:
The expression editor options should be dependent on the diagram node type.
h2. Decision Node
Should allow all expression types except of *Function*
h2. BKM Node
Should allow only *Function* expression type.
h3. Further improvement
BKM node has automatically function expression inside - separate jira, or won't be implemented?
([~jomarko] IMO If/when [~tirelli] confirms the subject of this JIRA is the expected/required operation I'd ensure BKMs have a Function set and cannot be cleared).
h2. Acceptance tests
- Not possible to set *function expression type* for Decision node
- Possible to set just *function expression type* for BKM node
-- Created automatically if we decide to implement here
- Dialog shown if opened file from external tool that doesn't follow this restriction
was:
The expression editor options should be dependent on the diagram node type.
h2. Decision Node
Should allow all expression types except of *Function*
h2. BKM Node
Should allow only *Function* expression type.
h3. Further improvement
BKM node has automatically function expression inside - separate jira, or won't be implemented?
h2. Acceptance tests
- Not possible to set *function expression type* for Decision node
- Possible to set just *function expression type* for BKM node
-- Created automatically if we decide to implement here
- Dialog shown if opened file from external tool that doesn't follow this restriction
> [DMN Designer] Make Expression Type dependent on Diagram Node
> -------------------------------------------------------------
>
> Key: DROOLS-2815
> URL: https://issues.jboss.org/browse/DROOLS-2815
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: drools-tools
>
> The expression editor options should be dependent on the diagram node type.
> h2. Decision Node
> Should allow all expression types except of *Function*
> h2. BKM Node
> Should allow only *Function* expression type.
> h3. Further improvement
> BKM node has automatically function expression inside - separate jira, or won't be implemented?
> ([~jomarko] IMO If/when [~tirelli] confirms the subject of this JIRA is the expected/required operation I'd ensure BKMs have a Function set and cannot be cleared).
> h2. Acceptance tests
> - Not possible to set *function expression type* for Decision node
> - Possible to set just *function expression type* for BKM node
> -- Created automatically if we decide to implement here
> - Dialog shown if opened file from external tool that doesn't follow this restriction
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2787:
----------------------------------------
[~uxdlc] [~tirelli] [~karreiro] The above [comment|https://issues.jboss.org/browse/DROOLS-2787?focusedCommentId=1361...] confuses me.
IMO the _selection_ mechanism is the [drop-down|https://redhatbxms.slack.com/files/UBN15ASSH/FBZRKH997/search.gif] that is to be used in the Properties Panel and "[in grid|https://issues.jboss.org/browse/DROOLS-2794]" (see [proposals|https://issues.jboss.org/secure/attachment/12438722/DROOLS-2792...]).
IMO the modal (access from the button on the drop-down -- or a new "edit/create" entry in the drop-down itself. I know this is/has been discussed) would be where Users _manage_ *custom* data-types (e.g. add new, edit existing, both simple and structured).
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2738.bmpr, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.)
> * *Remove* Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (DROOLS-2564) [DMN Designer] Data-types: Grid: General
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2564?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2564:
--------------------------------
Description:
Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components.
h3. Manual Acceptance test
- Create two decision nodes
- Specify some expression for both
- Open expression editor for first
- Rename the decision node in properties panel
-- Check *<< Back to XXX*
- Via navigation dock open second node expression
-- Check *<< Back to XXX*
- Rename the decision node in properties panel
-- Check *<< Back to XXX*
- Save and reopen diagram
-- Check names are stored
was:Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components.
> [DMN Designer] Data-types: Grid: General
> ----------------------------------------
>
> Key: DROOLS-2564
> URL: https://issues.jboss.org/browse/DROOLS-2564
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components.
> h3. Manual Acceptance test
> - Create two decision nodes
> - Specify some expression for both
> - Open expression editor for first
> - Rename the decision node in properties panel
> -- Check *<< Back to XXX*
> - Via navigation dock open second node expression
> -- Check *<< Back to XXX*
> - Rename the decision node in properties panel
> -- Check *<< Back to XXX*
> - Save and reopen diagram
> -- Check names are stored
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months