Multi-Language for HQ-sub Qooling environment

Modified on Fri, 11 Oct at 12:22 PM

If your organization uses Qooling's HQ-sub environment solution, there are a few details you should know regarding the multi-language feature. The translation principle for all module works exactly the same as for the normal Qooling environment. Refer to the multi-language instruction documents that we previously created to learn how to manage translations


HQ-sub translation dynamic explained


ScenariosEffect
1. Translations made/changed in HQ
  • Translations made in HQ are pushed to sub, given that the sync is turned on. 
  • Both environments will contain the same translation. 
  • If the sub does not have a specific local translation of the field, then the translation from the HQ will be taken over. 
  • If however the sub already has its own local translation, then HQ will not be taken over.
2. Translations made/change in subTranslations made or changed specifically on a sub level will remain only in the sub and will not sync back to HQ. For example:
  1. I translate a field in HQ called "Name HQ"
  2. "Name HQ" gets synched to sub initially
  3. But in sub, I change the translation to "Name SUB"
  4. The new translation in sub will be changed and the sync back to HQ will not happen
3. Remove translation in HQGiven that sub does not have its own local translation, the field from which translation was removed will become empty in both HQ and sub environments. If sub however, has its own local translation, then the removed translation will only impact HQ environment.
4. Remove translation in sub
If HQ environment has the a translation for the field from which the local translation was removed in sub, then the field in sub will take over the HQ translation. However, if the HQ also misses a translation for that field, then the field will become empty.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article