Understand routers

When you need to send a bundle of information down multiple paths based off of criteria or the actions that need to take place, you’ll want to use a router or if you’re in the UK, a router. A router allows you to apply If/Else logic to your scenarios, and will replace those If/Else cards in legacy Fusion flows. As you can see, it supports multiple types of logic such as If/Else, multiple If/Else, or If/Else/Continue type of logic. A router has two or more paths and each path can contain an optional filter. Each bundle of information will be processed by the router and sent down each path. All paths are processed in sequential order in the order in which they were created. As paths are created after a router, a number is applied to the back end of each path, and bundles are processed in that sequential order. A bundle might pass through zero paths, one, or any number of paths depending on the filters applied. Of course, a path without any filters will always allow a bundle to pass through and be processed. If you have a if all else fails situation, there’s an optional marker on a path to create a fallback route. Meaning, if a bundle of information can’t bypass any of the filters on any of the paths, that bundle of information will be processed by that fallback route only. Finally, it’s important to note that any information such as items, fields, or values in one path are not automatically available in a second or third path. In an upcoming course, we’ll show you how you can use certain modules to make that information available.

There are three different ways that you can add modules to your scenario. As we’re familiar, you can add it as a standard module by clicking into the scenario designer and adding another module. You can also connect two existing modules to a third and a router will automatically appear between the three. And finally, you can click the wrench icon or the setup icon between two modules and select the option to add a router. Again, it’s very important to note that the order in which you create paths is the order in which bundles of information will be processed. If for whatever reason you connect them in the wrong order you can always unlink a router path and relink them in the correct sequence so that bundles of information are processed the way that you want them to be. It’s also important to note that you can only have one fallback route by logic. If you try to turn a different path into the fallback route it will remove that icon from the first and push it to the second. -