Combi
      Back to home
      1. Feature Knowledge Base
      2. MSR | Mysolution Recruitment
      3. Combi

      Translations for collective labour agreement (CLA) information

      It is now possible to include CLA information in documents with translations. MSR-947 | September 2024

      Who is this feature for?

      For customers using MSR in combination with MSF.

      Benefits for you as a user

      Multinational applications:

      • For organisations operating in multiple countries, CLA descriptions can easily be displayed in the local language of their employees. 

      Efficiency in document generation:

      • Integrating translations into MSR allows documents to be generated faster and with less effort, saving time and reducing the risk of errors in manual translations.

      Compliance with laws and regulations:

      • This feature ensures better compliance with local labour laws and regulations, as CLA information is correctly and accurately translated and applied.


      Explanation of this new feature

      We will describe the feature from two perspectives.

      Translation on Placement

      When generating a document with CLA information on the placement, the related candidate’s language is checked. If there is a match with the language on the document type template, the CLA information is generated in the respective language. Note that in MSF, this translation must be present under the respective CLA. If no translation is recognised, MSR defaults to the document type template without a specified language.

      Translation on Account

      When generating a document with CLA information on the account, the document type template is checked for an account filter. If there is a match, the translation is written into the document.

      Feature Implementation Time (FIT)

      • Simple implementation:  < 1 hour

      Setup

      To add CLA information to a document, use the XML node named ‘CaoDescription’.

      Related to the relevant document type to which this node is added, you must create a document type template based on the desired language. Link the unique document for generation to this. Always create a document type template without a language, which serves as the ‘neutral’ version to fall back on if no language is detected.

      Finally, you must perform some additional configuration in Custom Metadata Types, General Language Settings. When creating a label here, ensure that the 'Language API Name' matches the language code as known in MSF. This will allow the correct translation to be retrieved for the CLA information.


      🔗 Here you can find the key features from the September 2024 Release