CollabNet Connector Framework

Thanks Hari, this is making more sense to me now. Is this true? I can add logic to setting artifactAction by either creating custom XSLT or by creating a mapping for this attribute with the CollabNet Desktop in Eclipse. In our graphical mappings ... [More] , there are already mappings from artifactAction in HP ALM to artifactAction in TeamForge. Should I modify this existing mapping? Or create a new one? Can there be more than one mapping from the same attribute? It looks like the mapping creation wizar... [Less]

Mikael, This link

Hi Hari, Thanks for your response, sorry mine has been so delayed. Can you point me to some documentation to understand your recommendation better? Something that explains top level attributes and artifact actions that depend on conditions? Mikael ... [More] Behrens From: hariharan k [mailto:[email protected]] Sent: Wednesday, April 4, 2018 6:44 AM To: [email protected] Subject: Re: [ccf-users] Updating Direct Cover Status in HP ALM causes sync traffic unnecessarily? As per your comments,... [Less]

As per your comments, you have made changes to Requirement, so when ever a changes occurs in Requirement irrespective of fields/mapping, CCF will try to sync the Requirement to Tracker. AFAIK, to skip the sync for particular field update, change ... [More] your top-level attribute and set artifact action to ignore Direct cover status field. Thanks, Hari ________________________________ From: Behrens,Mikael A (DFPS) [Less]

We are using CCF v2.3.6 to synchronize Requirements and Defects between HP ALM 12.53 and TeamForge 17.8. Certain operations in HP ALM on test sets and test cases cause many requirements those tests are linked to to change their Direct Cover Status. ... [More] This and the Modified date are the only two attributes that show as changed in the HP ALM history for these requirements when these operations happen. But we see evidence that the CCF is sending these changes to TeamForge even though neither Direct ... [Less]

Thanks Balaji, Removing the single RequirementType mapping from our QC-to-TF mappings seems to have fixed this issue. We will probably restrict ourselves to this single change rather than refreshing all of our mappings, unless CollabNet Support ... [More] instructs otherwise. Mikael Behrens DFPS From: balaji kandan [mailto:[email protected]] Sent: Tuesday, November 21, 2017 12:53 AM To: [email protected] Subject: Re: [ccf-users] NullPointerException when updating existing TeamForge artifacts ... [Less]

Hi Mikael, I believe the exception we see might be because of the requirement Type (non exisitng tracker field in TeamForge) Can we do a refresh on the field mapping configuration and map and use fields that are available in TeamForge. AFAIK in ... [More] TeamForge 8.1 non existing fields are ignored while doing a update. Now in TeamForge 17.8 we have added an implementation to do extra validation on the existing Trackers fields. May be that is why we see an exception while updating artifact with... [Less]

Thanks Balaji! CollabNet support has been engaged for a few days now. Based on your comments my colleague found an interesting mapping for RequirementType in both our QCtoTF and TFtoQC mappings. But there is not a RequirementType field in our ... [More] TeamForge requirements trackers. Is this some internal field in TeamForge we just cannot see? Or could it be the issue? Should we try removing it? The mapping exists in our production system, and our TeamForge 8.1 production system does not show this f... [Less]

Hi Mikael, After checking server.log, it seems while posting soap call for updating artifact it throws null pointer exception in Teamforge. The exception might be something to do with the data that we post to Teamforge. Need one confirmation, Can ... [More] you check QC2TF field mapping template and see whether any fields mapped is not available anymore in the teamforge Tracker. (That is validate mapped fields in the QC2TF field mapping template exist in the TeamForge tracker configurations.) Sending n... [Less]

Hi Balaji, Thanks, I'm attaching yesterday's log files. These are the same files I provided to CollabNet support (ticket CNSC-192996). These log files are for a CCF error that occurred at 2017-11-13 15:45:38. Requirement 31313 (artf57412) was ... [More] updated in HP ALM, changing priority field. export.xml is the failed shipment. Mikael Behrens From: balaji kandan [mailto:[email protected]] Sent: Tuesday, November 14, 2017 2:52 AM To: [email protected] Subject: Re: [ccf-users] NullPointerE... [Less]