There is a new process on your site that is crucial for all employees to complete. Users need to navigate to the time submission page, log their time for the quarter, and submit it in the platform. You have created a Smart Walk-Thru for this process. What should be the Goal?
Correct Answer: A
Question 37
Which is the most preferred Unique User ID setting and the one you should explore first for UUID setup?
Correct Answer: C
The Unique User ID (UUID) in WalkMe is used to track individual users for analytics and personalization. The most preferred setting to explore first is aVariable, as it allows Builders to leverage an existing user identifier from the application (e.g., a user ID stored in a JavaScript variable), ensuring accurate and reliable user tracking. Variables are typically provided by the application's authentication system and are more robust than other methods, which may be less consistent or require additional configuration. The other options are less preferred: * WalkMe ID(A) is a fallback generated by WalkMe but may not align with the application's user data. * Cookie(B) can be unreliable due to browser restrictions or clearing of cookies. * jQuery(D) is not a standard method for UUID setup; it's used for element selection, not user identification. Extract from Official WalkMe Documentation: Per the WalkMe Admin Center User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.10: User Identification): "For UUID setup, the Variable method is the most preferred, as it uses an application-provided user identifier (e.g., a JavaScript variable) for accurate tracking. Explore this option first before fallback methods like WalkMe ID or cookies." The courseAdvancing Your Skills in Building WalkMe Solutionsexplains: "Start with the Variable setting for UUID configuration, as it integrates with the application's user data, providing the most reliable and consistent user tracking for Insights analytics." Option C, Variable, is the most preferred UUID setting. References: SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.10: User Identification. WalkMe Admin Center User Guide, "UUID Configuration" Section. Course:Advancing Your Skills in Building WalkMe Solutions, Module 16: User Tracking and Analytics Setup.
Question 38
Which of the following is a capability of WalkMe's Smart Walk-Thrus?
Correct Answer: D
Question 39
You just published WalkMe content from your Editor for the first time. When you refresh your web page, you do not see any of the content. Which of the options could you check? Note: There are 3 correct answers to this question.
Correct Answer: A,C,E
Question 40
When building SmartTips with multi-language support, which practice should you avoid to ensure compatibility?
Correct Answer: C
When building SmartTips with multi-language support, it's critical to ensure compatibility across languages. The practice to avoid is using"Text Is" ruleswithin the Rule Engine, as these rules rely on specific text values that may change depending on the language. For example, a rule checking if a button's text is "Submit" in English will fail in Spanish where the text might be "Enviar," breaking the SmartTip's functionality. Instead, use language-independent identifiers, such as element IDs or classes, to ensure rules are not affected by language variations. The other options are acceptable or recommended: * Using language-independent element identifiers(A) is a best practice, as it ensures consistent targeting across languages. * Using the Customize tab for SmartTip text(B) is standard for defining multi-language content. * Adding inline CSS styles for language-specific elements(D) is permissible, though it should be used cautiously to avoid conflicts. Extract from Official WalkMe Documentation: According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.8: Multi-Language Support): "Avoid using 'Text Is' rules in the Rule Engine for multi-language SmartTips, as text-based rules are language-dependent and may fail when content is translated. Use language-independent identifiers like IDs or classes for reliable targeting." The courseAdvancing Your Skills in Building WalkMe Solutionsstates: "When configuring SmartTips for multi-language support, steer clear of 'Text Is' rules, which tie conditions to specific text strings that vary by language, causing compatibility issues." Option C, using "Text Is" rules, is the practice to avoid. References: SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.8: Multi-Language Support. WalkMe Editor User Guide, "Multi-Language SmartTips" Section. Course:Advancing Your Skills in Building WalkMe Solutions, Module 11: Multi-Language Best Practices.
