CollabNet Connector Framework

Need teamforge logs(vamessages.log and server.log created during this exception) to debug this issue further. As per export.xml it seems TeamForge SOAP API call is failing with a null pointer exception. Can you get us the logs to figure out why ... [More] null pointer exception happening during artifact updates? Thanks, Balaji Kandasamy ________________________________ From: Behrens,Mikael A (DFPS) [Less]

We are testing a new TeamForge 17.8 install. We are using the CCF 2.3.6 to synchronize several trackers with HP ALM 12.53. Currently the CCF is failing to update Requirements in TeamForge when they are updated in HP ALM. Updates in TeamForge are ... [More] getting to HP ALM, but updates in HP ALM are failing with this cause in the failed shipment: javax.ejb.EJBException: java.lang.NullPointerException I am attaching an exported failed shipment for a Requirement created in HP ALM. The CCF created the cor... [Less]

Thanks again, Mark. Giving our CCF user the permission that the Workflow requires seems to have fixed the issue. We did not have to do this with TeamForge 8.1 and the same Workflow. Mikael From: Mark Phippard [mailto:[email protected]] Sent: ... [More] Thursday, November 9, 2017 4:23 PM To: [email protected] Subject: Re: [ccf-users] "violates status transition constraints" error CCF has always had to go through the SOAP API so this is not something that would have changed or be new. Mark ... [Less]

CCF has always had to go through the SOAP API so this is not something that would have changed or be new. Mark On Nov 9, 2017, at 5:22 PM, Behrens,Mikael A (DFPS)

Thanks so much, Mark! Do the CCF's edits now have to conform to our Workflow restraints? I don't think the CCF was limited by this in our TeamForge 8.1 and CCF 2.3.5 environment. Was this a change in TeamForge since v8.1? Mikael From: Mark ... [More] Phippard [mailto:[email protected]] Sent: Thursday, November 9, 2017 4:16 PM To: [email protected] Subject: Re: [ccf-users] "violates status transition constraints" error That is not a bug, it means you probably need to change the Tracker confi... [Less]

That is not a bug, it means you probably need to change the Tracker configuration and look at what constraints have been created. CCF cannot uses API to update the artifacts so it cannot do what the rules are configured to not allow. Look in the ... [More] Tracker Workflow tab for this tracker in Project Admin. Mark On Nov 9, 2017, at 5:12 PM, Behrens,Mikael A (DFPS) [Less]

Hi, We have just upgraded our development TeamForge app to v17.8 and CCF to 2.3.6. We are synchronizing several trackers with HP ALM 12.53. My initial testing show that comments added to a defect in both HP ALM and TeamForge made it to the other ... [More] system. But creating a new Defect in HP ALM resulted in this error in the debug log and a quarantined artifact: CAUSE_EXCEPTION_MESSAGE: Setting field status in folder projects.alm_implementation_sandbox/tracker.defects to value 'New' violates status... [Less]

Thanks again, I was able to get our Defects sync'ing in our Dev environment. We were working with 3 copies of our production "databases": 1. TeamForge 2. HP ALM 3. CCF (Its database is on the server file system.) These three ... [More] databases were all from slightly different times. TeamForge was oldest, CCF was newest. Defects were not synchronizing because there were several new Defects created in this window of time difference between the databases. The CCF had records of newly... [Less]

Thanks so much for the quick response! I think I understand. Since the CCF data is more recent than the HP ALM and TeamForge databases, the CCF already has an identify mapping for Defect ID 3185, even though it was newly created in our Development HP ... [More] ALM. Currently in our HP ALM Dev database, 459003 is the maximum value of audit_log.au_action_id. This is the same value as the "Source last artifact version" of our HP-to-TeamForge mapping in the CCF. So should I remove all identity mappings in ... [Less]

An entry created in Identity mapping for all the shipped artifacts/defects. so delete the entry for 3185 from identity mapping and try to sync again. You have to adjust the identity mapping entries to get the defect sync match with TF. Thanks, ... [More] Hari On Saturday 07 October 2017 08:48 PM, Behrens,Mikael A (DFPS) wrote: > > Currently Defect synchronization is not working in our Development > systems. > > We are using CCF 2.3.5 to synchronize several trackers between HP ALM > v12.53 and Te... [Less]