How to Create a Registration Flow for a Field Event in Zuddl

Published:

8 mins read

Updated:

Flow builder allows you to tailor your registration style for your event, enabling you to customize each registration step based on your business needs.

Flow builder is only allowed for flex registration style-based events. For registration styles other than Flex registrations, you need to create a registration page. Learn how to create a registration page.

Editing the flow

In the form section, you can add or edit fields on the registration form

Log in to your Zuddl dashboard.
Navigate to Registration > Flow. This redirects you to the flow builder page.

You enter the flow builder screen in the draft state.

Create a form

In the form section, you can add or edit fields on the registration form. Edit the display name of the standard fields.

You can only edit the display name of the standard registration fields. Other properties cannot be edited.
Click +Add field to add a new standard or custom field.
1. You can choose from a list of standard fields or create a new custom field (default).
2. Select an option from the Type dropdown to select the data type.
  - Text: for text inputs
  - Email: for inputs in email format
  - Phone number: for inputs in phone number format
  - URL: for inputs in URL format
  - Country: This shows the country list as a dropdown
  - Dropdown: to select input from a list of options. You can add your options in an additional field called ‘Options.’
  - Multiselect: dropdown options with multi-select
  - Number: for inputs in number format
  - Rich Text: for inputs in rich text format
3. Select the Mandatory checkbox.
Now, in the Button section, rename the button name. Defaults to Continue.
In the same way, you can also add disclaimers to a registration form by clicking the +Add disclaimer button.
After you’ve finished the editing form, close the side pane to view the updated flow diagram.

You can rename all forms and delete the additional forms that you created. The form that contains First name, Last name, and Email fields and the Thank you step can’t be deleted.

If a registrant leaves the registration flow after filling up some forms and returns to the flow, the previously completed forms will be automatically saved and you can continue with the next step.

This works only if the registrant fills the form again using same device and the same browser.

Finally, edit the Success/Thank you page content. You can edit the standard messaging for Page title and the Sub-text to be shown to your attendees.

This completes the flow setup, and the data flow is auto-saved.

Publishing the flow

Publishing the flow makes it visible to attendees who plan to register for your event. After you have made all the changes, you can click the Publish button.

On the confirmation pop-up, click Publish. This makes the recently edited registration flow live for your attendees.

Note: The confirmation pop-up appears only when you publish a registration flow for the first time. After that, new changes are published when you click the Publish button.

You can click the </>Get embeddable code to copy the embeddable code to your clipboard to paste it at any desired web page to show the Zuddl registration form and collect registrations.

If you wish to embed flex widgets on third-party pages, you can use the ‘data-zuddl-sticky-header-id’ attribute, which needs to be added to the flow embed code if your page has a fixed (sticky) header.

View and restore version

Once published, you can view the published flow by clicking the three dots icon on the top, as shown in the screenshot below:

If you are making changes to an already published flow, you can restore the published version by clicking the Restore this flow button on the published flow view should you face any errors while editing the flow.

To view the previously published version, do not publish the data being worked upon.

Troubleshooting Errors

If there are any errors in the flow, they will be highlighted, as shown below. You can view more details to understand the error and fix it in the flow.

Since there is no undo option, all your changes are saved instantly and you would not be able to undo any changes made.

To apply your changes, go back to the registration flow and click the Republish button.

Create flow branches

You can create branches in the flow to cater to different audiences. For example, if an employee of your company tries to register for your event, you can take them directly to the thank you page, and you can take the rest of the users through the usual flow.

To create a branch

Go to the step that requires branching and go to the editing page.
Select the Branching tab. The default branch step is the immediate step after the root step and the same is shown in the list.
Click on the +Add branch button
On the branch edit form, enter the following:
1. Select the field on which branching condition is to be applied.
2. Select the appropriate condition clause
3. Enter the desired value.
4. Add more conditions if required by clicking the +Add Condition. In between two conditions, you can select an operator namely, 'Or' or 'And'. You can also delete conditions by clicking Delete condition option.
5. Select the Go to step from the dropdown with the default branch in mind. This is the step to which the branch should lead.
  
  Once you've added the Go to destination, you cannot change it. You would need to delete the branch and start over.
  Ensure that you've created all steps in the right order before you get started with the branching logic. You can use spreadsheets or drawing boards to visualize the flow before you create it.
You can edit your branch name if required. The branch names are displayed on the flow line and allows your team members to quickly identify the branch by its name.

This creates a branching logic for your registration flow.

You can view the branching conditions by hovering over the branch name.

You can create steps in between a flow by clicking + button in the flow line, the step it was pointing to before creating a branch will be the default step

Was this article useful?

Yes

Comments (0)