When building SmartTips with multi-language support, which practice should you avoid to ensure compatibility?

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.