Localization within Hyperfish

Mick Sowl -

*Applies to Online and Hybrid Tenants

*Will need Hyperfish Premium if using Collections feature

 Language Localization

 At this time Hyperfish does not provide out of the box language packs; however, it is possible to provide end users with an experience that is almost completely in their native language. This article will cover the steps necessary for an Administrator to perform in order provide end users with an experience in their native speaking language.

 Considerations-

Before starting this process, there are a few variables to consider.

  • Do all users within the directory scope speak the same language?
  • Is it necessary to retrieve different attribute information from users in a different language?
  • If the answer is "yes" to either of the above, how are these users categorized within your Active Directory instance? Are they in the same OU? If not in the same OU, is there a unique attribute that can be used to filter said users off of?
  • If for an online tenant, is there an attribute that can differentiate the different language speakers?

For Hybrid environments, there are two main ways one can set up localization. First, if the whole directory scope speaks the same language, editing the master settings will suffice. If only a specific subset of users speak a different language, there are multiple language experiences that need to be created or different attributes will need to be collected for different groups of users, the Hyperfish Collection feature will be necessary.  With collections, different settings can be applied to specific audiences of users. For Hybrid environments, collections are defined by either Organizational Unit (default) or by attribute value. For Online environments, it is only possible to setup collections based off an attribute value.

 Implementing Localization-

Once the target audience has been set, the next steps are to edit the settings from the Admin Dashboard. If a target audience is a subset group of users, first create a collection based on those users' OU or specific attribute value. The steps provided in this article are editing the master settings. For collections, the process is the same. Just ensure the collection is selected when making the edits and 'Override the Master Settings' option is enabled for each of the sections discussed. The first area to update will be the Attributes section. Navigate to Settings, then Attributes, the Display Name and Hint Text for each attribute will need to be modified/translated into the native language one wishes to have illustrated on the user's profile page. 

 

 Select the pencil icon next to each attribute that will be displayed on the user profile page.

The Display Name and Hint Text will be the two fields end users will come across on the profile page.  Translate the current properties in these two fields into the desired language users will understand.

Once all of the attributes displayed on the profile page are updated, the next step is to modify the email templates coming from the Hyperbot.

Navigate to Settings, Hyperbot. Scroll down to the Personality section. Expand the email templates and modify all of the options listed. This includes the First Attempt, Reminder and Update Rejected. Additionally, if Profile Validation is enabled, updating the email template for this feature is also located here (as seen below).

 

Select the pencil icon next to each of these templates. The image below will appear. Translate each field into the desired language. It is critical to ensure each of these properties has been translated. This will ensure optimal experience for end users.

 Once the First Attempt, Reminder, Update Rejected and Profile Validation email templates have been updated, as well as the display name and hint text for the attributes, the end user will now be able to interact with Hyperfish in their native language.  There are still a few items that will be seen in English. Including 'Sign out' option, 'Cancel or Save' and 'Contact your Administrator' option on the profile page. Additionally, the Skype communication channel for the Hyperbot is not available in languages other than English. 

 Localizing Hyperfish Web Parts-

Currently, the Hyperfish Profile, Live Directory and Organizational Chart web parts can be displayed in English, Dutch, German and French. More languages will be available in the future.  In order to utilize the languages other than English, the most up to date Web Part package will need to be installed. This can be found here.

Hyperfish Web Parts utilize SharePoint's localization Framework. In order for the web part to display in the user's native language, the SharePoint site preferred language will need to be set in the desired language, or the end user can update their language settings for the page the web part is located on to be their native language.

The filters/attributes displayed on the user's profile card are being pulled directly from the settings within Hyperfish. As long as the items listed in this article were translated, they will be displayed in the user's native language.

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.