Hi - I've away from DOORS since version 8.x and I'm coming across some DXL features that I'm not familiar with and assume have been introduced since then. I need some advice on whether the Auto Translate feature for database ID's extends to when a project is archived and restored on a different database. This is the feature that updates specific DB ID's assigned to link modules in code created by the Analysis Wizard to the DB ID's assigned when a project is archived and then restored. In the highly restricted environment that I am working in, I don't have access to another DOORS database to test this out.
Paul Miller PMiller - Tue Apr 24 21:03:23 EDT 2018 |
Re: DXL Auto Translate feature Tested on our DOORS 9.6.0.3. Made on company DOORS DB a restore of EasyStart and added a view with Analysis Wizard showing specific links from User Requirements to System Requirements. Archived this and restored the project to my local DOORS DB and the traceability column works and was autotranslated with both DOORS DB identifier and (formal) module ID changed. This was also commented in Layout DXL code: //Auto Translated: string limitModules[1] I would presume this translation would work also on specific link module ID. |
Re: DXL Auto Translate feature PekkaMakinen - Wed Apr 25 05:43:19 EDT 2018 Tested on our DOORS 9.6.0.3. Made on company DOORS DB a restore of EasyStart and added a view with Analysis Wizard showing specific links from User Requirements to System Requirements. Archived this and restored the project to my local DOORS DB and the traceability column works and was autotranslated with both DOORS DB identifier and (formal) module ID changed. This was also commented in Layout DXL code: //Auto Translated: string limitModules[1] I would presume this translation would work also on specific link module ID. Thanks Pekka
Paul Miller |