Exploring Condition Builder

Objective

After completing this lesson, you will be able to explore Condition Builder to create logic.

Introduction

The Condition Builder is a part of WalkMe that allows users to create specific conditions or rules for when and how content is displayed and activated.

By creating these rules, you can ensure that content only appears at the right time to the relevant audience, which will improve the user experience and increase effectiveness and engagement.

Watch the video to get an overview of the Condition Builder.

Key Takeaways
  • The Condition Builder is a fundamental part of building with WalkMe. It is found everywhere.
  • We can use the Condition Builder to determine how content plays.
  • Conditions are created using a rule or multiple rules.
  • WalkMe evaluates these rules in the background as users interact with your webpage or application, thus determining how the content behaves.

What is the Condition Builder?

As we learned in our intro video, the Condition Builder helps us create conditions that determine how, when, and where content is displayed to our audience. It can be found everywhere in the Editor.

When we create a WalkMe solution, such as a SmartTips Set or a ShoutOut for example, we will use the Condition Builder to define rules for when that specific solution should appear for end users.

Lets get comfortable with some of the terminology we'll be using going forward: Conditions & Rules.

What are Conditions?What are Rules?

A condition is the overarching criteria that we wish to set that will determine how WalkMe content plays.

Rules are the specific logic statements that we create to define the Condition.

Conditions are made up of one or more rules.

A condition can be made up of multiple rules.

Why use the Condition Builder?
  1. Personalize User Experiences: Tailor digital content to specific users or user groups based on their roles, actions, location, or other criteria. This ensures that users only see the most relevant content, which can improve user engagement and satisfaction.

  2. Provide Context-Sensitive Guidance: Set conditions for when content will appear based on the user's current context, such as the page they're on or the actions they've taken. This can make guidance more timely and relevant, increasing its effectiveness.

  3. Increase ROI: Personalization and context-sensitive guidance can improve user engagement, satisfaction, and productivity, all of which can contribute to a higher return on investment (ROI) from your digital adoption efforts.

Divider

We'll talk about when to use the Condition Builder more throughout the course, but to begin, let's look at an example.

  • An organization wants to start using SmartTips to provide reminders of important information in their online store.

  • They only want the SmartTips to display on the Cart page of their site.

In the SmartTips settings we create the condition, 'Only play on Cart page'. Within that condition, we have created a rule so that the SmartTips only play on a URL that contains the important /cart-page? portion.

The image shows the SmartTip display conditions for Cart page access".

The image depicts a software interface for setting display conditions for a SmartTip Set. It shows the condition labeled Only Play on the Cart page, detailed with a requirement that the current URL must contain '/cart-page?'. The clean design features icons for adding conditions and checking boxes. A color scheme of white, blue, and subtle green is used for clarity.

The Condition Builder will be used in a ton of other places. As you begin to build with WalkMe, you'll see it when you:

  • Continue creating more Apps and want to determine how they will play.

  • IntroduceStart Points to Smart Walk-Thrus to make sure they're intuitive for end users.

  • Start to add Goals in order to track if users complete processes for which we've built content.

How does the Condition Builder Work?

Go through the steps to understand at a high level what will happen when you create content and use the Condition Builder. In later lessons, we'll talk in more detail about how the Condition Builder works under the hood.

Step 1

From the Editor, we will first create the specific app content, such as a SmartTips Set or ShoutOut.

The Editor screen showing SmartTips Set.
Step 2

Within the settings for that piece of content, we will go to the Condition Builder by clicking "Create rules."

The Condition Builder screen showing Create rules.
Step 3

We'll build the conditions & define the rules for how we want the piece of content to display.

When naming the condition, we'll want to choose a name that reflects how we want the content to behave.

For example:

"Only Play on the Cart Page"

The screen showing the Create a SmartTip set display condition.
Step 4

When users interact with the webpage or application, WalkMe then will evaluate the condition's rules in a top down order.

A webpage example when WalkMe then will evaluate the condition's rules in a top down order.
Step 5

Rule evaluation takes place

If a condition evaluates as TRUE, then the content will play. If it evaluates as FALSE, then the content will not play.

In the next section, we will look at the components that make up a rule within the Condition Builder.

Rules

Understanding the three components of a rule is important so that you can build the conditions that will be best for the content you want to create.

Watch the video where we will introduce these three components: Rule Types, Operators, and Values.

Key Takeaways
  • Rules are made up of three components: Rule Types, Operators, and Values.
  • The Condition Builder lets you choose from a variety of preset Rule Types.
  • The Rule Types will have related Operators that will dictate the relationship to the values you enter.

Divider

Lets look at an example to recap on each component.

The image displays the structure of a rule statement. Each element is numbered from 1 to 4. Element 1 is labeled Current URL, featuring a globe icon, indicating web navigation focus. Element 2 shows a dropdown menu titled contains, suggesting conditional logic. Element 3 has /cart-page? text box for URL input. A green checkmark beside element 4 denotes successful validation or selection.
Component of the StructureDescription
Rule Type

Rule Types are the different categories that you can check against when creating a rule.

In this example: Current URL

Operators

Operators will set the criteria for how the Value relates to the Rule Type.

In this example: Contains

Value

The value is what we are asking to be true in order to trigger the rule.

In this example: /cart-page?

Evaluation

There is a visual check mark for the rule itself and the overall condition that will display to show if they are currently true, false or incomplete.

  • Green Tick = True
  • Red X = False
  • Yellow pencil = Incomplete

In this case the Current URL does contain /cart-page? so the rule evaluates as true.

Rule Types

When we create a rule, the first thing we will select is the Rule Type. This is the criteria that our rule will apply to.

The 3 most common Rule Types and their description are as follows.

Checks against the URL that the user is currently on.Checks against an element you select on-screen for things such as visibility, content, length, or type.Checks dates such as day of the week, month, or a specific date. If item is set to auto play until a certain date, it will expire at the end of that day.

These are the ones we'll focus on in this course, but to learn more about the various Rule Types refer to the Condition Builder Support Article.

Operators

Operators set the specific criteria for our selected Rule Type and how they are evaluated. They define how the rule should function in relation to the Value.

Let's look at some of the possible Operators for our three main Rule Types: Current URL, Date, and Element on Screen.

Current URL

This Rule Type will have Operators such as "contains," "value is like," or "is exactly."

Choosing a URL Rule Type will default to a "value is like" operator and automatically enter the URL you are currently on as the value.

Here we've switched to the Operator "contains" followed by a partial URL: /cart-page? as the Value.

When to use: If we wanted content to only play on the a specific website URL.

The image displays a dropdown menu within a web interface for setting URL conditions, likely related to web development or digital marketing. The dropdown, titled contains, offers various options: doesn't contain, value is like, value is not like, is exactly, is not exactly, is per Regular Expression, and is not per Regular Expression. The interface is clean, with a focus on functionality.

Note

When using 'contains,' we can remove the https:// protocol and domain information.

Note

Using the "contains" Operator

  • "Contains" is the preferred operator when using a Current URL Rule Type.

  • URLs can often contain dynamic elements that change such as session ID or user information.

  • Using "Contains" focuses only on the "static" elements of the URL, allowing us to remove everything else that may change and cause our rule to not work.

  • However, we need to use it wisely to avoid applying the rule to more pages than desired. Always ensure the portion of the URL is unique to the page where we want the content to play.

Element on Screen

This Rule Type will have Operators such as "is visible" or "is not visible."

In the image, we are using the "is visible" Operator. When you select this Rule Type, you'll be prompted to select the element.

When to use: If we wanted to display content next to an on screen icon that only appears at a specific part of a process.

The image depicts a dropdown menu interface within a software application, presented in a clean, minimalistic design. The focus is on a selection of conditions: is visible, is not visible, is selected, is not selected, text is exactly, text is not, text is like, and text is not like. It's part of a feature for setting element visibility and selection criteria.

The figure displays that the Element on screen Is visible.

Date

This Rule Type will have Operators such as "weekday is" or "month is."

In the image, we are using the "weekday is" Operator followed by "Friday" as the Value to ensure that our content only plays on a Friday.

When to use: If we wanted to play content reminding employees to complete a weekly admin task before finishing their working week..

The image shows a digital interface for setting date conditions. There are three dropdown menus: Date, weekday is, and Friday. The selected condition weekday is appears ticked, with options such as is, is not, From, Until, month is, and year is visible. Additionally, there's an option to + Add Condition, suggesting further customization possibilities.

Note

Date - Weekday is

Values

The Value for each rule will vary depending on the Rule Type and Operator.

With our 3 Rule Types in mind, let's look at common values for each.

Current URL

Rule Type = Current URL

Operator = Contains

The Value must be a section of the URL.

Watch the video to know more. Note that the video doesn't support audio.

Element on Screen

Rule Type = Element on Screen

Operator = Is Visible

Selecting element on screen will prompt us to select the element from the page, this is our Value.

Watch the video to know more. Note that the video doesn't support audio.

Date

Rule Type = Date

Operator = Is

When we choose the Date option with an "is" Operator, then our Value will be a specific date that must be chosen from the calendar picker.

Watch the video to know more. Note that the video doesn't support audio.

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

Log in to track your progress & complete quizzes