You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue tracks the UI work needed to support #2255. Currently there are restrictions placed on the edge type of a node based on the edge types of it's siblings. For example, when adding a new node if the parent of the new node has other children with an edge type of always then the new node's edge type is current restricted to always. The same is true for the combination of success/failure. In the previous example, if the children had an edge type of success then the new node's edge type would currently be restricted to success or failure. The work associated with this issue will remove that restriction from new/existing nodes. The user will now be able to select any of the three edge types regardless of the edge type(s) of it's siblings.
This is what the RUN (edge type) option should always look like (exception below):
I've outlined what the edge type restrictions currently look like. After this work is completed, all three options (always/success/failure) should be present:
The one exception to this rule is root nodes. These nodes are displayed as children of the start button and their edge type is alwaysalways:
Acceptance Criteria:
As a user, I can create and edit a node with the WF visualizer using all three edge types, so I can create concise and manageable workflows
Tests pass (e2e)
A test should be written that confirms that the edge type on a root node is always always
A test should be written that confirms that S/F/A can be selected when adding a node with no siblings
A test should be written that confirms that S/F/A can be selected when adding a node with a sibling
A test should be written that confirms that S/F/A can be selected when editing a node
The text was updated successfully, but these errors were encountered:
ISSUE TYPE
COMPONENT NAME
SUMMARY
link #2255
This issue tracks the UI work needed to support #2255. Currently there are restrictions placed on the edge type of a node based on the edge types of it's siblings. For example, when adding a new node if the parent of the new node has other children with an edge type of
always
then the new node's edge type is current restricted toalways
. The same is true for the combination ofsuccess
/failure
. In the previous example, if the children had an edge type ofsuccess
then the new node's edge type would currently be restricted tosuccess
orfailure
. The work associated with this issue will remove that restriction from new/existing nodes. The user will now be able to select any of the three edge types regardless of the edge type(s) of it's siblings.This is what the
RUN
(edge type) option should always look like (exception below):I've outlined what the edge type restrictions currently look like. After this work is completed, all three options (always/success/failure) should be present:
The one exception to this rule is root nodes. These nodes are displayed as children of the start button and their edge type is always
always
:Acceptance Criteria:
The text was updated successfully, but these errors were encountered: