Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deleting first step of call flow rearranges sub call flows #626

Closed
edjez opened this issue Jan 16, 2015 · 1 comment
Closed

Deleting first step of call flow rearranges sub call flows #626

edjez opened this issue Jan 16, 2015 · 1 comment

Comments

@edjez
Copy link

edjez commented Jan 16, 2015

When deleting the first step of the first subcallflow in the call flow designer, the whole first sub-flow got rearranged to be the last sub-call-flow on the designer.
This caused the call to start at the sub-flow remaining at the top, with no way to rearrange than to delete and recreate the whole "stack" of flows.
Given multiple sub call flows it may be great to allow users to promote one to be the "first"/top one
image

spalladino added a commit that referenced this issue Nov 1, 2016
- Root attribute in a call flow step is now an observable.
- Loading steps is delayed so workflow is defined in initializers
- Refactored bottom-actions in all steps into a partial

Fixes #626
@spalladino spalladino self-assigned this Nov 1, 2016
@spalladino spalladino added this to the Release 2.8 milestone Nov 1, 2016
@mmuller
Copy link

mmuller commented Nov 7, 2016

Sub flows can be rearranged properly in version 3.0-pre1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants