C_WME_2506 Exam Dumps - SAP Certified Associate - WalkMe Digital Adoption Consultant

The issue described—where a SmartTip scrolls with the page before snapping back to its intended position—indicates that the SmartTip is not properly anchored to its associated element. TheLock to Elementconfiguration ensures that the SmartTip remains fixed relative to the selected element, even during scrolling or dynamic page changes. Enabling this setting in the WalkMe Editor prevents the SmartTip from moving independently and ensures it stays aligned with the target element.

The other options are incorrect:

Display Condition(A) controls when the SmartTip appears based on rules, not its positioning behavior.

Z-Index(B) affects stacking order, not scrolling alignment.

Appears and disappears as a result of end user action(C) relates to element visibility triggers, not anchoring during scrolling.

Extract from Official WalkMe Documentation:

According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.5: SmartTips):

“The ‘Lock to Element’ setting ensures that a SmartTip remains anchored to its selected element, preventing it from scrolling independently or misaligning during page interactions like scrolling.”

The courseAdvancing Your Skills in Building WalkMe Solutionsadvises:

“If a SmartTip moves with page scrolling before snapping back, enable ‘Lock to Element’ in the Editor to maintain consistent positioning relative to the target element.”

Option D, Lock to Element, resolves the scrolling issue observed during Quality Assurance.

To display a Launcher on every product page, the Current URL rule must target the common pattern in the product page URLs. The example URLs share the segment “/product,” which uniquely identifies product pages. Using the ruleCurrent URL > contains > /productensures the Launcher appears on all pages with “/product” in the URL, following best practices for specificity and flexibility. This approach avoids overly broad or restrictive rules and accommodates potential URL variations.

The other options are incorrect:

is like > shopme.walkme.com/product(A) is too specific, missing subpaths like “/taylor-swift-1989/.”

is like > walkme.com(B) is too broad, matching non-product pages.

contains > shopme.walkme.com(D) is also too broad, including non-product pages on the domain.

Extract from Official WalkMe Documentation:

Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 1.9: URL Rules):

“For URL-based rules, use ‘contains’ with a unique URL segment (e.g., ‘/product’) to target specific page types, ensuring flexibility and accuracy for dynamic URLs.”

The courseGetting Started with Building WalkMe Solutionsadvises:

“When targeting pages like product pages, use ‘Current URL contains’ with a distinctive segment like ‘/product’ to capture all relevant pages without including unrelated ones.”

Option C is the best URL rule for the Launcher.