SAP C_WME_2506 - SAP Certified Associate - WalkMe Digital Adoption Consultant

TheSplitfeature in a Smart Walk-Thru allows Builders to create alternate paths based on user actions or conditions, such as selecting a specific dropdown option. In this case, if users choose a dropdown option that requires additional steps, the Split feature can branch the Smart Walk-Thru to guide them through those steps before rejoining the main flow. This ensures the Smart Walk-Thru adapts dynamically to user choices, providing tailored guidance.

The other options are incorrect:

Start Point(A) defines where a Smart Walk-Thru begins, not alternate paths.

Wait For Condition(B) pauses the flow until a condition is met, not for branching.

Popup Step(D) displays a message or input field, not for managing alternate paths.

Extract from Official WalkMe Documentation:

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

“The Split feature enables branching in Smart Walk-Thrus based on user actions, such as dropdown selections, allowing customized guidance for different paths.”

The courseGetting Started with Building WalkMe Solutionsexplains:

“Use Split steps to handle alternate paths in a Smart Walk-Thru, like additional steps for specific dropdown choices, ensuring flexible and accurate guidance.”

Option C, Split, is the correct feature for this scenario.

WalkMe’sDigital Experience Analytics (DXA)supports organizations bytracking how users interact with predefined on-screen elements, such as buttons, forms, or pages. This provides insights into user behavior, friction points, and adoption gaps, enabling organizations to optimize processes and improve digital experiences. DXA integrates with WalkMe Insights to deliver actionable data.

The other options are incorrect:

Replacing manual processes(A) is a benefit of automation, not DXA’s primary role.

Creating new applications(C) is outside WalkMe’s scope.

Eliminating training(D) is an exaggeration, as WalkMe supports training, not replaces it.

Extract from Official WalkMe Documentation:

Per the SAP WalkMe Digital Adoption Consultant Study Guide (Section 3.1: Analytics Overview):

“Digital Experience Analytics (DXA) tracks user interactions with predefined elements, offering insights into engagement and pain points to enhance digital adoption.”

The courseWalkMe Fundamentalsexplains:

“DXA helps organizations by monitoring how users interact with on-screen elements, providing data to identify inefficiencies and improve user experiences.”

Option B correctly describes DXA’s support for organizations.

The Dynamic Layout of a WalkMe ShoutOut in the Editor is composed of three layers: theFrame,Canvas, andWidget. TheFramedefines the outer structure and positioning of the ShoutOut (e.g., size and placement on the screen). TheCanvasis the content area where text, images, or buttons are placed. TheWidgetincludes interactive elements, such as the call to action button or close button, that users can interact with. These layers work together to create a customizable and visually appealing ShoutOut.

The other options are incorrect:

Z-index(C) is a CSS property that controls stacking order, not a layer of the ShoutOut’s layout.

Player(E) refers to the WalkMe Player, which delivers content but is not part of the ShoutOut’s internal structure.

Extract from Official WalkMe Documentation:

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

“The Dynamic Layout of a ShoutOut consists of three layers: the Frame, which sets the structural boundaries; the Canvas, which holds the content; and the Widget, which includes interactive components like buttons.”

The courseAdvancing Your Skills in Building WalkMe Solutionselaborates:

“When designing ShoutOuts, understand the Dynamic Layout’s three layers—Frame, Canvas, and Widget—to effectively customize appearance and functionality for user engagement.”

Options A, B, and D are the correct layers of a ShoutOut’s Dynamic Layout.

WalkMe provides a custom jQuery wrapper, wmjQuery, to test and validate jQuery selectors within the WalkMe environment. This wrapper ensures that selectors are evaluated in the context of WalkMe’s framework, accounting for its specific DOM interactions and configurations. To check a jQuery selector, Builders type wmjQuery("InsertSelectorHere") into the browser’s developer console, replacing InsertSelectorHere with the desired selector (e.g., wmjQuery("#myButton")). This returns the matched elements, confirming the selector’s accuracy.

The other options are incorrect:

WMjquery InsertSelectorHere(A) is not a valid syntax and lacks proper formatting.

walkmeJQuery("InsertSelectorHere")(B) uses incorrect capitalization and naming.

jQuery("InsertSelectorHere")(C) uses standard jQuery, which may not account for WalkMe’s specific environment.

Extract from Official WalkMe Documentation:

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

“To test jQuery selectors in the WalkMe environment, use the wmjQuery function in the browser’s developer console. Syntax: wmjQuery("selector"). This ensures compatibility with WalkMe’s framework and accurate element targeting.”

The courseAdvancing Your Skills in Building WalkMe Solutionsexplains:

“When troubleshooting or validating jQuery selectors, always use wmjQuery("selector") in the developer console to ensure the selector works within WalkMe’s context, as standard jQuery may produce inconsistent results.”

Option D, wmjQuery("InsertSelectorHere"), is the correct syntax.

AnOnboarding Taskin WalkMe is a collection of steps or content designed to guide users through a set of actions to complete an onboarding process. The two types of WalkMe content that can be included in an Onboarding Task areSmart Walk-Thrus, which provide step-by-step guidance through processes, andResources, which link to help articles or external documentation to support onboarding. These content types are versatile and align with the goal of guiding users through critical tasks.

The other options are incorrect:

SmartTips and Launchers(A) are not part of Onboarding Tasks; SmartTips are field-specific, and Launchers trigger other content.

Resources and Shuttles(C) are partially correct, but Shuttles only navigate to pages, not guide through tasks.

Smart Walk-Thrus and Shuttles(D) are also partially correct, but Shuttles are not task components.

Extract from Official WalkMe Documentation:

According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 1.8: Onboarding Tasks):

“Onboarding Tasks consist of Smart Walk-Thrus, which guide users through processes, and Resources, which provide supplementary help content to complete onboarding.”

The courseGetting Started with Building WalkMe Solutionsstates:

“Build Onboarding Tasks using Smart Walk-Thrus for process guidance and Resources for additional support, ensuring users have the tools to complete onboarding.”

Option B, Smart Walk-Thrus and Resources, is the correct answer.

To open a support ticket with WalkMe’s technical experts, users should visit theWalkMe World Community, an online platform where customers can access support resources, submit tickets, and engage with WalkMe’s support team. This community serves as the primary channel for technical assistance, offering a streamlined process for reporting issues and receiving expert guidance.

The other options are incorrect:

Insights(B) is an analytics tool for tracking user behavior, not for support.

WalkMe Console(C) is not a standard WalkMe platform for support; it may refer to internal tools.

Admin Center(D) manages account settings and permissions, not support tickets.

Extract from Official WalkMe Documentation:

According to the SAP WalkMe Digital Adoption Consultant Study Guide (Section 1.11: Support and Resources):

“The WalkMe World Community is the primary platform for submitting support tickets to WalkMe’s technical experts, providing access to help articles and direct support.”

The courseGetting Started with Building WalkMe Solutionsstates:

“For technical issues, use the WalkMe World Community to open a support ticket, ensuring prompt assistance from WalkMe’s support team.”

Option A, WalkMe World Community, is the correct place to open a support ticket.

ASmart Walk-Thru Goalis a defined outcome that measures the success of a Smart Walk-Thru in guiding users to complete a specific process or action (e.g., submitting a form, reaching a page). Goals are tracked in WalkMe Insights to evaluate the Smart Walk-Thru’s effectiveness, providingmetrics like completion rates and identifying where users succeed or drop off. This helps Builders optimize guidance to improve user adoption and process completion.

The other options are incorrect:

Option Adescribes step-level tracking, not Goals, which focus on the overall process outcome.

Option Crefers to initiation tracking, not Goals.

Option Dis too narrow, as Goals measure process completion, not just viewing the last step.

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):

“Smart Walk-Thru Goals track the effectiveness of guidance by measuring whether users complete the intended process or action, providing insights into adoption and success rates.”

The courseGetting Started with Building WalkMe Solutionsstates:

“Define Goals in Smart Walk-Thrus to monitor how effectively they help users achieve key actions, using Insights to analyze completion and optimize the flow.”

Option B accurately describes a Smart Walk-Thru Goal.

TheGoalof a Smart Walk-Thru defines the successful completion of the intended process, which in this case is employees submitting their quarterly time. The most precise Goal isUser is on the time submission page and clicks the submit button, as it confirms both that the user has reached thecorrect page and completed the submission action, ensuring the process is fully executed. This Goal is measurable in WalkMe Insights and directly aligns with the process’s objective.

The other options are less accurate:

User inputs time into input fields(A) is a partial step, not the final outcome.

User clicks a submit button(B) lacks context about the page, risking false positives.

User navigates to the time submission page(C) is incomplete, as navigation alone doesn’t ensure submission.

Extract from Official WalkMe Documentation:

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

“Set Goals to reflect the completion of the process, such as a user reaching a specific page and performing a key action, like clicking a submit button, to track success accurately.”

The courseGetting Started with Building WalkMe Solutionsexplains:

“For a process like time submission, define the Goal as the user being on the target page and clicking the submit button, capturing the full completion of the task.”

Option D is the correct Goal for the Smart Walk-Thru.