Structure Overview 

Use

The structure overview displays all fields (elements and attributes) in the source and target structures. In the structure overview, you can assign source and target fields to each other or include them in the data-flow editor

More information: Assigning a Field

The structure overview also contains a variety of additional functions that are described below.

Features

Functions in the Header Area

You use the structure overview on both the Definition and Test tab pages. Most of the buttons available in the structure overview are available on both tab pages.

Structure Overview Buttons

Button	Use
Tree View (only on Definition tab page)	View that only displays nodes for fields (elements and attributes) and their names.
Tabular Tree View	When you select this view, on the Definition tab page the field attributes or their type are displayed in addition to the tree view. In the test environment, you can enter values for the test in an additional column in the source structure.
Source Text View	Displays the structure as text in the editor. You can edit the text document directly in the test environment.
Expand Tree Collapse Tree	Expands/collapses tree.
Pretty Print (only on the Test tab page in the source document view)	Makes the XML document more readable by using indentations.
Show/Hide Search Field	Shows or hides the input help to search for fields in the structure. The search function does not support wildcard characters. To search for a node, you only need to enter the first letter of the node name.
Save Document Source	Saves the structure as an XML file.
Show Complete Path (only in Tree View or Tabular Tree View)	Displays prefixes for namespaces and numbering for duplicated fields in the structure overview. More information: Duplicating Subtrees
or (only in Tree View or Tabular Tree View)	Inactive or active filter for fields in the structure (see below)
Remove Unused Fields (only in the Tree View or the Tabular Tree View on the Test tab page)	Removes all fields from the structure of a test instance that are not used in any target-field mapping.

General Functions in the Source and Target Structures

Filter

To increase overall clarity, you have the option of reducing the number of fields displayed in the source structure, target structure, and test environment to a specified subset. The following table gives you an overview of the possible filter settings.

Filter Setting	Source Structure	Target Structure	Test Environment
Display Fields with Mapping Only	X	X
Display Fields Without Mapping Only	X	X
Display Directly Assigned Fields Only		X
Display Indirectly Assigned Fields Only		X
Display Selected Fields Only		X
Display Used Fields Only			X

Filter for Selected Fields in Target Structure

To display any number of target fields in the target structure, in the menu bar for the target structure, choose Display Selection Column ().

 The mapping editor displays an additional column in which you can select the fields you require. By using the where-used list (see below), the mapping editor can also select any fields that the where-used list contains.

Differentiating Field Names on the Same Hierarchy Level

The field names of the source and target structure must be unique. The mapping editor supports identical field names on the same hierarchy level in the following way:

●      Fields of the source and target structure can be qualified by namespaces

●      Attributes are differentiated from elements by a proceeding at sign (@) in the mapping editor.

Access Paths for Fields

For fields in the structure overview (on both the Definition and Test tab pages) you can copy the path for a field to the clipboard by choosing the context menu option Copy Path. This also applies to fields in the data-flow editor.

Recursive Structures

The mapping editor does not fully support the mapping of recursive structures (data types that reference themselves). In the structure overview, elements of this type are indicated by means of an icon ().

Due to their recursive nature, the substructures of these elements can theoretically be infinitely long. It is possible to map these elements in the mapping editor in a rudimentary fashion by using the context menu to expand a specific number of subnodes and then use them in target-field mappings.

Where-Used List (Source Structure Fields and Functions)

●      You can display the fields of the source structure or functions in a where-used list:

●      Position the cursor on a field to display a quick info that contains information about the target fields this particular field is assigned to by means of a target-field mapping.

●      To display a where-used list for a particular field or function, choose Where-Used List in the context menu. You can navigate directly to the target fields that a particular field or function is assigned to.

If a field or function is used for multiple target fields, you can easily filter it out of the target structure:

...

       1.      In the menu bar of the target structure, choose Display Selection Column ().

       2.      Call the context menu for a source field or function.

       3.      In the menu for the where-used list, choose Select All Fields (<Number of Usages>) in Target Structure.

Special Functions: Target Structure

Navigating to Target-Field Mappings

If a field in the target structure is green or yellow, this indicates that an incomplete target-field mapping already exists. Double-click a field to display it in the data-flow editor.

Target-Field Mappings for Particular Positions

To define target-field mappings for different positions of a target element that occurs frequently, the context menu for the target structure has the function Duplicate Subtree (see: Duplicating Subtrees). You have the option of deleting any duplicates that you create.

Disabling Fields

A mapping is complete when there is a target-field mapping for all obligatory target fields. In cross-system scenarios where the values for such fields are not entered during mapping, but at a later point in time, this specification is too restrictive. To disable a target field and all its subnodes, choose Disable Field in the context menu in the structure overview. The mapping editor shows disabled fields crossed out. The check and the mapping runtime ignore disabled fields.