Search Engine: Elastic

Article ID: 131621, created on Oct 16, 2017, last review on Nov 19, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 7.2

Symptoms

After new localization package (.po file) is uploaded on the Addons tab, new localization strings are not applied.

Cause

Software-related issue #APS-39337: "Custom locale for APS package is not applied automatically".

Resolution

For UI service running on the management node:

  1. Customization of a view or tab label (these are present in po files as well as mentioned in APP-META.xml) requires simple pau restart to apply changes.

  2. Customization of any other string that is not a view or tab label (like a notification or some message on the APS Application screen) does not require any actions and will be applied right away.

  3. Customization of any string to "" (NULL) or " " (space) will lead to the following situation: next changes of the same string will not be applied until the version of locale APS package with "" or " " will be removed from OA > Services > Applications > app_name > Add-ons > app_name - localization xx_XX > Versions.

for UI service running on a branding node:

  1. Customization of a view or tab label (these present in po files as well as mentioned in APP-META.xml) requires simple pau restart;

  2. Customization of any other string that is not a view or tab lable (like a notification or some message on the APS Application screen) requires removal of Apache cache:

    # rm -rf /var/cache/brands/*
    

    no need to restart httpd.

Please refer to KB4642 for the instructions on how to restart OA services correctly.

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 8c199f0ee4305da1a577740620df4a51 31987597efff5a3a9ce779cc203bbe5e

Email subscription for changes to this article
Save as PDF