TeamForge connector 2.2.1 adds these new
features.
- Support for TeamForge 7.0
- TeamForge connector (CCF) 2.2.1 supports
TeamForge 7.0
- Automatic check for the dummy service
- When you use TeamForge connector 2.2.1 (or
later) to integrate with TeamForge
7.0 (or later), you can use the in-built dummy service that runs within
TeamForge 7.0. CCF will
automatically detect the Integrated Application Framework (IAF) service
endpoint for TeamForge 7.0 and use
it. You do not need to separately install the dummy service on the TeamForge server. You do not need to
add or edit the ccf.iafServiceEndpoint property in
ccfhomeruntimeconfig.properties either.
- CCF Core properties are configurable in the user interface
- To help you configure the CCF Core more easily, the following properties are
available in the user interface:
- Use Alternative FieldName: Enables handwritten
XSLT scripts to refer to HP Quality Center display names during
transformation of artifacts.
- Ignore Connector Updates: To prevent
infinite update loops, updates made by the connector are not shipped
to the other connector participant by default. Turn off this setting
only if you are absolutely sure of what you are doing; and never
turn it off for both directions.
- Translate Technical ReleaseIds: If set to true,
human-readable file release names are translated to technical
release IDs (relxxx). Turning on this setting will impact
performance because further SOAP calls have to be made.
- Retrieve Parent Info For Tracker Items: Determines
whether parent information should be fetched for tracker items.