Translations and Multi-Language Events
  • 01 Feb 2024
  • 7 Minutes to read
  • Dark
    Light

Translations and Multi-Language Events

  • Dark
    Light

Article Summary

Blackthorn has multiple translation options for Events that will fit various use cases.

Static Translations Feature now in Beta!

Please reach out to our support team if you'd like to participate in as an early adopter!

Multi-language Events

Functionality Updates

The following changes only apply to Translations using Google’s API:

  • If a Source Language is set on the Event Settings, the Event URL will automatically be displayed in that language. Language can be changed by the Language Selector (if enabled).
  • If a Source Language is NOT set on the Event Settings, then the Event URL will automatically be displayed in the language related to the user’s browser locale setting. Language can be changed by the Language Selector (if enabled).
  • If a Source Language is set on the Event Settings related to an Event Group, then the Event Group URL will automatically be displayed in that language. Language can be changed by the Language Selector (if enabled).
  • If a Source Language is NOT set on the Event Settings related to an Event Group, then the Event Group URL will automatically be displayed in the language related to the user’s browser locale setting. Language can be changed by the Language Selector (if enabled).

Blackthorn harnesses the power of Google Translate as the basis of our Events translation capabilities.

By default, with no specific Salesforce configuration, Event pages load in English. A user may change the language by using the Language Selector on the Event.
D_02_07_Translations 1

From your Event Settings record, you can also:

  • Set the Language Selector to "Off" to hide it from your Event pages.
  • Choose a default Source Language for your Event. This will ensure the Event loads in the selected language and can be used with or without the Language Selector being set.
    • If the Source Language = "Spanish", then the user must enter text in Spanish instead of in English.
    • If the Event information is entered in English and the user wants it to be translated by the language selector, then Source Language = None.
  • Filter the list of available languages a user can choose from by selecting specific languages in the Supported Languages picklist.
    D_02_07_Translations 2

Translation Overrides

While using the Google Translate API is beneficial and provides a quick path for Event Planners to translate Events’ pages, we also recognize that these translations may not always be picture perfect or accurate.

We now have two great options to choose from to ensure you are able to provide accurately translated pages to your users and Attendees.

Data Dictionary

Our Data Dictionary feature can be utilized to override inaccurately translated button labels and static text on your Event pages. We also support multi-language Events with this feature. When setting up Data Data Dictionary Entries, you can specify different overrides with different languages of the same button label or static text. For information on configuring the Data Dictionary, please refer to this page.

Static Translations (Beta)

As of March 2022, our Static Translations feature is now in Beta! Similar to the functionality of the Data Dictionary override capability, we now have a solution which allows an Event Planner to override or simply write their own Translations in place of Google Translate's auto-translation. The feature supports multi-language events as well!

Requirements

  • Use our Candy Shop to install or upgrade to Blackthorn Events 3.56 or above.
  • Beta opt-in (please reach out to Blackthorn Support to submit a request).
  • Review Base Package documentation to learn about our new Translations object in Salesforce.
  • The Language field is a required field on the Translation record.

Configuration Steps

  1. Navigate to the Blackthorn | Events Admin page and click the Upgrade tab.
  2. Click Upgrade Translation Layouts, which will deploy all the supported fields to the Translation page layout.

Important to Know

  • When an Event Admin creates a Translation record from a record related to an Event, both the Event lookup and the parent record lookup record are set automatically.

  • After creating a Translation record from a record related to an Event, the user will be blocked from setting more than one lookup on that Translation record.

  • Forms, Form Elements, Form Element Condition, Form Big List Option, and Keywords cannot have the Event lookup since each of the items listed can be used by multiple Events.

  • A translation relationship should be created between the Event and Event Item every time a Form with translated Form Elements is re-used, whether it's applied on the Event or Event Item level.

    If a Form is used on the Event level, the translations from the Form’s Form Elements will display on all Event Items only if a Translation record is created on the Event record where the Event and one of the Event Items are populated as lookups. No other information/translation should be filed on that Translation record.

    If a Form is used on the Event Item level, the translations from the Form’s Form Elements will display on one Event Item only if a Translation record is created on the Event record, as mentioned above. This means that if there are multiple Event Items using the same Form, a new Translation record needs to be created for each Form so the Event Item can be related to an Event. No other information than the Event/Event Item lookups should be populated on the Translation record. A work around is to set the Form on the Event level (described above); however, that would mean that that the Form would apply to all Event Items.

Creating Translation Records

Duplicate Translation Records

If an Event Admin tries to create a duplicate Translation record from a related record with the same Language, they will be unable to save the record and will receive the following error message. “Only one Translation record can be created per parent record and language, such as one Translation per Session’s or Event Item’s language.”

  1. Navigate to an Event record and find the Translations Related List.

  2. Click the down arrow and then click New.
    D_02_07_Translations 3

  3. Select a value (language) for Language.

    NOTE: The value (language) selected here directly correlates with our Language Selector values on the Event page.

  4. Type or copy/paste your translated values directly into the equivalent fields on the Translation record.

    NOTE: You can only translate fields from a single record per Translation record. For example, if you have an Event with one Event Item and one Session. You will need to create three Translation records for the same language: one for the Event fields, one for the Event Item fields, and one for the Session fields.

D_02_07_Translations 4

  1. Save your Translation.
  2. Click Update or Publish on your Event.
  3. Launch your Event and change the Language Selector to match that of your Translation records.

Success! You'll see that your static Translations are visible in place of the Google Translate translation.

When an Attendee selects a language on the Event page, all records related to that language will be queried.

D_02_07_Translations 5

Objects and Fields Available for Translation

Formatting Updates

The following formatting has been updated to help with the translation of abbreviated months on the Event Page URL and Event Group URL pages.

  • Abbreviated months (except for Event Group listings)
    • Old: JAN
    • New: 1
  • Event Group listings
    • Old: Jan 2, 2022
    • New: January 2, 2022

The following objects and fields are currently supported for translation.

Event

  • AttendeeLink Message
  • Checkout Details
  • Description
  • Precheckout Details
  • Success Message
  • Short Description
  • Social Message
  • Waitlist Message
  • WiFi Message

Event Item

  • Description
  • Public Item Name
  • Short Description

Session

  • Description
  • Display Name
  • Location
  • Topic
  • Type

Speaker

  • Bio
  • Title
  • Account Name

Sponsor

  • Description
  • Display Name
  • Tier

Event FAQ

  • Answer
  • Category
  • Question

FAQ Category

  • Name

FAQ Question

  • Answer
  • Question

Custom Event Tab

  • Content

Event Content

  • Content Name

Form

  • Submitted Message

Limitation
Translations do not work for post-Event surveys/Forms. This update will occur in a future release.

Form Element

  • Hint
  • Question Text Only
  • Question Rich Text
  • Picklist Values

Form Element Condition

  • Selected Value

Form Big List Option

  • Value

Translation Object Layout

The page layout for the Translation object now includes the following sections and related fields.

Section TitleField Label
EventCategory
AttendeeLink Message
Checkout Details
Description
Precheckout Details
Success Message
Short Description
Social Message
Waitlist Message
WiFi Message
Event ItemDescription
Public Item Name
Short Description
SessionDescription
Display Name
Location
Topic
Type
FormSubmitted Message
Form ElementHint
Question
Picklist Values
Form Element ConditionCondition Value
Form Big List OptionOption Value
SpeakerBio
Title
Account Name
SponsorDescription
Display Name
Tier
TrackTrack Name
Custom Event TabContent
Event FAQAnswer
Category
Question
FAQ CategoryFAQ Category Name
FAQ QuestionAnswer
Question