If you are upgrading your existing Agile Business Suite Software to a higher release level, you can retain the translations for your screen layouts, Segment attributes, and captions. Similarly, you can retain the translations of your application.
FTU includes functions that enable you to merge your existing translations with the changes for the new release.
A Report is printed summarizing the merge. You can choose to print this Report without performing the merge.
Availability of Functions
These functions apply to built applications.
Note: Changes made with FTU do not change the Specification. If the Specification is rebuilt, changes made with FTU are lost unless you use the procedure outlined in "Translation Procedure" under Translating Individual Ispec and Teach Screens to retain your changes.
Requirements
You require the following files if you want to retain translations for screen layouts:
Unmodified LINCFORM file from the previous release
Translated LINCFORM file from the previous release
Unmodified LINCFORM file from the new release
You require the following files if you want to retain translations for Segment attributes and captions:
Unmodified MULTILANG files from the previous release
Translated MULTILANG files from the previous release
Unmodified MULTILANG files from the new release
Translating Screen Layouts
To translate your screen layouts, perform the following:
Ensure that the following files are all available on disk:
Unmodified LINCFORM file from the new release
Unmodified LINCFORM file from the previous release
Translated LINCFORM file from the previous release
Initiate FTU as usual, then enter :X in the System name property of the first screen.
A screen headed NGEN28 TRANSLATED FORMS FILE MIGRATION is then displayed.
Enter the names of the files in the properties in the following table.
Property | Description |
---|---|
This release | Unmodified LINCFORM file for new release |
Last release | Unmodified LINCFORM file for previous release |
Translated | Translated LINCFORM file (existing file) |
Enter your file names in the form:
file ON pack
Refer to Files Used with FTU for more information.
In the Enter 'Y' for GSD/DDAD property, enter N. (Translation of Segment attributes and captions is described later in this section.)
In the Enter 'Y' for merge (else report only) property, enter
N to print a summary report of the differences.
Y to proceed with the merge process, and overwrite the file for the new release. Refer to Results of Merging Translations for more information about the results.
Take one of the following actions:
To return to the Welcome screen, enter :Q or :R.
To receive online help details, enter :HELP.
To refresh the current screen, enter :?.
Translating Segment Attributes and Captions
To translate your Segment attributes and captions, perform the following:
Ensure that the following files are all available on disk:
Unmodified MULTILANG file from the new release
Unmodified MULTILANG file from the previous release
Translated MULTILANG file from the previous release
Initiate FTU as usual, then enter :X in the System name property of the first screen.
A screen headed NGEN28 TRANSLATED FORMS FILE MIGRATION is then displayed.
Enter the names of the files in the properties in the following table.
Property | Description |
---|---|
This release | Unmodified MULTILANG file for new release |
Last release | Unmodified MULTILANG file for previous release |
Translated | Translated MULTILANG file (existing file) |
Enter your file names in the form:
file ON pack
Refer to Files Used with FTU for more information.
In the Enter 'Y' for GSD/DDAD property, enter Y.
In the Enter 'Y' for merge (else report only) property, enter
N to print a summary report of the differences.
Y to proceed with the merge process, and overwrite the file for the new release. Refer to Results of Merging Translations for more information about the results.
Take one of the following actions:
To return to the Welcome screen, enter :Q or :R.
To receive online help details, enter :HELP.
To refresh the current screen, enter :?.