Objective
After reading this article, you will understand how to implement and utilize Form Translations in Youreka Web and Youreka on Pulsar.
Before you get started
These articles might be helpful before you read further:
Introducing Form Translations!
The Youreka Form Translations feature, introduced in the Voltage release, is designed to enhance the accessibility and usability of forms across a global user base. Available in Youreka for Windows Pulsar and Youreka Web, this feature provides seamless translations of Section Labels, Question Labels, Question Value Labels, and Free Text within a form, ensuring users can interact with forms in their preferred language with ease. This feature is NOT available in Youreka Mobile.
Note: Youreka Web refers to the Forms Experience in Salesforce plus viewing the Form on the Form’s Detail page.
Form Translations empower organizations to support multilingual teams efficiently by offering two key translation methods:
-
User Preferred Language: Forms automatically display in a user's pre-defined preferred language when available.
- Language Change Experience: Users can manually select a different language while viewing a form, allowing for greater flexibility.
With these capabilities, Youreka continues to provide an intuitive and adaptable experience for users across various industries and locations.
Benefits
Implementing the Form Translations feature provides several key benefits to organizations and their field teams:
- Enhanced Accessibility: Ensures users can interact with forms in their preferred language, reducing language barriers and improving overall comprehension.
- Improved User Experience: Users can seamlessly switch languages without needing additional tools or manual translations.
- Standardized Data Collection: Translated forms promote consistency and accuracy in data capture across different language groups. Also consider reporting.. It just got easier! One report across forms in different languages!
- Greater Flexibility: Users can adapt to changing needs in real-time by selecting the appropriate language for each form they interact with.
- Compliance and Inclusivity: Supports organizational goals of inclusivity and compliance by accommodating diverse workforces and regulatory language requirements.
Use Cases
Use Case 1: Multinational Field Teams
A global organization with field technicians across multiple regions can leverage Form Translations to ensure that forms are displayed in each technician's preferred language, improving comprehension and reducing data entry errors.
Use Case 2: Regulatory Compliance
Companies operating in regulated industries can use the feature to meet compliance requirements by ensuring that critical inspection or audit forms are available in legally required languages.
Use Case 3: Seasonal Workforce Support
Organizations that employ seasonal workers from diverse linguistic backgrounds can use the language change experience to accommodate temporary staff and maintain operational efficiency.
Use Case 4: Cross-Departmental Collaboration
Teams that span across various departments with different language preferences can collaborate effectively by switching form languages based on their needs, ensuring a smooth workflow.
Use Case 5: Customer-Facing Forms
Businesses collecting data from customers in different regions can present forms in their customers' preferred language, enhancing engagement and data accuracy.
How to Setup
Before we dig into the fun stuff, we have to ensure that a few things are set in place to ensure a successful experience.
Set Up Translations
First, we have to ensure that a Global Language Picklist Field has been defined.
- Define the Global Language picklist field
- This field determines what languages are available for Translation Selection
- Head to Setup
- In the search bar, search for “Picklist value sets”
- Select that option
- Select “Languages”
- Navigate to the “Values” Section on the page
- Add languages
- Once you’ve added languages, you are good to go! This is a global picklist, so the languages will be available for selection once Translations are created.
Now that’s complete, we can start creating Translations for our Form Template!
- Navigate to an already created Form Template Record.
- Select “View Form Template Properties” in the Settings Menu
- Click on the Related List
- If they exist, you should now be able to see your Section Records, Question Records, Question Value records, and Content Records (Free Text).
- For this example, we will translate a Question Label for French.
- Select a Question Record
- Click on the Related List
- See the Translations Section and Click “New”
- This is where the Translation for your Question Label will be added.
- Make sure to fill out the following fields
- Language
- Translated Label
- Note: When inputting a translation for Free Text, you need to stylize your Translation with the proper HTML markup.
- Example: Hello World
- <p> Hello <b> World </b> </p>
- Example: Hello World
- Click Save
- You now have a Translation Record for that specific Question Label. If that form template were to get translated to French, that Question Label would match the Translated Label that was defined!
Now that Translations Exist for a Form Template, we can define a User’s Preferred Language. NOTE: This part of the setup experience is optional but preferred! This ensures that anytime a specific user opens up a form, they’re viewing it in their preferred language (if translations for that language exist for that form template)!
- Navigate to Salesforce Setup
- In the quick find bar, search and select Users
- Find a user and select Edit
- Find the Additional Information Section
- View the Preferred Language Field
- Select the User’s Preferred Language
- Click Save
And just like that, you are ready to tap into the Translations experience!
How to Use
After creating a Global Language Picklist and creating Translations for a Form Template, you can follow these steps to see Translations in action.
Completing a Form in Web
- Create a Form using the Form Template that contains Translation records
- Once you are in the form, you will see that the following elements, if they exist, have been translated into your preferred language. Note: If the User’s Preferred Language is not defined, the form will not be automatically translated.
- Section Label(s)
- Question Label(s)
- Question Value Label (s) (Picklist Values)
- Free Text
- You will also see that there is a new Language Change Picklist
- Selecting that picklist will show the list of languages that exist for that Form Template
- There will be a default option. Selecting that will change the language of the form to its original created language.
- Selecting a language in the picklist will then translate necessary elements in the form to that language.
Form Detail Page
- Once a form has been submitted, navigate to the form record in Salesforce
- The necessary elements of the form will be translated to the User’s Preferred Language, if defined.
- The Language Change Picklist exists here as well.
- Selecting a language in the picklist will then translate necessary elements in the form to that language.
Youreka for Windows Pulsar
- Create a Form using the Form Template that contains Translation records
- Open that form in Pulsar
- The necessary elements of the form will be translated to the User’s Preferred Language, if defined.
- The Language Change Picklist exists here as well.
- Selecting a language in the picklist will then translate necessary elements in the form to that language.
Considerations
- Translations are not supported for Table Sections
- Translations do not work if a form contains a Sketch Pad question
- Cloning a Template with Translations will not clone those Translations over
- Importing/Exporting a template with Translations will not pull the Translations over
By leveraging Youreka Form Translations, organizations can streamline their operations, foster inclusivity, and enhance productivity across global teams. Get started now!
Comments
0 comments
Article is closed for comments.