Introducing WalkMe Environment and Apps
Strategizing with WalkMe
Creating Logic with Condition Builder
Using SmartTips
Using Smart Walk-Thrus
Managing Smart Walk-Thru Flow Steps
Configuring Resources
Exploring Shuttles
Managing Onboarding Tasks
Implementing Entry Points & Menu
Creating Launchers
Designing ShoutOuts
Implementing Segmentation
Previewing & Publishing Content
Troubleshooting Content Issues

Creating Efficient Conditions

Objective

After completing this lesson, you will be able to optimize conditions so that your content plays efficiently.

Introduction

The sample rule shown in the image below to identify each rule component and its correct example:

  • Rule Type → Current URL
  • Operator → Contains
  • Value → /shop-all
URL filter rule set to contain /shop-alldivider

Let's do a quick example to tie these concepts together.

URL Rule Example

Let's say you have a customer facing website called Klaw. The URL of the site is https://klawsign.com/app/

You want to have a ShoutOut with an important message automatically appear when a user gets to the Setting Page. You can use the Condition Builder for this!

Examine the URL Behavior

When you navigate to the Settings page, you notice that the URL now includes the word "settings" at the end. You'll use that in rule!

Klaw E-Sign settings page showing Leslie Carlucci's profile.

Create Rule

You will tell WalkMe to look for the URL to contain the word "settings." You can focus on the most unique portion of the URL and exclude everything else.

So my rule statement would look like this: Current URL → contains → /settings.

* Contains is the most common URL Rule option. It is typically used for the vast majority of Current URL rules.

Condition rule: Current URL contains /settings, validated.

Summary

Current URL rules are the most common and simplest rules to implement. You recommend always checking to see if you are able to use a URL rule first and then exploring other options from there as needed. These rules are easy for WalkMe to evaluate.

*If your site is a Single Page Application (SPA), URL rules will not be as relevant. This is because the URL often does not change, and the page does not refresh often.

Best Practices

There are a few tips and best practices to keep in mind as you create conditions in the Condition Builder.

Indicator Icons

Each time you write a rule, there will be an indicator icon to the far right-hand side of that rule. It will be either a green checkmark, red X, or a yellow pencil icon.

  • If you see the green checkmark, it means the rule statement is currently evaluating as TRUE, and the content would appear for the end user.
  • If you see the red X, the rule statement is currently evaluating as FALSE.
  • If you see the yellow pencil icon, it means the rule is incomplete. Finish editing the rule, and the indicator will change!

As you are building and troubleshooting, the indicator is the quickest way to check the condition logic.

Departments Page condition rules using URL contains and wildcard filters.

Remove URL Domain

To simplify the URL as much as possible when using this rule type. This means deleting the domain information and extra text. Let's use the https://klawsign.com/app/settings/ URL as example.

Domain: WalkMe will already be technically configured to show up on platform - or in this case, Klawsign. WalkMe will already know which environment is a TEST environment, and which environment is the live PRODUCTION environment. You do not need to tell WalkMe again to show up on Klawsign in every rule.

Additionally, so you do not have to create additional rules or rebuild rules so content will work in both TEST and PRODUCTION, simply delete the domain altogether (unless it is specifically necessary for your use case), and just write one rule that works for both environments!

https:// - Also remove the "https://" text from the beginning of the URL. It is not necessary.

URL condition rule set to /settings

Simplify URL

Essentially, remove all portions of the URL that are not specific to the rule. In most cases, you will want to focus on the unique portion of the URL that tells exactly which page the user is on.

In case, you took the URL down from:

https://klawsign.com/app/settings

to

/settings.

Current URL contains /settings condition configured

In the next section, you will start to talk about how rules can be grouped together.

Multiple Rules and Grouping

Using Multiple Rules

As you build more, you may find yourselves wanting to create more complex logic with conditions. WalkMe gives the ability to create multiple rules and group rules together.

Watch the video to understand the concept of multiple rules and grouping.

Key Takeaways
  • Depending on the use case or business need, some solutions may require multiple conditions or rules in order to play the way you want them to.
  • Grouping is a way to ensure that, when using multiple conditions or rules, they are still organized and easy to follow in the Condition Builder.

When Would I Add More?

Maybe there are multiple things you want to make sure are true for a user before they see content.

Example: On a site, only certain users can perform the task of adding departments. Therefore, you only want a Launcher to appear for users who are on the departments page, and the + New Departments button is present for them.

Dialog for setting launcher display conditions with URL and element rules.

Note

A URL and Element on Screen rule is used above.

The And/Or Toggle

You'll want to adjust the "And" or "Or" toggle operator between different rules so that WalkMe undertands how the statements relate to one another.

  • And tells WalkMe that both or all of your conditions must be true for content to show for users. It narrows down who will see content.
  • Or tells WalkMe that either of your conditions can be true for content to show for users. It broadens who will see content.

For the example provided above, you would want to use an AND operator. The user must be on the departments page AND the + New Department button should be visible.

divider

By grouping rules in the Condition Builder, you can add more conditions and rules for more complicated logic. It is a process that organizes rules and conditions to evaluate them collectively.

  • When you have two or more rules under one condition and at least one rule outside of that condition, the rules under the same condition will be grouped together automatically.
  • When you have more than two rules, you can also manually group at least two of these together.

Grouping helps in creating complex logical structures where multiple conditions need to be evaluated together.

Understanding condition and rule evaluations

When you have multiple conditions, rules, or groups, and you're not sure if your condition is working, then you can use the visual markers to see how rules are being evaluated and if the overall condition for your content will work.

The condition evaluations will be one of the following:

  • True (Green Tick)

  • False (Red X)

  • Incomplete (Yellow Pencil Icon)

  • Cannot Assert (Gray Question Mark)

In this example, you have created two conditions for WalkMe to play:

  1. One for either of two URLs containing: /partners OR /cart-page.

  2. One for specific day of the week: Tuesday.

You can see from the markers beside each line that one of the Current URL conditions is evaluating as true and one as false, and that the Date condition is also evaluating as true.

SmartTip Set display conditions using URL and date criteria.

If at least one of these conditions is true, then the final evaluation is true because you're using the "Or" operator between the conditions. In this example, SmartTips Set will play, as shown by the green tick at the top of the Condition Builder window.

Rule evaluation for the overall condition

Note

When looking at evaluation, always check the operator(s) between rules/conditions to see if it is AND or OR. This is also called an operator, which might be confusing, but is only used between rules/conditions and is not specific to one rule.

In the next section, you will begin to talk about how to structure conditions to ensure your WalkMe content works efficiently.

Exercise: Use the Condition Builder

Below is a simulation that will guide you through using the Condition Builder to build conditions for a SmartTips set. To use the Condition Builder to determine where the SmartTips Set should play. The simulation will replicate what you will experience when you build in your own Editor.

ExerciseStart Exercise

Summary

Creating Conditions Using Condition Builder

  • The Condition Builder is a fundamental part of building with WalkMe. It is found everywhere.

  • Using the Condition Builder is how you will determine how content plays.

  • It's possible to add more than one rule, and this may lead to grouping rules together.

Related Resources

Condition Builder Knowledge Base Article

This article includes an overview of the Condition Builder.

View Article

Rule Types

This article from Knowledge Base covers the Rule Types available.

View Article
Learning

SAP FacebookSAP YoutubeSAP LinkedIn