![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Suppressing notification of soft-deleting a linked Module Topic Summary: DOORS notifies the user when deleting a modules with links in it. this makes DXL automation hard Created On: 20-Apr-2007 03:20 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|||
DOORS notifies the user when deleting a modules with links in it. This makes DXL automation hard since the user has to keep clicking on message boxes. How can I suppress this message box ? (see attached jpg)
Thanks! Jason
|
|||
![]() |
|||
![]() |
|||
Well, what about writing the DXL script in such a way that it explicitly deletes the links prior to deleting the module?
Regards, Peter |
|||
![]() |
|||
![]() |
|||
DOORS warns about deleting objects with incoming links for a good reason. It is generally not a good idea to do this!
Why would you need to automate deleting data? ------------------------- Tony Goodman http://www.smartdxl.com |
|||
![]() |
|||
![]() |
|||
we have a classified and unclassified DOORS DBs, and we want the classified side to have a read-only copy of the data contained in the unclassified side. we plan do to this by periodically archiving the unclassified modules, and then restoring them as read-only on the classified side. however, each time we do this, we need to delete the "old" copies on the classifed side to make room for the new restored archive. what we plan to do is rename the old module with when it was "updated" (deleted) in case there is some reason we might need it. the only reason i can think of why we'd need these old copies on the classified side is because of links that might havebeen made between classified modules and unclassified modules on the classified database. thus, we don't want to delete the links in case we need to undelete one of these unclassified modules to retreive link info (shouldn't ever happen that we'll need to do this....but "just in case").
When a formal module is deleted, the link modules still keep it's link sets alive, but inactive unless the formal module is undeleted.
Jason
|
|||
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.