The migration tool merges map and UI edits as follows:
- For each edit or message, the migration tool does the first of
the following that applies:
- If a UI edit is specified, the migration tool converts the UI edit and its
associated message information to the corresponding EGL properties.
- If only a map edit is specified, the migration tool converts the map edit
and its associated message to the corresponding EGL properties.
- If the UI message is specified without its associated UI edit, the
migration tool converts the UI message to the corresponding EGL
property.
- If the map message is specified without its associated map edit, the
migration tool converts the map message to the corresponding EGL
property.
- If UI and map edit and message information are not specified, the
migration tool does not set the corresponding EGL properties. The
normal EGL defaults apply.
- In VisualAge Generator, Justify and Hex edit are only specified for map
edits, so they are always used to set the corresponding EGL properties.
|
Except as noted later in this section (Handling ambiguous situations for
data items), the migration tool migrates the default edits and messages in the
same way both with and without the associated parts.
|
Potential Problem 1: A problem only arises if conflicting
map edits and UI edits exist in VisualAge Generator and you really intend the
edits to differ between maps and UI records. The problem does not occur
until the item is added to a text or print form.
- Note:
- If you never used VAGen Web Transactions, only map edits should exist in
VisualAge Generator and you should not have a problem.
Possible Solution: Other than adding a comment to the data
item definition to list the VAGen map item edits and messages, there is
nothing you can do for the data item definition. If you add the item to
a text or print form, you can override any properties that need to differ for
that particular form.
Potential Problem 2: A problem can also arise if you use
the item in an EGL UI record. The item might have some additional edits
or messages that were migrated from the VAGen map edits.
Solution: Always review the edits for items in a UI
record.
| The same potential problems mentioned in the Migrating with the
associated part column apply. You can use the same
solutions.
|