It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×6,035
×5,942
×118

question asked: May 23 '16, 1:40 p.m.
question was seen: 2,828 times
last updated: Jun 01 '16, 4:05 a.m.

Related questions

Migration by migration package migrates exclusions?

0
Danielle Silva (11●2●6) | asked May 23 '16, 1:40 p.m.
 Hi, I'm currently working in the migration of a project from DOORS version 9.6.1.3   to  DOORS NG 6.0.2. To do it, in following the instructions to generate a migration package and export it. However, when I import in doors next generation, my migrated modules appear with the old excluded requirements. How can I solve this?

One answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Koak Lodge (156●2●10) | answered Jun 01 '16, 4:01 a.m.
edited Jun 01 '16, 4:05 a.m.

(Assuming "old excluded" equals deleted, but not purged, objects in modules in DOORS.)

Migration packages include deleted objects in modules. There is a DNG attribute created called "ReqIF.ForeignDeleted". If it is "No value", then the object was not deleted in DOORS. I think "True" for deleted.

Two ways to deal with this:

In DOORS, purge deleted objects before exporting.

In DNG, filter on "ReqIF.ForeignDeleted" is "True" and delete them.

Hope that helps.

Your answer

Register or to post 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.