Following Best Practices for Multi-Language

Objective

After completing this lesson, you will be able to follow best practices for building WalkMe solutions.

Smart Walk-Thru Best Practices

The decision to support Multi-Language should be made before you begin building WalkMe solutions.

Reach out to your WalkMe Customer Success Manager before building to enable a feature to ensure that elements captured in one language will play correctly in another.

Note

Please note, this change will not make the content you have already created Multi-Language friendly. The ignore text box, discussed below, may need to be manually checked for your existing solutions. Determine whether to support Multi-Language upfront to avoid rework.

Smart Walk-Thru Best Practices

Avoid Using Text to Identify Elements

When building out your content, because the text may change depending on the language selected, avoid using:

  • Text Is... rules within the Rule Engine.

    Image shows Locations of the Text Is rules in the Rule Engine
  • :contains("text") jQuery selectors. Image shows The location of the jQuery selector in the Step Options
    The figure shows the location of the jQuery selector in the Step Options ﹥ Selected Element ﹥ Define how to identify the element section.

  • [title] jQuery attributes unless you are certain these will not be translated when your site loads in another language.

  • By text when identifying an element. Image shows how to identify the element by text.

    The figure shows the location of the By text option in the Step Options ﹥ Selected Element ﹥ Define how to identify the element section.

Ignore Text Attributes

For non-DeepUI multi-language implementations only, reach out to your WalkMe Contact to enable a feature that will make all steps ignore text by default (setting shown in the following image). This change will not affect content already created. The ignore text box will need to be manually checked for your existing solutions.

This feature should not be used and is not necessary for customers using DeepUI.

Inside the Step Options, the section Define which attribute to ignore will allow you to check a box to ignore Text for the Selected Element.

The figure shows that the Define which attribute to ignore section will allow you to check a box to ignore text for the Selected Element.

Text Length and Format

Some phrases may be longer in other languages.

Check the balloon size and position in different languages. The positioning may need to be adjusted because the length of the text will vary from language to language.

The balloon's Spanish translation (bottom) is longer than the English translation (top), causing the balloon to become cut off on the right side of the screen.

The figure shows that the balloon's Spanish translation (bottom) is longer than the English translation (top), causing the balloon to become cut off on the right side of the screen.

Similarly, be aware of different writing systems.

If some of your translations include a Right to Left or Left to Right language change, be sure to test these translations thoroughly as the balloon position may need to be adjusted.

Launcher Best Practices

Do not use images with text.

Since text within images cannot be translated, do not use Launcher images that contain text, or Launchers from the Gallery with text.

If a Launcher is meant to work in more than one language, it is recommended to use a Launcher without text or a Launcher with translatable text created in the Customize tab.

Examples of Launchers with text and without text in the Launcher Gallery. Accessed by selecting Change Launcher from the Launcher's Interaction tab. Click image to enlarge, then click the close icon to close.

The figure shows the examples of Launchers with text and without text in the Launcher Gallery. You can access the Launcher Gallery by selecting Change Launcher from the Launcher's Interaction tab.

Use the Customize tab to create Launchers with translatable text.

These can be translated in the WalkMe Console in the Multi-Language Translations tab. Click into WalkMe General, then navigate to the Launchers & SmartTip Icons folder, shown in the following figure. If translated text is longer in another language, you may need to adjust the position of the Launcher so it does not block your site's content.

Let's see how to navigate to Launcher translations in the Admin Center. Note that alt tags for Accessibility can be added for Launchers here as well.

Watch the video to know more. Note that the video doesn't support audio.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn