Question about attachment and history for CQ (7.1.2) importer (to RTC 4.0.1)
Hello,
If a CQ defect contains multiple attachments or multiple history entries, the CQ query will return multiple result lines. If this query is used, multiple result lines will correspond to one single CQ defect. When CQ importer creates a new RTC work item, is it smart enough to handle those multiple entries in CQ query for the same defect so that only one work item will be created?
The CLM 4 information center did not mention how we handle the attachments and history with CQ defect during the import.
Thanks and regards
Accepted answer
Hi Frank,
Even if a CQ record contains multiple attachments or history entries, the CQ Importer will still create only one work item in RTC.
One way to verify this is to look at the .zip file that is created after you export your records to XML. There should be one .xml file for each of your CQ records to be imported. The .xml file name will be the ID of your CQ record. If a record has any attachments, they are stored in a corresponding folder in your .zip file (the folder will also have the name of your CQ record). Each .xml file represents one work item that will be created in RTC, so you should not see duplicates.
Thanks,
Matt
Even if a CQ record contains multiple attachments or history entries, the CQ Importer will still create only one work item in RTC.
One way to verify this is to look at the .zip file that is created after you export your records to XML. There should be one .xml file for each of your CQ records to be imported. The .xml file name will be the ID of your CQ record. If a record has any attachments, they are stored in a corresponding folder in your .zip file (the folder will also have the name of your CQ record). Each .xml file represents one work item that will be created in RTC, so you should not see duplicates.
Thanks,
Matt
One other answer
I've created Add note to CQ Importer doc. to specify how Importer handles multiple attachments (248060) to update the help with this information.
Ken