For urgent and critical tasks, such as a mandatory computer update to prevent cyber-attacks, WalkMe ShoutOuts are effective for grabbing user attention and driving immediate action. A ShoutOut positioned in the middle of the screen with a single call to action (CTA) button to complete the update ensures high visibility and encourages prompt compliance. Including only one CTA avoids distractions and aligns with the urgency of the task, as users are guided directly to theupdate process without options to delay or seek additional information.

The other options are less effective:

Option B(ShoutOut at the bottom) is less noticeable and allows users to delay action, which is risky for a critical update.

Option C(Launcher with a Knowledge Base article) provides information but doesn’t directly facilitate the update process.

Option D(ShoutOut with a ‘Remind me tomorrow’ button) undermines the urgency by allowing users to postpone the update.

Extract from Official WalkMe Documentation:

Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.9: ShoutOuts):

“ShoutOuts are ideal for urgent announcements requiring immediate user action. Positioning a ShoutOut in the center of the screen with a single, clear call to action maximizes engagement and drives compliance with critical tasks.”

The courseAdvancing Your Skills in Building WalkMe Solutionsadvises:

“For time-sensitive and mandatory actions, such as security updates, use a centrally placed ShoutOut with a single CTA to ensure users prioritize the task. Avoid options that allow postponement to maintain urgency.”

Option A is the best strategy for this critical use case.

To ensure the Smart Walk-Thru starts only on product pages with a Subscribe button, the Start Point must combine URL and element conditions. The ruleCurrent URL -> Contains -> /product-page AND Element on screen -> Is Visibletargets pages with “/product-page” in the URL (covering all product pages) and checks for the Subscribe button’s visibility. This ensures the Smart Walk-Thru is available only on relevant pages, following best practices for precise and reliable Start Points.

The other options are incorrect:

Element On Screen -> is visible(A) is too broad, applying to any page with the element.

Current URL -> is exactly ->www.PetShop.com/product-page(C) is too restrictive, missing subpaths.

Current URL -> Contains -> /product-page/mixed-bird-seeds OR Element on screen -> is Visible(D) is too specific to one product and uses OR logic, allowing starts on non-relevant pages.

Extract from Official WalkMe Documentation:

According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.2: Smart Walk-Thrus):

“For Start Points, combine URL rules (e.g., ‘Current URL contains /product-page’) with element visibility checks (e.g., ‘Element on screen is visible’) to ensure Smart Walk-Thrus start only on relevant pages.”

The courseGetting Started with Building WalkMe Solutionsstates:

“Use AND logic in Start Points, like URL contains and element visibility, to restrict Smart Walk-Thru initiation to pages meeting all criteria, ensuring relevance.”

Option B is the best Start Point rule.

jQuery is a powerful tool in WalkMe for advanced element targeting and dynamic interactions. The correct use cases are:

If the WalkMe element selector algorithm is not consistently identifying your element(B): jQuery selectors provide precise targeting when WalkMe’s default algorithm struggles with dynamic or complex elements.

To grab a dynamic value from an on-screen element and incorporate it into a ShoutOut for a personalized experience(D): jQuery can extract values (e.g., a username) for use in personalized content.

To target a very specific element on your website(E): jQuery allows fine-tuned selectors for elements with unique attributes or structures.

The other options are incorrect:

Redesigning the entire layout of WalkMe balloons(A) is done via Global/Local Design settings, not jQuery.

Closing the WalkMe menu and starting an Onboarding task(C) uses WalkMe’s native APIs or rules, not jQuery.

Extract from Official WalkMe Documentation:

Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.7: jQuery Selectors):

“Use jQuery in WalkMe to target specific elements when default selectors fail, extract dynamic values for personalization (e.g., in ShoutOuts), or address complex DOM structures requiring precise element identification.”

The courseAdvancing Your Skills in Building WalkMe Solutionsexplains:

“jQuery is essential for scenarios like inconsistent element detection, grabbing dynamic data for personalized content, or targeting unique elements with custom selectors.”

Options B, D, and E are valid jQuery use cases.