Create type mapping
Define the mapping between data sources in a connection.
A type is a system asset such as an epic, issue, requirement, task, or user story. When creating a connection, you must add at least one type to synchronize between your master and target data sources. For example, you may want to map a Broadcom Rally Central Hierarchical Requirement to a Story.
The types that are available to add to a connection are limited to the types that you added to your data source. If the type that you want is not listed, return to the Data Sources tab and add the type to the data source. For details, see Create a data source.
Note: If you save the connection before adding any types, you can then edit it and select which types you want. If you do not save the connection before pressing next (to go to the Types and Fields page), Micro Focus Connect will automap a preselected list of types and fields.
You define type mapping in the Connection Wizard, as a step in creating a connection, or later when editing a connection.
To define type mapping in a connection:
- In the connection wizard, click Next to open the Types and Field tab.
In the Default Sync Direction list, select a direction for data synchronization. Synchronization between all types and fields will be performed in this direction. You can override this setting for specific types. Possible values for synchronization direction are:
From Master Data is only synchronized from the master to the target. To MasterData is only synchronized to master from the target. Bi-Directional Data is synchronized both to and from the master and target. (This is the default.)
You can allow Micro Focus Connect to automatically map the data sources' types and fields. Click Auto Type Mapping. Micro Focus Connect will attempt to auto-replace and map all types exposed by the selected data sources, and their fields. If you choose Type one, Connect resets the types that you see in the mapping to the types that are available in the auto-map.
Caution: Mapping that you may have already manually input can be overwritten.
If you want to set the type and field mapping manually, click + Type Mapping. The Add Type Mapping window opens. For more details, see Map types manually.
If Micro Focus Connect cannot map the connection's types automatically, you can map them manually.
To add a manual type mapping:
- In the Types and Fields tab of the connection wizard, click + Type Mapping. The Add Type Mapping dialog box opens.
- The Target Type and Master Type fields list all the types that you exposed in the target and master data sources. Select the types to map from the target and master data sources.
- In the Direction field, select a direction for data synchronization. Select the "Inherit" option to use the default direction that was set in the main Types and Fields tab. For details, see Define type mapping in a connection.
After selecting the types to map, you can now map the types' fields. Click Fields.
- You can allow Micro Focus Connect to automatically map the types' fields. Click Auto Type Mapping. Micro Focus Connect will attempt to map all fields between both types.
- To define a manual field mapping, click Add Field Mapping.
Select fields in the target and master data sources to map with each other.
For details on the field types that can be mapped, see Define type mapping in a connection.
For details on mapping relationship fields, see Relationship mapping.
- Select the synchronization direction in the Direction list for each field. By default, the direction is inherited from the type mapping.
In the Conversion field, in most circumstances leave the default "No Conversion" value.
Apply one of the following values only after careful consideration:
Master is HTML If the master side of a field mapping contains HTML-formatted content and you want, or are allowed only, plain-text content in the target. This setting converts the HTML content in master to plain-text content in target. Target is HTML If the target side of a field mapping contains HTML-formatted content and you want, or are allowed only, plain-text content in the master. This setting converts the HTML content in target to plain-text content in master. Apply user map If neither side of the mapping is a user property, you can apply the user map by selecting this option. No Conversion The field data is not altered when synchronizing.
- If the fields you are synchronizing use different values, create a value map. For more details, see Create value maps.
- Click the OK button to save your mappings and close the Add Type Mapping dialog box.
In addition to mapping attribute fields between types, you can also map relationship fields.
A relationship field defines the link between two types in a data source. For example, in ALM Octane, a story is linked to a feature via the story's Feature field.
Micro Focus Connect provides the ability to synchronize those relationships between data sources. For example you can map and synchronize the ALM Octane story-to-feature relationship with a similar story-to-epic relationship in Jira.
Considerations for relationship mapping:
- The relationships in either data source may not be the same type. For example, ALM Octane's story-feature relationship is a parent–child relationship. Whereas most relationships in Jira are many–many relationships.
Where there can be an ambiguity between relationship and attribute fields, Micro Focus Connect represents the relationship as a field with the prefix “link”.
For example, in the list of Jira story fields, there is a fixVersions field. This is a regular attribute field that is populated in Jira by a plain string. Micro Focus Connect adds a link.fixVersions field that represents the story's relationship to a virtual fixVersion entity. This allows you to treat Jira's fixVersions like an ALM Octane release.
If you have mapped two select-list fields, you need to make sure that the fields' values are also mapped.
A value map defines how a field value in Product A maps to a field value in Product B.
To define value maps:
- In the connection wizard's Types and Fields tab, expand a type mapping. The types' fields are listed.
- Click the Edit value map button . The Value Maps dialog box opens.
- Click Auto Value Mapping to allow Micro Focus Connect to map the field values automatically, or + Value Map to map the values manually.
- On each row, select a value in the master's field to map to the corresponding value in the target's field.
It is possible that the field in Product A has more values than the equivalent field in Product B. In this case, you need to map more than one value in Product A to the same value in Product B.
|Product A||Product B|
The last value in Product A that is mapped to the same value in Product B will appear in bold (see above). This indicates that, when changes are synchronized from Product B to Product A, the "Open" in Product B will translate to "In Progress" in Product A, and not to "New".
The following table lists the supported field type mappings.
|Field type||Maps to types|
|datetime||datetime, richtext, string, date|
|boolean||boolean, richtext, string, enum|
|long||long, richtext, float, int, double, string, long|
|richtext||richtext, datetime, float, boolean, int, double, enum, date, string, user, long|
|float||float, richtext, int, double, string, long|
|int||int, richtext, float, double, string, long|
|double||double, richtext, float, int, double, string, long|
|enum||enum, richtext, enum, string, boolean|
|date||date, richtext, datetime, date, string|
|string||string, richtext, datetime, float, boolean, int, double, enum, date, string, user, long|
|user||user, string, richtext|