Initial and Incremental Loading of Master Text List
 |
When the Manage Translations screen is launched for the first time in an org by any user, the master list of all the existing translatable strings associated with the above features is loaded into the ServiceMax Tag object. The list of keys associated with these translatable strings is updated in the related ServiceMax Processes object record(s).
|
Whenever any translatable strings are added/modified, this screen needs to be relaunched to load the new or modified strings into the ServiceMax Tag object, and to update the related ServiceMax Processes record. Examples of additions/modifications include creation of a new SFM Transaction, updating of an existing SFM Wizard, and adding objects to an existing SFM Search.
|
|
Any master text stored in a field of length up to 255 characters can have only one translation per language, as the master text is used as the key for the translation record (ServiceMax Tag record). For example, if 'Renew And Activate Contract’ is used as an SFM Process Name and SFM Wizard Step Name, there is only one translation record per language for these two contexts, with the key being ‘Renew_And_Activate_Contract.’ There can be only one translation for this label, which displays in both SFM and SFM Wizard delivery screens. Master text stored in a field of length above 255 characters can technically have more than one translation per language if it is used in two or more contexts. This is because the key used in these cases is the relevant process/page layout ID concatenated with ‘_DESC’ / ‘_PAGELAYOUT.’ For example, if 'Renew And Activate Contract renews an existing contract and activates it’ is used as the Page Help Text in an SFM Transaction and also as the SFM Wizard Step Description, there are two translation records per language, one for each occurrence. Therefore, the translation will have to be defined for each of these occurrences.
|