Kbase P95253: What is the Migrate Widget Translation Tool?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/3/2004 |
|
Status: Unverified
GOAL:
What is the Migrate Widget Translation Tool?
GOAL:
How to use the Migrate Widget Translation Tool?
GOAL:
Dynamics 2.1A SP03
FACT(s) (Environment):
Dynamics 2.1A
FIX:
The Migrate Widget Translation Tool Allows you to generate entity-based translation records by migrating widget-based translations for selected entities and languages.
The entity translation is used by DynView and DynBrow objects linked to a DynSDO, and DynView objects linked to a static SDO. The entity translation is also used by the Find/Filter options in the SmartToolbar.
The Migrate Widget Translation tool can be launched by running the afmigtrnww container from the Dynamic Launcher (AppBuilder window Compile>Dynamic Launcher).
The Migrate Widget Translation window has the following options:
- Entity tab - Allows you to select entities in the Repository for which to generate an entity-based translations from widget-based translations, and specify source and target languages.
- Buttons Select All and Deselect All can be used to select/deselect all the entities in the Entity Browse.
- Logging tab - Shows the results of the migration in an editor.
The logging data is appended to a log file named translation_migration.log, stored at the SESSION:TEMP-DIRECTORY. This log file can be deleted after the migration process is complete.
Entity tab options:
- Source language - List of defined languages. The migration process looks translations for the specified source.
- Target language - List of defined languages. Defaults to the language used by the session. The migration process creates translations for the specified target language.
- Database - List of databases with defined entities. Option <ALL> can be used to specify all the databases with defined entities.
- Entity Browse - List of the enties for the specified database.
- Remove widget-based translation - When a widget-based translation is found for a field in a selected entity, this option instructs the migration process to remove all the widget-based translations matching the widget name and translation used for the specified source and target languages. If tooltips are set for a widget-based translation, the translation is not deleted. Since there are some translations that are only available using widget-based translations, use this option only if you are certain that the applications using the Repository do not need them. (Windows using DynBrow and static SDOs do not use entity-based translations.)
- Skip creation of data field translation if multiple translations are found - If this option is set, a widget-based translation for a widget with multiple translations available is ignored, and no entity-based translation record is created.
- Test migration - Report migration changes without updating the repository - When this option is set, translations records are not created nor deleted, but logging information is displayed in the Logging tab that shows the translations records that would be created or deleted when the migration is run with this option turned off.
Please note that the migration process looks for widget-based and entity-based translation records (widget type: BROWSE, FILL-IN, DATAFIELD, etc) for the fields of the selected entities that do not have a translation record. If a translation record is found, it is determined if there are any other translation records available, depending on the options selected, a translation record using DATAFIELD as the widget type is created, and widget-based translation records matching the source for the translation are deleted...