|Repository Server Management / Upgrading the repository database for name change propagation|
Ambiguous entities require user intervention to map them to defined interfaces or, alternatively, to keep them as text form.
When a test module or action contains entities that belong to more than one interface, the entities are referred to as ambiguous entities. TestArchitect is not able to automatically create unique one-on-one references for those ambiguous entities. Instead, TestArchitect displays a dialog box containing (see the example below) the list of all ambiguous entities and which interface to map the ambiguous entities to.
The Specify Interface for dialog box has a table that lists the line numbers ( Line column) where the ambiguous entities (Interface Entity column) are found and which interfaces (Map to interface column) the ambiguous entities should be mapped to. The last column contains check boxes for enabling the entity mapping for each specific row. To enable the check boxes in the last column, you must select the check box Apply the selected mappings specified above to ALL entities with the same names in this item. Ambiguous interface entities with the same names are grouped together as a single unit and can only be mapped to a single interface. Selecting a check box to map a grouped entity automatically disables the check boxes for mapping other ambiguous interface entities in the same group. For example, both ambiguous interface entities named login in the above dialog box (lines 18 and 25) are in the same group and mapped to the same Car Rental interface. If the check box for the ambiguous entity on line 18 is selected, the check box for the ambiguous entity on line 25 will be disabled, and vice versa.
When mapping an ambiguous entity to an interface called [--Keep as text--], which is the default value, the name of the ambiguous entity is mapped to a text string whose value is the same as the string name of the ambiguous entity. Unlike mapping an ambiguous entity to a valid interface, any ambiguous entity mapped to [--Keep as text--] can no longer be available for automatic name change propagation, and you will not be prompted to remap the [--Keep as text--] entity again. (For example, if you were to upgrade the repository database based on the mapping dialog box above, the View cars entity could still enjoy name change propagation after the database upgrade, but the View orders entity could not. If you want all ambiguous entities to map to [--Keep as text--], select the check box Keep all items as text.
An ambiguous entity may span more than one module in a project, in which case you can specify the mapping for that ambiguous entity for each module. Or you can apply all mappings specified on the Select Interface for Interface Entity dialog box to all modules in a project during the database upgrade by selecting the checkbox Apply the selected mappings specified above to ALL entities with the same names in this item.
When you are satisfied with how ambiguous entities are mapped, click the OK button on the Select Interface dialog box to map all ambiguous entities as specified and continue. If you click the Close button, TestArchitect maps all ambiguous entities listed in the Interface entity column to the default [--Keep as text--].