How does a GoTo step work?
Comments
-
Hihi! I was trying to use a GoTo step to jump from one part of my flow to another part so I didnt have any lines crossing and to keep it all neat and stuff, but I cant seem to find the data from the previous part of the flow when I do that? If I connect them directly, I can see the data in the "Select from Flow" part. I dont really understand how to use this step. Am I using it wrong or is this some sort of defect?
-
Hey there! Yes, that is the expected behaviour of a GoTo step. Typically, you would use it as a way to navigate back to a section of the flow that already exists previously rather than using it to jump from one location to another as the data does not carry over after the GoTo step. A GoTo step can be useful as a way to restart a process if a certain outcome was reached for example.
If you find that there is too much going on in your flow, and it becomes hard to keep your lines neat without them crossing over each other too much, I would highly recommend breaking some of the steps into smaller sub flows to consolidate logic neatly. There will be less lines to look at overall, and then you can map the fewer steps to each other without needing to cross as many/any lines. If you can break parts of this flow into smaller sections of steps that are all linked, then that can become a new sub flow. You can refer to our documentation on [url=https://documentation.decisions.com/docs/best-practices#functionality]Decisions Best Practices[/url] and [url=https://documentation.decisions.com/docs/using-sub-flows]Using Sub Flows[/url] where these outline the benefits of using sub flows.
While [url=https://documentation.decisions.com/docs/using-placeholder-components-to-sketch-out-flow-structure]Placeholder Steps[/url] steps are typically used as just temporary steps, they can also be used to clean up your flows by minimizing how many lines you have trying to go towards the same step by routing most of them to that placeholder step, and then from the placeholder step to the step all the ones were intending to go towards. This can be used as a way to just anchor your lines more neatly when routing through it since Placeholder steps dont really add any big benefits to a flow. This is mostly an alternative, but sub flows are definitely the preferred method for keeping your flows neat and orderly. These placeholder steps can be useful in niche cases of organisation so I outlined their benefit as well.
Howdy, Stranger!
Categories
- 4.2K All Categories
- 67 General
- 11 Training
- 202 Installation / Setup
- 1.1K Flows
- 106 Rules
- 262 Administration
- 212 Portal
- 490 General Q & A
- 695 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 52 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 179 Pages
- 5 Process Mining
- New Features
- 179 Datastructures
- 69 Repository
- 221 Integrations
- 28 Multi-Tenant
- 27 SDK
- 78 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 83 Lunch And Learn Questions