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
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
The text was updated successfully, but these errors were encountered:
- 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
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
The text was updated successfully, but these errors were encountered: