CollabNet Connector Framework 1.4.2 resolves these issues.
| Artifact ID | Description |
|---|---|
| ccf373 | If the CCF database wasn’t running when you switched to non-graphical mapping in the mapping wizard, the GUI didn't indicate that the operation failed. This is now fixed. |
| ccf378 | Any operation that reports an incorrect "You do not have the required permissions to execute this action." message is now retried until it succeeds. |
| ccf379 | A problem where replaying a quarantined artifact led to unnecessary reprocessing of artifacts synchronized already, is fixed. |
| ccf380 | The code related to Quality Center attachments has been modified so that CCF will always download the complete attachment from Quality Center. |
| ccf381 | After downloading a Quality Center attachment, CCF now compares the attachment file size with the actual file size. If the file sizes don't match, a warning message is logged. |
| ccf382 | If an attachment can't be downloaded, CCF now proceeds with synchronization and ships at least the plain artifact data. A warning message is displayed in the logs. Network outages and clearly identifiable API bugs will still cause a retry of the attachment download operation. |
| ccf383 | If the CCF server and Quality Center server run in different time zones and only one has daylight saving time enabled, CCF now converts dates correctly. |
| ccf384 | CCF is now immune to problems in the source system's polling APIs where artifacts were reported with wrong last modification dates. With this release, the synchronization status record is only updated if the current last synchronized version is smaller or equal to the anticipated last synchronized version. |
| ccf385 | Whenever Project Tracker's web service APIs return an uninitialized last artifact modification date, CCF ignores the transaction in question. |
| ccf390 | The connector now ships large attachments from Quality Center to Project Tracker or TeamForge tracker and vice versa. |
| ccf393 | If CCF is shutting down and Quality Center's COM thread needs more than ten seconds to shut down, the JVM is halted forcefully to be able to release the COM thread properly. |
| ccf395 | Attachment download errors from QC 9.2 API are treated as transient networking failures and the transmission is retried up to ten times, and attachments with a reported size of zero up to three times. This works around an issue with QC APIs where attachments that are still being uploaded are returned and can be downloaded, but then cause a file not found error or an erroneous file size to be reported. |
| ccf409 | While mapping fields for an artifact type with square brackets in the name, the CCF GUI displayed errors. This is now fixed. |
| ccf411 | Attachments with square brackets in their names now ship to Quality Center. |
| ccf413 | The Save button in the Eclipse GUI was sometimes enabled when it should have been disabled. This is now fixed. |
| ccf418 | An unspecified hospital error code that resulted when a Quality Center requirement was checked out and locked, is fixed. |