[JBoss JIRA] (WFCORE-1985) :read-resource-description operation should consistently order attributes by alphabet
by Jiri Ondrusek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1985?page=com.atlassian.jira.plugi... ]
Jiri Ondrusek updated WFCORE-1985:
----------------------------------
Summary: :read-resource-description operation should consistently order attributes by alphabet (was: :read-resource-description operation should consistently order resources by alphabet)
> :read-resource-description operation should consistently order attributes by alphabet
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-1985
> URL: https://issues.jboss.org/browse/WFCORE-1985
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Michal Jurc
> Assignee: Jiri Ondrusek
>
> While {{:read-resource-description}} returns an ordered list of resources with their descriptions for most resources, some resources do not return result consistent with this (resources ordered by alphabet).
> Affected resources:
> * {{/subsystem=iiop-openjdk:read-resource-description()}} returns unordered list of resources and their descriptions, while {{/subsystem=iiop-openjdk:read-resource()}} returns ordered list
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - not prevent from merge
# Check if navigator dock can be resized (/)
## Can be expanded or collapsed to left corner, good enough, no need for resize
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node
## opened DRG, clicked DRD
## opened DRD, clicked other DRD
## opened DRD, clicked DRG node
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
# Long node names
# Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - not prevent from merge
# Check if navigator dock can be resized (/)
## Can be expanded or collapsed to left corner, good enough, no need for resize
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node
## opened DRG, clicked DRD
## opened DRD, clicked other DRD
## opened DRD, clicked DRG node
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
# Long node names
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
> # Check node icons
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
> # check situation when multiple nodes has the same name, empty name
> # Check case when DRG contains a lot of nodes , if possible to view all of them
> # Check case when some decision has a lot of inputs - all of them visible
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode (x)
> ## DROOLS-2431 - not prevent from merge
> # Check if navigator dock can be resized (/)
> ## Can be expanded or collapsed to left corner, good enough, no need for resize
> h3. Navigation
> # check *back to* link present if DRD opened and shows proper node name
> # check click in Navigator dock cause either selecting DRG node or opening given DRD
> ## opened DRG, clicked other DRG node
> ## opened DRG, clicked DRD
> ## opened DRD, clicked other DRD
> ## opened DRD, clicked DRG node
> # Check behavior if user tries to select multiple entries in navigator
> # Check behavior if user tries to invoke context menu from navigator
> # Check behavior if user tries to drag some elements in navigator
> h3. Sorting
> # check is possible sort asc, desc
> # check sorting is possible even if some node selected
> # rename some DRG nodes, check navigator keeps selected sorting
> h3. Undo / Redo
> # change selection in navigator, check behavior of undo redo
> # rename some DRG nodes, undo redo, check changes reflected in navigator
> # delete DRG node, undo redo, check changes reflected in navigator
> # clear DRD node, undo redo, check changes reflected in navigator
> h3. Synchronization
> # delete DRG node, check changes reflected in navigator
> # clear DRD node, check changes reflected in navigator
> # Drag DRG elements, no effect to expected
> # Rebuild connections, change should appear in navigator
> # Check multiple connections, input node connected to multiple decisions ...
> # Long node names
> # Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - not prevent from merge
# Check if navigator dock can be resized (/)
## Can be expanded or collapsed to left corner, good enough, no need for resize
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node
## opened DRG, clicked DRD
## opened DRD, clicked other DRD
## opened DRD, clicked DRG node
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
# Long node names
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - not prevent from merge
# Check if navigator dock can be resized (/)
## Can be expanded or collapsed to left corner, good enough, no need for resize
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node
## opened DRG, clicked DRD
## opened DRD, clicked other DRD
## opened DRD, clicked DRG node
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
> # Check node icons
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
> # check situation when multiple nodes has the same name, empty name
> # Check case when DRG contains a lot of nodes , if possible to view all of them
> # Check case when some decision has a lot of inputs - all of them visible
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode (x)
> ## DROOLS-2431 - not prevent from merge
> # Check if navigator dock can be resized (/)
> ## Can be expanded or collapsed to left corner, good enough, no need for resize
> h3. Navigation
> # check *back to* link present if DRD opened and shows proper node name
> # check click in Navigator dock cause either selecting DRG node or opening given DRD
> ## opened DRG, clicked other DRG node
> ## opened DRG, clicked DRD
> ## opened DRD, clicked other DRD
> ## opened DRD, clicked DRG node
> # Check behavior if user tries to select multiple entries in navigator
> # Check behavior if user tries to invoke context menu from navigator
> # Check behavior if user tries to drag some elements in navigator
> h3. Sorting
> # check is possible sort asc, desc
> # check sorting is possible even if some node selected
> # rename some DRG nodes, check navigator keeps selected sorting
> h3. Undo / Redo
> # change selection in navigator, check behavior of undo redo
> # rename some DRG nodes, undo redo, check changes reflected in navigator
> # delete DRG node, undo redo, check changes reflected in navigator
> # clear DRD node, undo redo, check changes reflected in navigator
> h3. Synchronization
> # delete DRG node, check changes reflected in navigator
> # clear DRD node, check changes reflected in navigator
> # Drag DRG elements, no effect to expected
> # Rebuild connections, change should appear in navigator
> # Check multiple connections, input node connected to multiple decisions ...
> # Long node names
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - not prevent from merge
# Check if navigator dock can be resized (/)
## Can be expanded or collapsed to left corner, good enough, no need for resize
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node
## opened DRG, clicked DRD
## opened DRD, clicked other DRD
## opened DRD, clicked DRG node
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
##
# Check if navigator dock can be resized (/)
## Can be expanded or collapsed to left corner, good enough, no need for resize
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node
## opened DRG, clicked DRD
## opened DRD, clicked other DRD
## opened DRD, clicked DRG node
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
> # Check node icons
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
> # check situation when multiple nodes has the same name, empty name
> # Check case when DRG contains a lot of nodes , if possible to view all of them
> # Check case when some decision has a lot of inputs - all of them visible
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode (x)
> ## DROOLS-2431 - not prevent from merge
> # Check if navigator dock can be resized (/)
> ## Can be expanded or collapsed to left corner, good enough, no need for resize
> h3. Navigation
> # check *back to* link present if DRD opened and shows proper node name
> # check click in Navigator dock cause either selecting DRG node or opening given DRD
> ## opened DRG, clicked other DRG node
> ## opened DRG, clicked DRD
> ## opened DRD, clicked other DRD
> ## opened DRD, clicked DRG node
> # Check behavior if user tries to select multiple entries in navigator
> # Check behavior if user tries to invoke context menu from navigator
> # Check behavior if user tries to drag some elements in navigator
> h3. Sorting
> # check is possible sort asc, desc
> # check sorting is possible even if some node selected
> # rename some DRG nodes, check navigator keeps selected sorting
> h3. Undo / Redo
> # change selection in navigator, check behavior of undo redo
> # rename some DRG nodes, undo redo, check changes reflected in navigator
> # delete DRG node, undo redo, check changes reflected in navigator
> # clear DRD node, undo redo, check changes reflected in navigator
> h3. Synchronization
> # delete DRG node, check changes reflected in navigator
> # clear DRD node, check changes reflected in navigator
> # Drag DRG elements, no effect to expected
> # Rebuild connections, change should appear in navigator
> # Check multiple connections, input node connected to multiple decisions ...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2431) [DMN Designer] Navigator has not same header height in full screen mode
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2431?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2431:
--------------------------------
Summary: [DMN Designer] Navigator has not same header height in full screen mode (was: [DMN Designer] Navigator has not same header width in full screen mode)
> [DMN Designer] Navigator has not same header height in full screen mode
> -----------------------------------------------------------------------
>
> Key: DROOLS-2431
> URL: https://issues.jboss.org/browse/DROOLS-2431
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Trivial
> Attachments: Screenshot from 2018-03-28 08-26-22.png
>
>
> If DMN Designer enters full screen mode, its header has has different height as navigator, see the attachment. Compare header height in *Decision Navigator* part and *New DMN diagram* part.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2431) [DMN Designer] Navigator has not same header width in full screen mode
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2431:
-----------------------------------
Summary: [DMN Designer] Navigator has not same header width in full screen mode
Key: DROOLS-2431
URL: https://issues.jboss.org/browse/DROOLS-2431
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.8.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Priority: Trivial
Attachments: Screenshot from 2018-03-28 08-26-22.png
If DMN Designer enters full screen mode, its header has has different height as navigator, see the attachment. Compare header height in *Decision Navigator* part and *New DMN diagram* part.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
##
# Check if navigator dock can be resized (/)
## Can be expanded or collapsed to left corner, good enough, no need for resize
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node
## opened DRG, clicked DRD
## opened DRD, clicked other DRD
## opened DRD, clicked DRG node
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode
# Check if navigator dock can be resized
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node
## opened DRG, clicked DRD
## opened DRD, clicked other DRD
## opened DRD, clicked DRG node
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
> # Check node icons
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
> # check situation when multiple nodes has the same name, empty name
> # Check case when DRG contains a lot of nodes , if possible to view all of them
> # Check case when some decision has a lot of inputs - all of them visible
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode (x)
> ##
> # Check if navigator dock can be resized (/)
> ## Can be expanded or collapsed to left corner, good enough, no need for resize
> h3. Navigation
> # check *back to* link present if DRD opened and shows proper node name
> # check click in Navigator dock cause either selecting DRG node or opening given DRD
> ## opened DRG, clicked other DRG node
> ## opened DRG, clicked DRD
> ## opened DRD, clicked other DRD
> ## opened DRD, clicked DRG node
> # Check behavior if user tries to select multiple entries in navigator
> # Check behavior if user tries to invoke context menu from navigator
> # Check behavior if user tries to drag some elements in navigator
> h3. Sorting
> # check is possible sort asc, desc
> # check sorting is possible even if some node selected
> # rename some DRG nodes, check navigator keeps selected sorting
> h3. Undo / Redo
> # change selection in navigator, check behavior of undo redo
> # rename some DRG nodes, undo redo, check changes reflected in navigator
> # delete DRG node, undo redo, check changes reflected in navigator
> # clear DRD node, undo redo, check changes reflected in navigator
> h3. Synchronization
> # delete DRG node, check changes reflected in navigator
> # clear DRD node, check changes reflected in navigator
> # Drag DRG elements, no effect to expected
> # Rebuild connections, change should appear in navigator
> # Check multiple connections, input node connected to multiple decisions ...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode
# Check if navigator dock can be resized
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node
## opened DRG, clicked DRD
## opened DRD, clicked other DRD
## opened DRD, clicked DRG node
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
# check situation when multiple nodes has the same name, empty name
# Check case when DRG contains a lot of nodes , if possible to view all of them
# Check case when some decision has a lot of inputs - all of them visible
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode
# Check if navigator dock can be resized
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name
# check click in Navigator dock cause either selecting DRG node or opening given DRD
# Check behavior if user tries to select multiple entries in navigator
# Check behavior if user tries to invoke context menu from navigator
# Check behavior if user tries to drag some elements in navigator
h3. Sorting
# check is possible sort asc, desc
# check sorting is possible even if some node selected
# rename some DRG nodes, check navigator keeps selected sorting
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo
# rename some DRG nodes, undo redo, check changes reflected in navigator
# delete DRG node, undo redo, check changes reflected in navigator
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
> # Check node icons
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing
> # check situation when multiple nodes has the same name, empty name
> # Check case when DRG contains a lot of nodes , if possible to view all of them
> # Check case when some decision has a lot of inputs - all of them visible
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode
> # Check if navigator dock can be resized
> h3. Navigation
> # check *back to* link present if DRD opened and shows proper node name
> # check click in Navigator dock cause either selecting DRG node or opening given DRD
> ## opened DRG, clicked other DRG node
> ## opened DRG, clicked DRD
> ## opened DRD, clicked other DRD
> ## opened DRD, clicked DRG node
> # Check behavior if user tries to select multiple entries in navigator
> # Check behavior if user tries to invoke context menu from navigator
> # Check behavior if user tries to drag some elements in navigator
> h3. Sorting
> # check is possible sort asc, desc
> # check sorting is possible even if some node selected
> # rename some DRG nodes, check navigator keeps selected sorting
> h3. Undo / Redo
> # change selection in navigator, check behavior of undo redo
> # rename some DRG nodes, undo redo, check changes reflected in navigator
> # delete DRG node, undo redo, check changes reflected in navigator
> # clear DRD node, undo redo, check changes reflected in navigator
> h3. Synchronization
> # delete DRG node, check changes reflected in navigator
> # clear DRD node, check changes reflected in navigator
> # Drag DRG elements, no effect to expected
> # Rebuild connections, change should appear in navigator
> # Check multiple connections, input node connected to multiple decisions ...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month