![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Archive/Restore and Baseline linking Topic Summary: Created On: 4-Nov-2002 14:13 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
As many of you know, when you use archive/restore to exchange a module between databases, special care must be taken to capture the links in and out of the module. In addition, when restoring on top of an existing module, you also need to capture the links going into the module from all others (at least the way we do it - there is a period where the existing module has been deleted before the new version is restored).
Here is the problem: When the existing module is deleted, all links into it are also deleted (that is why you capture them, right?). This also includes links from prior baselines of other modules. Once the module is restored, you can restore the links for the current version of each module, but YOU CANNOT RESTORE LINKS FOR A BASELINE because, of course, you can't make any changes to the baseline. Does anyone already have a workaround for this? Is there a way of restoring without deleting the existing module, such that the baseline links don't get deleted? If there is not a simple solution to this, then clearly it has implications for those of us using archive/restore to exchange modules. Walt Roscello |
|
![]() |
|
![]() |
|
As far as I know you do NOT preserve links when you baseline: the baseline contains the data and attributes, but displays the CURRENT links only; for whatever that is worth. You should therefore capture the in and out link information (or better yet, capture the information about the linked partners as text attributes) before you baseline, thus presevering the state-of-the-links at the time of the baseline.
Your archive-here-restore-there scheme will really only work when the "here" database is the only one that makes changes to the module, and the "there" database needs only to read it or link TO it. If so, you would capture the TO link information in the other "there" modules, and reapply them in those modules when you restore the target module. - Louie |
|
![]() |
Telelogic DOORS
» Enterprise Operations
»
Archive/Restore and Baseline linking
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.