Tags
Baan delivers PMC solutions for Baan IV c4 only in the languages Dutch, English, German and French. When you use a so-called B-Language (a language for which components are not delivered in the individual PMC solutions), installing a PMC solution wasn’t always beneficial. E.g. when a form and an object were changed to solve a problem, after installation of the solution you used the new object (because an object is language-independent), but you still used the ‘old’ form, because it was not updated in your B-Language.
By installing the Translation Service Packs, the B-Language components were up to date again. However, installing Translation Service Packs could cause other problems, because components of installed newer solutions could be overwritten with older ones.
PMC has been extended to cover this problem area: B-Language Support.
The next chapters will describe this extension in more detail.
1.1 Introduction
PMC B-Language Support provides for functionality to keep your B-Language components on the same level as the components of the languages, which are delivered in the PMC solutions. During installation of the PMC solution, also the B-Language components are updated automatically. Language-dependent parts of the components are retained as much as possible.
To prevent newer components being overwritten by older ones a new format for Translation Service Packs has been defined. These new format Translation Service Packs are not available at this moment. Service Pack 12 (for BaanIV c4) will be the first Translation Service Pack in the new format. However, to be able to install the translated components up to Service Pack 11 in one go, the Translation Service Pack 11 will also be available in the new format, and this one will contain all translated components accumulatively. This accumulative Translation Service Pack 11 will be available at the same time as Translation Service Pack 12.
Note 1: When B-Language Support is activated, do not install the old-format Translation Service Packs anymore, because newer components may be overwritten by older ones.
Note 2: B-Language Support only works on already installed B-Language base installations and cannot be used to install a new B-Language on an existing running system.
1.2 Getting Started
The following steps have to be executed to get started with B-Language Support:
n Define the parameters (see Chapter 3).
n Define the B-Language(s) you want to be updated automatically during installation of PMC solutions (see Chapter 4).
n Define a Package Combination at the level of your Update VRC. Use sessions “Maintain Package Combinations” (ttaad1120m000) and “Maintain Packages by Package Combination” (ttaad1121m000). This package combination is mandatory for being able to compile your updated B-Language components.
n Define developer parameters for the user who installs PMC solutions (e.g. “bsp”). Use session “Maintain Development Parameters by User” (ttadv0110m000). These parameters are mandatory for being able to compile your updated B-Language components.
n Bring the B-Language components to the level of the components, which have been installed with PMC solutions (see Chapter 5).
After these steps have been executed, installing new PMC solutions will keep your B-Language components up to date.
1.3 Menu PMC B-Language Support
The menu with the new functionality can be found in the Maintenance submenu of PMC (Recipient):
The configuration of what is set in the Maintain PMC B-Language support Parameters (ttpmc3100m000), and which B-Language is filled in, in the Maintain B-Languages by Update VRC (ttpmc3101m000) will control the functionality under process solutions with regards to B-Languages. If these sessions are not used and filled then PMC will act as normal and ignore the B-Language functionality.
1.1 Session PMC B-Language Support Parameters (ttpmc3100m000)
When this session is used for the first time, the system will fill the parameters with a default value. Change these settings to you own requirements and save the information.
The next paragraphs explain the parameters in detail.
1.1.1 Overwrite Description When Base Description Changes
This parameter specifies whether, the B-Language description is overwritten by the English one, when the English one has been changed.
During installation of PMC solutions, a check is done whether the English description has changed. The corresponding component in the B-Language is changed based on this parameter.
PMC cannot always know whether the English description has been changed because the English components may not have been installed initially. For this situation the parameter Adopt Base Language Descriptions for First Time Components applies.
Regardless of this parameter setting, the descriptions in the B-Language will be replaced when the new format translation service pack is installed.
The system default for this parameter is “Yes”.
Setting advice
“Yes”
When the English description has been changed, this description is also used in the B-Language. This is advised for environments, where users can read and understand English texts.
“No”
The B-Language descriptions are kept when the English descriptions have been changed. This setting is advised for environments, where users cannot read and understand English texts.
1.1.2 Adopt Base Language Descriptions for First Time Components
This parameter specifies whether, the B-Language description is overwritten by the English one, when the system does not know whether the English description has been changed. This is the situation when English is not installed initially on the system and the component is changed for the first time.
When English is installed initially or the component is changed again (then the English description is known from the previous solution), the parameter Overwrite Description When Base Description Changes applies.
Regardless of this parameter setting, the descriptions in the B-Language will be replaced when the new format translation service pack is installed.
The system default for this parameter is “No”.
Setting advice
“Yes”
B-Language descriptions will be overwritten when a component is changed for the first time and the English components are not installed initially. This setting is not recommended, because a lot of descriptions may be overwritten by English ones. Only when you want to be sure to have the newest description and your users are able to understand the English descriptions, you can use this setting.
“No”
The B-Language descriptions are kept for components, which are changed for the first time.
1.1.3 Overwrite Help Texts when Base Help Text Changes
This parameter specifies whether the B-Language help text is overwritten by the English one, when English help text is delivered in a solution.
Regardless of this parameter setting, the help texts in the B-Language will be replaced when the new format translation service pack is installed.
The system default for this parameter is “No”.
Setting advice
“Yes”
When the English help text has been delivered in a solution, this help text is also used in the B-Language. This is recommended when you prefer up to date English help texts instead of older B-Language help texts and for environments, where users can read and understand English texts.
“No”
The B-Language help texts are kept when English help texts are delivered in a solution. This setting is advised for environments, where users cannot read and understand English texts.
1.1.4 Compile / Dump reports, Forms and Menus During Installation
This parameter specified whether report, forms and menu must be compiled or dumped in the B-language during the installation of solutions.
The system default for the parameter is “Yes”.
Setting advice
“Yes”
Reports are compiled, forms and menus dumped in the B-Language during the installation of solutions. This will slow down the installation of solutions.
“No”
Reports, forms and menus are not compiled / dumped in the B-Language during the installation of solutions.
In this case session Compile / Dump B-Language Components (ttpmc3210m000) must be used after installation of solutions to be able to use the modified components in the B-Language.
1.1 Session Maintain B-Languages by Update VRC (ttpmc3101m000)
When a PMC solution is installed in an Update VRC, the language dependent components of that solution are copied to the B-Language(s) that is / are specified in this session. When this session has not been used, then the B-language functionality is ignored by PMC during installation of solutions.
1.1 Introduction
This session should only be used for components of solutions, which have been installed before the B-Language Support was activated.
The end result of this session is that the functionality level of the B-language will be the same functionality level as the A-language for all installed solutions.
When B-language Support has been activated (by specifying parameters and B-Languages to support, sessions Maintain PMC B-Language support Parameters (ttpmc3100m000), and Maintain B-Languages by Update VRC (ttpmc3101m000)), the components are copied automatically during the installation of solutions.
1.2 Session Copy Components of Solutions to B-Languages (ttpmc3200m000)
Make the selection ranges of solutions to copy or based on date range then start the copy option.
The system will select all language dependent components from the given range. Before the real copying starts, the user is asked to confirm the process, after the system has displayed the number of components to be processed.
The components will be copied from the English to the B-language.
The parameter ‘Overwrite Description When Base Description Changes.’ is ignored, because the system does not know whether the English description have been changed.
The parameter ‘Adopt Base Language Descriptions for First Time Components‘ is used; it is recommended to have this parameter set to “No” otherwise a lot of B-Language descriptions may be replaced by an English one.
The parameter ‘Compile / Dump reports, Forms and Menus During Installation‘ is also ignored. All processed reports, forms and menus will be compiled or dumped in the B-Language.
The report will contain a list of all processed components, including the compiler output for processed reports, unless ‘Print Errors Only’ is set to “Yes”; then only compiler errors will be printed for the reports.
2.1 Introduction
During installation of PMC solutions when B-Language Support is activated, the components are copied to the B-Language. When the parameter ‘Compile / Dump reports, Forms and Menus During Installation’ is set to “Yes” these components are already compiled and dumped. Then this session is not necessary to be executed. When this parameter is set to “No” then this session must be executed to activate the changes in reports, forms and menus for the B-Language.
2.2 Session Compile / Dump B-Language Components (ttpmc3210m000)
Make the selection ranges of solutions for which the components have to be compiled or dumped. Solutions can be selected by Installation Run. This is a collection of all solutions, which are installed in one go, e.g. an individual solution and all its dependencies, or a weekly collection. Use the Compile/Dump option to start the process.
The system will select all reports, forms and menus from the given range and compiles or dumps them.
The report will contain a list of all processed components, including the compiler output for processed reports, unless ‘Print Errors Only’ is set to “Yes” then only compiler errors will be printed for the reports.
3.1 Introduction
This session will print the English description and also the B-language descriptions of installed solutions to be able to perform checks on the validity of the descriptions in the B-Language. This is useful when the option is chosen for retention of all B-language descriptions, and allows the customer to translate critical descriptions himself.
3.2 Session Print B-Language Components (ttpmc3410m000)
Make the selection ranges of solutions for which the descriptions have to be printed. Solutions can be selected by Installation Run. This is a collection of all solutions, which are installed in one go, e.g. an individual solution and all its dependencies, or a weekly collection.
To print only differences between the old description and the new description (in either English or the B-Language) set the option ‘Print differences Only’ to “Yes”
Note that old descriptions are not always printed because of new components or first time changed components.
Use the Print option to start the process.