New instance is not getting created after importing reqIF File in DNG
Hello Team,
We are using DNG system with below details
IBM Engineering Requirements Management DOORS Next 7.0.2 SR1 DOORSNext7.0.2-I20220722_0732
The patch is active for RM. For details about the patch, see the readme.txt file. 7.0.2 SR1 iFix027
Steps :
1: We import ReqIF file and we get all the required modules containing artifacts and components properties stuff imported
2: We delete the some of the modules and along with their respective base folder
3: We Re-import the same ReqIF file
Expectation:
Since the previous imported data is deleted, tool shall create new module with new artifact ids
Actual:
Post re-import, tool is created the new module with new artifacts with same old id(which was deleted)
Is it a excepted behavior?
Is DNG somehow storing the deleted artifact data somehwere in database(even after deleting it permanently)?
|
2 answers
Hi Rajat,
The behaviour is expected. When an artifact is created from reqif a Map is created in RM DB, which stores the artifact id's and reqif id's, this map is created because during a round trip RM should not create any duplicate. Hence the behaviour.
Comments
Hello @Bhagath P B,
Thanks for quick response, but is there any possibility to even delete it from DNG DB as a jazz admin?
Reason : Because when we get initial requirement in form of zip files(which contains ReqIF and ole files) from customer, we import it to DNG project area but then sometime we have to delete it (incase requirement is revised) so the customer re-share this in zip format, sometimes the same old requirement is repeated but then when we re-import the zip file, it create a requirement with same old id and timestamp which gives wrong impression during review
Thank you
Hi Rajat,
Best way is to first import to a test project, verify what all you need and then import them to your actual project.
|
Ian Barnard (2.0k●6●13)
| answered Feb 22, 8:54 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Feb 22, 9:55 a.m. As Bhagath says, what you're seeing is the expected behaviour. If the artifacts you deleted are reimported they're recreated with the same ID.
It sounds like you shouldn't be deleting the requirements you don't want, instead leave them there and perhaps link to the ones you're interested in keeping and not to the ones you aren't interested in, then re-importing will only update the existing artifacts but won't impact the linked ones so you can still get views of the artifacts you're interested in. Or put the artifacts you're interested in into a module so you only see them when you view the module?
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.