Skip to main content

Multi-Language Configuration

anaddell
Updated

You can configure the multi-language feature to view job descriptions in multiple languages.

To enable multiple languages

1. Navigate to the Admin Tools tab.

2. Click the Other Administration Tasks node, and select Edit Business Rules.

This displays the following screen:

3. Select the JDX Business Rules (JobDescBusRules.JDXBR) node as shown:

4. Set the EnableMultiLanguage property to True.

5. Click More next to the ActiveLanguages property.

This displays the Select Languages(s) dialog box:

6. Select the required languages which you require for conversion.

7. Click OK.

The selected languages are populated as shown:

8. Click Save.

To set a conversion profile for each language

1. Navigate to Admin Tools.

2. Select the Data Management node, and click Multi-Language Administration.

This displays the following screen:

image-20240718-081107.png

3. Click Edit Conversion Profiles.

image-20240718-081150.png

This displays the following screen:

image-20240718-081357.png

The active languages are displayed in the left pane.

4. Click Select and add a job.

image-20240718-081532.png

This displays the following screen:

image-20240718-081808.png

5. Click Add New Profile.

This displays the following screen:

image-20240718-081939.png

6. Click More.

image-20240718-082011.png

This displays the following screen:

image-20240718-082125.png

It automatically creates a print profile with the language name.

7. Select a conversion profile and click Select and Conversion Profile.

image-20240718-082244.png

8. Click Save and Close.

image-20240718-082345.png

This displays the following screen:

image-20240718-082507.png

9. Select a template in the Word Template list:

image-20240718-120927.png

  • Click Create Template and choose the blocks you want to include in the document. Repeat this process for each language profile.
  • Select the same tabs as used in the Default job description. All boxes are selected by default.
  • Select the Translate Captions check box.

10. Select the All Properties tab and set the required language (for example, French).

image-20240718-094304.png

  • You must create at least one profile for each language.
  • Each profile can be assigned to only one language. For example, a French profile will not be available for English.

11. Click Save and Close Form.

12. Preview the job in multiple languages from Job Management as shown:

image-20240718-095959.png

If the changes are not displayed, clear your system cache, log out, and log back in.

 

Q&A

  1. Is the translation on the fly at JD level or do you translate the building blocks?
  • Translation occurs at the building-block level using phrase tables, and the JD renders the translation on the fly.
  1. Are they stored once translated
  • The translations themselves are generated in real time. However, any corrected phrases are saved in the phrase table list and applied when rendering.
  1. Is there a link between the original English JD and the translated JD, what happens if the original is changed?
  • Yes—there’s a single source JD. When the English JD changes, selecting Translate re-renders the latest version; saved phrase-table entries are applied where available.
  1. Do the translated JDs display in the same job matrix, would we be doubling up? Can we filter on language. If no link how to you keep them in sync.
  • Translations work on the fly through translation tables. Once translated the translation does not stay. Cannot filter on language.
  1. Assume individuals involved in translations, verifying would need write access?
  • Organizations usually setup their translators with access to the phrase table area where the translations happen through the JDAdmin role.
  1. Do you have to put the translation through a workflow to finalize it
  • No workflow is required
  1. Does the translated JD receive a new unique job code?
  2. No
  3. Please demo the process of translating a JD 
    1. Which roles can use this functionality (do we need to create new access roles for those translating JDs?)
  • Only Admins and JDAdmins can edit the phrase table. Any role can view translations if you grant permission to that print view.
  1. Can translations be done en masse or only one-by-one?
  • One by one. Translations are real-time renders and are not saved as attachments.
  1. Where are the translated JDs stored?
  • They aren’t stored as separate artifacts; translations render in real time and can be exported.
  1. Who (which roles) can review and update (correct) the translated job description? Are these corrections saved? Can these translations be updated? Are the changes version controlled (is history maintained for translated JDs)?
  • Admins and JDAdmins can review and update via the phrase table list. Corrections are saved there and can be updated at any time. Version control isn’t available on the phrase table list; it always reflects the current entries, rendered in real time.
  1. Are the translated JDs viewable in the Job Library? If not, where would employees/others with JDX access locate these JDs?
  • Yes. They appear in the Job Library in the same location as today, with the additional Translate option
  1. If the translation is limited to the printed version of the JD, what about the fields that do no appear on the printed version? Would we have to add them to the printed version in order to have the fields translated?
  • Translations are limited to the default print view. Fields not in that view would need to be added to be translated.
  1. Are the headings (field names) also translated or just the content?
  • Both headings/field names and the content can be translated.
  1. Can all fields be translated including the job title, job family name etc?
  • Yes—titles, job family names, and other fields can be translated. Note: rich HTML fields may not translate perfectly if used.
  1. Could these translated JDs be included in an export file so we could make the translated JD available in downstream systems?
  • Yes—export on a job-by-job basis. Only print views can be exported with translations.

Related articles

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk