Walk-Thru Flow Steps allow you to change the way that users go through a Walk-Thru Flow process. Flow Steps are an essential part of developing Walk-Thru Flows that accommodate different situations and types of users.
This article is about the new Walk-Thru Flow app. Read the Walk-Thru (Classic) version of this articel
What's the difference between Walk-Thrus and Walk-Thru Flows?
Let's Talk A Bit MoreWalk-Thru Flows are created using steps and Flow Steps. Steps in a Walk-Thru Flows are visible to the end user and give them guidance on their website. Flow Steps are not visible to the end user, allow you to control how the Walk-Thru Flow plays.
Some examples of what Flow Steps can be used for include:
- Split a process: Create multiple ways for users to complete a process with a single Walk-Thru Flows
- Wait for a page to load: Verify that users reach a page before continuing a Walk-Thru Flows
- Error Proof your Walk-Thru Flow: If users get an error during a process create additional steps to help them resolve their errors
- Redirect a user to a specific page: Save time by taking users right to a page where their Walk-Thru Flow begins
- Take control of your user’s computer: Take action by clicking, hovering, typing or selecting items on screen for your user.
- Save time by taking users right to a page where their Walk-Thru Flows begins
How It WorksFlow Steps allow you to control the way that different users complete your Walk-Thru Flows and using them is an essential part of building. Flow steps are not visible to your users and are configured to perform an action while a Walk-Thru Flows is playing.
Many Flow Steps, such as Splits and Wait for, use the Rule Engine to determine if an action should take place. For example, a Split will use the Rule Engine to decide if a user should continue on the current flow or be branched to a different one. With a Wait for, WalkMe can actually pause the Walk-Thru Flows until the Rule created is met and then will continue playing the Walk-Thru Flow. Flow Steps that use the Rule Engine will display a Rule Summary tooltip icon, helping you easily see the rule created. Flow Steps that use the Rule Engine will display a Rule Summary tooltip icon, helping you easily see the rule created.
Other Flow Steps take action when the user reaches them in a Walk-Thru Flows. For example, when a user is playing a Walk-Thru Flows they may get to a Page Action Flow Step that redirects them to a new URL.
Accessing Flow Steps:Hover over any Add New button in your Walk-Thru Flow to see Flow steps in the Menu.
A Split allows you create an alternate way of going through a Walk-Thru Flow. For example, you may have additional steps in a process that only certain users must complete. A Split uses the Rule Engine to determine if a user should change which flow they are on. If the Rule created for your Split is True then the user is taken to an alternate branch which may include different steps. If the Rule for a split is False then the user will continue down the flow as normal.
Wait for A Wait for allows you to pause a Walk-Thru Flow for a period of time. You may configure your Wait for to pause a Walk-Thru Flow for a specific time duration or use the Rule Engine to determine when to continue playing your Walk-Thru Flows. For example, you may want to set your Wait for using a Rule that checks if the user reaches a specific page before continuing your Walk-Thru Flow. Another example is that you may use a Wait for to delay your Walk-Thru Flows for a few seconds if you would like the user to have time to orient themselves on a new page before playing the next step.
Custom Actions Custom Actions allow you control what happens on your user screen. This can automate specific tasks for users and help them complete processes more easily and save time.
There are 4 types of actions:
- Custom Action: Click, Hover, Focus, Fill Text or Select List Value. Instead of using a step to give directions to users, use Custom Actions to control the application for them. This is especially useful if tasks should be done in a specific way to reduce errors or simply to automate the process. To select a Custom Action, select the element on screen and then choose the action you wish to take.
- Refresh: Refreshes the browser window. In some processes changes only take effect when a browser window in refreshed. This Page Action does it for the users.
- Open Menu: Open the WalkMe Menu to show users available WalkMe items. This Page Action is often used at the end of a Walk-Thru Flows process to encourage users to continue using items placed in the Menu.
- Redirect: Take users to a completely different URL. Use a Redirect to take users directly to a form or page where they start a process instead of making steps that navigate them there.
Connect to Walk-Thru Flow
A Connect to Walk-Thru Flow allows you to switch your user to another Walk-Thru Flow. You have the option to create a new Walk-Thru Flow when adding this Flow Step or selecting a premade Walk-Thru Flow. Using Walk-Thru Flow you have already created is a great strategy for breaking down a process into different parts. For example, creating a contact in your system may be used in several processes. Instead of creating these steps for each Walk-Thru Flow, you can create a separate Walk-Thru Flow for it and connect to it from the other Walk-Thru Flow. This is also convenient for updating this process in the future, so if the create a contact process is updated in the future you only have to update one Walk-Thru Flow instead of all the processes that connect to it.
Error Handling Group
Error Handling Groups allow your Walk-Thru Flow to show specific steps to a user if they make an error during a process. Adding an Error Handling Group allows you to use the Rule Engine to check if the user has generated an error message. If the Rule you create is true, meaning an error is detected, you may add steps into your Error Handling Group to help the user to correct their mistakes and complete the process. When all steps are played in the Error Handling Group, WalkMe checks the Rule again to see if an error message still appears. If the user has generated another error message then it replays the steps in the Error Handling Group.
Error Handling Groups are usually added to a Walk-Thru Flow when the user is most likely to get an error message, for example when clicking the submit or done button after filling in information.
Switch to Frame Switch to Frame Flow Steps allow your Walk-Thru Flow to switch from one URL to another, which may occur if your process has steps in an iFrame or Popup. These URLs may have different domains as long as the WalkMe Snippet is installed on both of them and your account is configured to work Cross Domain. WalkMe stores data locally while you play a Walk-Thru Flows. If your Walk-Thru Flows plays across different domains, regardless of whether the different domain is in an IFrame or a separate window, your account must be configured to work across these different domains. If you encounter issues, contact your Customer Success Manager to ensure that your editor account is configured to use Cross Domain Storage.
In many cases WalkMe will detect that your next step is in an iFrame and automatically add the the Switch to Frame Flow Step to your Walk-Thru Flows.
When a Walk-Thru plays a Switch to Frame Flow Step, WalkMe checks the rule for it to determine the URL it should switch to and if that URL is loaded in an IFrame or a Popup window. WalkMe then switches to this URL and looks for the element of the next step.
Switching to an IFrame (aka Auto created Switch to Frame)
If you want to switch back again to the original frame, simply use another Switch to Frame Flow Step.
Learn More about Switch to Step ( Used also in Walk-Thrus).
Set WalkMe Data
Using WalkMe Data allows you to work with more complex scenarios by using WalkMe cookies as markers for user behavior. For example, if a user visits your site multiple times without completing their onboarding, you could use WalkMe Data to count the number of visits and show a ShoutOut on Day 3.
WalkMe Data functions like a site cookie. When placed on the user’s computer, it has a name (key), value, and duration and can be referenced later by WalkMe. By using rules in the rule engine you’ll be able to test for the presence or value of WalkMe Data on the user’s computer, and have actions take place as a result. These cookies can have any name (key) but should not have spaces. The duration is measured in seconds and can be made to stay on a user’s computer for various lengths of time whether that amounts to seconds, minutes, days, or even years (up to a maximum of 10 years).
Learn more about WalkMe Data
Best Practice:It is recommended that you rename all Flow Steps so they describe when the action will take place. For example, instead of just leaving the name”Wait For”, customize it to “Wait for checkout page”.