SAP Certified Associate C_WME_2506 Release Date

To address common support tickets and promote self-service, aMini Menuplaced next to the support ticket form is the best solution. A Mini Menu is a compact, context-sensitive menu that provides quick access to relevant content, such as Smart Walk-Thrus or Resources for the top three support issues. Positioning it near the form ensures it’s highly visible and accessible when users are likely to need help, reducing ticket submissions by guiding users to solutions proactively.

The other options are less suitable:

A Survey(A) collects feedback but doesn’t provide guidance to prevent tickets.

Adding to the WalkMe Menu(C) is less targeted, as users must navigate to find content.

A large ShoutOut(D) is disruptive if shown repeatedly and less effective for ongoing self-service.

Extract from Official WalkMe Documentation:

According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.11: Mini Menus):

“Mini Menus are ideal for delivering context-specific content, such as guidance for common issues, directly on a page. Place them near relevant elements, like a support form, to promote self-service and reduce support tickets.”

The courseAdvancing Your Skills in Building WalkMe Solutionsstates:

“To address frequent support tickets, create a Mini Menu with targeted content and position it near the point of need, such as a ticket form, for quick user access and effective self-service.”

Option B, a Mini Menu next to the support ticket form, is the best solution.

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.

WalkMe Launchers are on-screen elements that can be configured to trigger actions or content, such as Smart Walk-Thrus, Resources, or Shuttles. A key feature of Launchers is their ability to be customized for visibility and positioning, including the option to make them “invisible” by adjusting transparency settings. This makes them ideal for temporarily covering a problematic UI element without requiring code changes to the underlying website. By placing an invisible Launcher over the unwanted UI element, the Builder can block user interaction with it, effectively “hiding” it until developers can remove it.

The other options are less effective for this use case:

A mandatory field Launcheris not a standard WalkMe feature; Launchers are not tied to form validation or mandatory fields.

A Resource to a support articleprovides information but doesn’t prevent users from interacting with the confusing UI element.

A Mini Menuis a navigational tool for accessing content and cannot cover or hide a UI element.

Extract from Official WalkMe Documentation:

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

“Launchers can be customized to be fully transparent using the ghost icon in the WalkMe Editor, allowing them to overlay and block interaction with specific UI elements without being visible to the end user. This is useful for temporarily disabling problematic elements.”

The courseAdvancing Your Skills in Building WalkMe Solutionsnotes:

“In scenarios where a UI element causes confusion and cannot be removed immediately, an invisible Launcher can be placed over the element to prevent user interaction, serving as a temporary workaround.”

Option D is the correct solution, as it directly addresses the need to make the UI element inaccessible without requiring development resources.

To collect end user feedback within WalkMe Insights, the most effective approach is to use WalkMe’s native Survey tool, as it integrates directly with Insights for seamless data collection and analysis. Placing aShoutOut on the feature pagethat activates a WalkMe Survey with multiple questions ensures high visibility and context-specific engagement, as users are prompted to provide feedback while interacting with the new feature. This method leverages WalkMe’s analytics to track responses and correlate them with user behavior, providing actionable insights.

The other options are less optimal:

A Survey in the WalkMe Menu(A) is less targeted, as users may not proactively access it.

A Shuttle to a Google Form(B) lacks integration with Insights, making data analysis cumbersome.

A 3rd party survey tool via email(D) is disconnected from the feature context and WalkMe’s analytics.

Extract from Official WalkMe Documentation:

According to the WalkMe Insights User Guide (SAP WalkMe Digital Adoption Consultant StudyGuide, Section 3.5: Surveys):

“WalkMe Surveys, when triggered by a ShoutOut on a relevant page, are ideal for collecting contextual feedback. Responses are tracked in Insights, enabling analysis of user sentiment and feature adoption.”

The courseAdvancing Your Skills in Building WalkMe Solutionsexplains:

“For feature-specific feedback, use a ShoutOut to launch a WalkMe Survey on the feature page. This ensures users provide input in context, with data seamlessly captured in Insights for analysis.”

Option C is the best approach for collecting feedback within Insights.