Web GUI custom conversions
EngBernie 120000H79Y Comment (1) Visits (2720)
For example, to correctly set custom conversions for Severity in Spanish, you will need to edit $TIP
priority.0=My custom val1
Do this for as many language as you need by editing the corresponding language file. You'll need to restart the TIP server for this to take effect.
But what if you do not care about translations? Maybe you are only concerned with one language, and wish to maintain the conversion only in the ObjectServer? Continuing our previous example, you'll need to disable translation of conversions in Web GUI. You do this by commenting out the key-value pairs in the Spanish (con
Once you've finished editing the files, restart TIP and you should see ObjectServer conversions take effect. You'll want to back-up your custom conversion files as these do get overwritten during upgrades (and possibly fix pack installs). Once you've upgraded Web GUI, re-apply the custom translations by copying entries from the old translation files to the new ones. Do not overwrite the new translation files with the old ones as they may contain new translations.
Also note that setting custom conversions via translation files in Web GUI will only work for default (non-customised) areas. Translations for any new customer-created conversions will not have translations in Web GUI, so the only way to customise these will be through Obje
Webtop 2.2 & Web GUI 7.3.0 : $TIPWeb GUI 7.3.1: $TIP