Introduction

The “Anchor” component allows you to keep flow segments within the routing point that will NOT be part of the user's main path, but that you want to save as a reference or for future reuse.

It is very useful when you are testing flow variants, when you want to preserve logic that you are not yet ready to activate, or when you need to “park” a section without deleting it and without generating errors during compilation.

Configuration

• This component is located within the “Design” tab of the wolkvox Studio components panel.
• This component will be the starting point of your isolated flow (but NOT of the actual user flow).
• It does not have a component configuration panel.

• From the Anchor, start connecting the components you want to keep: functions, notifications, message sending, validations, etc.
• Design that part of the flow as if it were a normal path, but keep in mind that the user will not pass through it, as the actual journey always starts from the Start component (green circle).
• The idea is for this flow “island” to be ready for future use, copying, or reference.
• It is mandatory that the path starting from the Anchor ends in an “End” component. If you do not do this, syntax errors will appear when compiling the routing point because an open path would exist.
• With the End component, you indicate that the isolated segment is correctly closed, and the system accepts it even if it doesn't have its own “Start” component.
• Once you have your main flow and the section isolated with Anchor → … → End, compile the routing point.
• In the “Compile Log” panel, you should see a message indicating that there are no syntax errors.
  • If an error appears, check that the path coming out of the “Anchor” is completely closed in an “End” and that there are no unconnected components.