Pausing WalkMe with Wait For Conditions

Objective

After completing this lesson, you will be able to pause WalkMe with Wait For conditions.

Pause WalkMe with Wait For Condition

A Wait For Condition will make the Smart Walk-Thru wait for a certain amount of time or until a certain condition is met before continuing to the next step.

Watch the video to learn about Wait For Condition.

Key Takeaways

A Wait For Condition has several uses. Use it to wait for:

  • Amount of Time: Wait for a few seconds when a user reaches a new page so that they have time to look around before continuing the Smart Walk-Thru.
  • URL: Wait for user to reach a certain URL before continuing.
  • Element On-Screen: Wait for the page to display a certain field before continuing.

The Wait For Condition can be configured to wait for a specific time duration or use the Condition Builder to determine when to continue playing your Smart Walk-Thrus.

Pausing WalkMe with Wait For Condition

Waiting with Wait For Conditions

A Wait For Condition can be added anywhere in a Smart Walk-Thru. When WalkMe gets to the Wait For Condition, the Smart Walk-Thru will wait to play the next step until a certain number of seconds have passed or the associated rule(s) is/are True.

The figure shows a Wait For Condition in the WalkMe Editor.

The image shows a Wait For Condition in the WalkMe Editor.

Why Delay Flows Intentionally?

Wait For Conditions can be necessary for making the user experience feel more smooth and to make sure Smart Walk-Thru steps play at the correct pace.

While it won't be part of our initial build, a Wait For is usually added as a troubleshooting tactic when we notice something not functioning ideally.

For example, we don't want our Smart Walk-Thru steps to preemptively play when the user hasn't even reached the next step yet! It's is also commonly used when the page loads too fast, and WalkMe doesn't have the time to detect the element which might cause the Smart Walk-Thru to stop.

The figure shows how the Enter Quantity step is playing too quickly, causing it to cover drop-down selection.

The image shows how the Enter Quantity step is playing too quickly, causing it to cover drop-down selection.

Next, we'll go through a scenario on our Eddie's Depot platform. In this scenario, our previously built Split Step is evaluating too fast, causing our guidance in the Yes branch to not play correctly. Because of this, our Split Step, which was created to reduce user confusion, is now causing more confusion because it isn't evaluating properly.

To resolve this confusion, we'll add a Wait For Condition to our Smart Walk-Thru to pause WalkMe so that it may evaluate our Split Step more accurately.

Exercise: Create Wait For Condition to your Smart Walk-Thru

Below is a software simulation that will guide you through how to create Wait For Condition for your Smart Walk-Thru. The simulation will replicate what you will experience when you build in your own Editor.

Best Practices for Wait For Condition

Timed Conditions

When creating Wait For Conditions, we can choose to wait for a specific amount of time, or to wait until certain page conditions are met using the Condition Builder.

As a best practice, we generally recommend using a timed condition for processes that include Auto-Steps. Automation can be fast. Sometimes too fast. Wait For Conditions help WalkMe slow down and give the platform a bit more time to load properly before moving on.

The figure shows the best practices for Wait For Conditions.

The image shows the best practices for Wait For Conditions.

Name Wait For Conditions

Naming our Wait For Conditions is an important step in the WalkMe building process. These steps can be based on time or conditions established by us in the Condition Builder.

Something like conditions Wait for the Success Page URL tells us, as Builders, exactly what we need to know about this Wait For Conditions and helps us maintain our content more efficiently.

The figure shows the step for Wait For Conditions.

The image shows the step for Wait For Conditions.

Great job! Now that we've covered Split Steps and Wait For Condition, we'll show how we can speed up processes with automation!

Log in to track your progress & complete quizzes