Workday®: Page Identification and Conditions

Last Updated November 29, 2023

Download as PDF

Share Article Copy link to clipboard

Brief Overview

The best practice to identify pages in Workday® is by using vars instead of URLs. This is because Workday is a single page application (SPA) and the URL changes.

How It Works

There are three Workday® segments to choose from. 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 dropdown menu in the condition builder.

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"

walkMeWorkday.segmentation.flow.subPage

• 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"

walkMeWorkday.segmentation.flow.forms

• Identifies forms specifically
• Forms have a special structure (activated / not activated), and have indicative names that we extract using a variable

Page Segment and Conditions Best Practices

• Some pages appear in multiple places in the site and in other processes
  • If that is the case, you need to find an element on screen to add to the rule
• Not all pages have page segments
  • For those that don't, try to rely on on-screen elements or avoid using the rule
• The form variable is the most specific variable and usually makes the page identification stronger
• It may be important to use a combination of 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 (for example, nav bar, search bar, worklet, etc.)
• Apply global segmentation instead of display rules where possible to optimize performance
• When adding multiple rules, set the Rule Engine to identify high-level elements first (meaning, set it to identify by URL or var before evaluating for jQuery for on-screen elements)
• Learn more about the Rule Engine