Workday®: Page Identification and Conditions

Download as PDF

Brief Overview

We identify pages using Workday® Vars instead of URLs since the URL changes (since Workday® is a single page application (SPA)).

How it Works

There are three Workday® segments to choose from:

1. walkMeWorkday.segmentation.flow.Page
   • Use the current value filler to load the information of the page you are currently on. This rule type should always be used in combination with a sub-page rule. Connect the two rules using “AND.”
2. walkMeWorkday.segmentation.flow.subPage
3. From Pages, you can access different sub-pages. Each sub-page also has a unique variable.
   • If no sub-page is available use the operator “Does not Exist.” This rule type should always be used in combination with a page rule. Connect the two rules using “AND.”
4. walkMeWorkday.segmentation.flow.forms
5. Identifies forms specifically. Forms have a special structure (activated / not activated), and have indicative names that we extract using a variable.

There is a Workday® option in the Segmentation Rule Engine that allows you to use these variables automatically. You should select the object from the drop-down menu in the condition builder.

Page Segment and Conditions Best Practices

• Some of the same pages appear in different places in the site / in other processes. In that case you need to find an element on screen to add to the rule.
• Not all pages have the Page segments. For those that don’t, try to rely on on-screen-elements or avoid having to use the rule.
• The most specific variable is the form variable. That usually makes the page identification stronger.
• It may be important to use a combination of the above variables to identify the page that you want your content to appear on and the state it should be in when the content does or does not appear.
• It can be helpful to make conditions like variable “does not exist” or is undefined.
• Avoid adding redundant rules.
• variables can changes depending on how you get to the page. Test the condition by navigating to the page in different ways (e.g., via search bar, Worklet, etc.).
• Apply global segmentation instead of display rules where possible to optimize for performance.
• When adding multiple rules, set the Rule Engine to identify high-level elements first (e.g., set it to identify by URL or Var before evaluating for jQuery for on-screen elements).
  • Read more here.

Pro-tip: You can use a URL if it’s associated with a custom dashboard and the user is completing a process/transaction, as the pages on which the process/transaction occurs have a unique Task ID you can see in the URL.