|
Create Translations for Activities and Other Configurations |
Scroll Previous Topic Top Next Topic More |
In order for all elements shown in the multilingual app to be multilingual, it is necessary to translate some information from the data model.
This includes the fields ActivityType, EdgeType, nextActivityType, previousActivityType (also for the Resource Log) as well as the Subprocesses, the Happy Path Descriptions, or the Optimization Potentials.
To do this easily, we provide a template for these translations on tab "7. Data Model Translations". Just follow the steps mentioned:
|
If you don't want to translate the data model fields, just do nothing on this tab and load the data as usual. The original field value will then automatically be added as a dummy translation and your front end will be fully functional. |
1. Translate the ActivityType to translate the fields ActivityType, EdgeType, nextActivityType, previousActivityType. Simply fill in the inline table "ActivityTranslations" or use a table with the same name from another data source like QVD or CSV. The first field ActivityType contains the values of the field ActivityType loaded in the EventLog and the following columns get the respective translation.
ActivityTranslation:
NoConcatenate
load * inline
[ |
ActivityType, ActivityType_EN, ActivityType_CN, ActivityType_DE, ActivityType_ES |
]; |
|
|
Do not forget to also translate the Start and End activity. |
After that this ActivityTranslation table is used in several methods for translation. The method mw_add_edge_translations translates the edges, while the other calls of mw_add_field_translations translate the field specified in the third parameter. The last call drops the translation table (last parameter = 1).
call mw_add_edge_translations('ActivityType','ActivityTranslation','ActivityType','pa_activity_log_$(mvProcessDescription)');
call mw_add_field_translations('ActivityType','ActivityTranslation','ActivityType','pa_activity_log_$(mvProcessDescription)',0);
call mw_add_field_translations('ActivityType','ActivityTranslation','nextActivityType','pa_activity_log_$(mvProcessDescription)',0);
call mw_add_field_translations('ActivityType','ActivityTranslation','previousActivityType','pa_activity_log_$(mvProcessDescription)',1);
2.Optional: After that, if necessary, translate the ActivityTypes from the resource log. This is done by filling in the inline table ResourceTranslation.
ResourceTranslation:
NoConcatenate
load * inline
[ |
$(mvProcessDescriptionResource)_ActivityType, $(mvProcessDescriptionResource)_ActivityType_EN, $(mvProcessDescriptionResource)_ActivityType_CN |
]; |
|
Again, the EdgeTypes and the next- and previousActivityTypes are translated with the subsequent method calls. The last method call drops the translation table (last parameter = 1).
3.Optional: After that, translate the subprocesses, if necessary, so that their texts are displayed in the front end in the correct language. This is done by filling in the following table:
SubprocessTranslation:
NoConcatenate
load * inline
[ |
Subprocess, Subprocess_EN, Subprocess_DE, Subprocess_ES, Subprocess_CN |
]; |
|
Again, with the subsequent method calls, the translation of the field values is performed and the translation table is dropped.
|
It is important to define (if necessary) the subprocess translations before calling the translation for the optimization potentials, as the translation of subprocesses is used in the translation of the root cause optimization potentials. |
4. Optional: After that, translate the subprocesses, if necessary, so that their texts are displayed in the front end in the correct language. This is done by filling in the following table:
OptPotentialTranslation:
load * inline [
OptPotential, |
OptPotential_EN, |
OptPotential_CN, |
OptPotential_DE |
Target lead time missed, |
Target lead time missed, |
错过了目标准备时间, |
Ziel lead time verpasst |
Low process governance, |
Low process governance, |
流程治理水平低, |
Niedrige process governance |
Reworked Case, |
Reworked Case, |
流程治理水平低, |
Nacharbeits-Case |
]; |
|
|
|
|
If further customer-specific optimization potentials have been added in the RCA than specified in the template, these are to be added to the OptPotentialTranslation. This also applies to translations of the CriticalQueries option. Subprocess OptPotentials are automatically added if a translation was found. |
Again, with the subsequent method calls, the translation of the field values is performed and the translation table is dropped.
5.Optional: After that, if necessary, translate the Happy Path Descriptions so that their texts are displayed in the front end in the correct language. This is done by filling in the following table:
HappyPathDescriptionTranslation:
NoConcatenate
load * inline
[ |
HappyPathDescription, HappyPathDescription_EN, HappyPathDescription_DE, HappyPathDescription_ES, HappyPathDescription_CN |
]; |
|
Again, with the subsequent method calls, the translation of the field values is performed and the translation table is dropped.
6.Optional: After that, if necessary, translate the Group Descriptions so that their texts are displayed in the front end in the correct language. This is done by filling in the following table:
ActivityGroupLabelTranslation:
NoConcatenate
load * inline
[ |
ActivityGroupLabel, ActivityGroupLabel_EN, ActivityGroupLabel_DE, ActivityGroupLabel_ES, ActivityGroupLabel_CN |
]; |
|
Again, with the subsequent method calls, the translation of the field values is performed and the translation table is dropped.
If further fields are to be customer-specifically translated, such as the case dimensions, this can be done according to the same pattern. A translation table is loaded and passed into the method mw_add_field_translations.
call mw_add_field_translations('<KeyFieldForTranslationInTranslationTable>','<TableHoldingTranslation>','<FieldToBeTranslatedInTargetTable>','<TargetTable>',<DropTranslatinOrNot 1 or 0>);
The methods are called with the following 5 parameters:
1.'<KeyFieldForTranslationInTranslationTable>': String - The field in the translation table that is to become the key field to the target table
2.'<TableHoldingTranslation>': String - The translation table
3.'<FieldToBeTranslatedInTargetTable>': String - The field in the target table that is to become the key field to the translation table
4.'<TargetTable>': String - The target table
5.<DropTranslatinOrNot 1 or 0>: Boolean - Dropt ranslation table (1) or not (0)
