TeamForge connector 2.3 adds these new
features.
- Support for TeamForge 7.1
- TeamForge connector (CCF) 2.3 supports
TeamForge 7.1.
- Lean requirement type mapping
-
- Support for requirement type ‘ALL’ to sync all requirement types
from HP QC/ALM to a single TeamForge tracker using a
single repository and graphical field mapping.
- Eliminates the need to create multiple repository mappings for each
requirement type in HP QC/ALM, which in turn reduces field mapping
maintenance effort for CCF admins.
- Reduces the number of QC connections, which results in improved
performance and stability.
- Supported for all three types of field mappings namely Custom XSLT,
Mapforce Mapping and Mapping Rules Mapping.
- For more functional and technical information, see CCF blog: The lean SyncUp.
- Manage field mapping through Web UI (CCFMaster)
-
- Ability to view and manage the associated field mapping for the
repository mapping direction from Web UI.
- Support to create field mappings from existing field mapping
templates for the repository mapping direction directly from Web
UI.
- Support to create new linked field mapping from the existing field
mapping templates in the Web UI.
- User will be able to switch/set active field mapping and delete
inactive field mapping for the repository mapping direction from the
Web UI.
- Field mappings can be linked/created from both connector and project
mode field mapping templates from the Web UI.
- Improved log output from synchronization engines
- Log entries about artifact updates and creation now contain information
about the affected TeamForge
tracker.