IFS Cloud - install new languages via delivery

​@Ben Monroe ​@Banu Liyanapathirana ​@Serhii Kovtunovych any input on this one please?

Should I also download the translation files and commit them to the customer repo? 

​@Marcel.Ausan 

Hello,

Yes, you are right, translations should be added to the delivery automatically. This dialog just modifies the translationusage.json file and activates the required languages. When building the distribution, DevOps checks this file and adds the required translations to the delivery from IFS Core translation repository (https://docs.ifs.com/techdocs/25r1/070_remote_deploy/400_installation_options/050_translation_downloader/?h=translations).

>> Should I also download the translation files and commit them to the customer repo? 

No, you do not need to commit translations to GIT - the Core translations are not stored in GIT.

Please check the delivery archive - it should contain *.trs files for the specified languages.

If delivery includes translations files - please check the background jobs with the name “Bulk Import of Language Files” (Language_Sys.Bulk_Import_Def_Call_) - this job imports translations from intermediate storage into IFS translations storage (Oracle tables) and refreshes language cache to activate them for end users. This job is automatically created during delivery installation.

Execution may take a long time, or there may be system issues with running the background job.

If everything is OK - you can try to refresh language caches manually using Used Languages page.

Best Regards,

Serhii

​@Serhii Kovtunovych the “Bulk Import of Language Files” has finished successfully. It only took 3 mins.

When I look in the job details, I can see only references to English. nothing about the other languages that I enabled from the buildplace.

I ran the refresh language cache but it didn’t help.

Any other ideas?

​@Marcel.Ausan 

This is very short. If this call was initiated by the delivery, it means it doesn't contain translations or, for some reason, didn't import them.

Please check the translationusage.json file inside the delivery - does it have other languages enabled?

InstallationFiles\server\translation\translationusage.json

  {
    "code": "it",
    "used": "true"
  },

If yes - Does delivery contain *.trs files for other languages?

InstallationFiles\server\translation\*WEB-Core-it.trs

If yes - Does the Text Translations page contain translations into other languages? 

Filter by language and Main Type:

Best Regards,

Serhii

​@Serhii Kovtunovych 

I downloaded the zip folder of the delivery and I could see insode translationusage.json - the languages are set to true:

Also translation files are inside the delivery:

But there are no Text Translations:

Any other ideas? Do you think this could be an IFS Bug?

​@Marcel.Ausan 

Yes, it could be a bug.

It could also be related to some of the options during the installation of the delivery — the option to import translations (Apps 10 has such option for translations files) , which languages ​​should be imported, etc. If so, the delivery will need to be reinstalled. Unfortunately, I don't know how this process works in Cloud— another team performs it for Cloud, and our technician is currently on vacation((. Please check if these options are available and what values are set.

As a manual solution, if it is applicable for project rules, you can try to use the Import Language Files page and select files from the delivery translation folder with the option to run import as a background job for logging. If you already have new additionally  installed deliveries after this one, you need to create a new temporary translation folder and copy all delivery translation folders into it in the order of deliveries installation to import the latest translation version.

Best Regards,

Serhii