![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Help syncronizing modules... Topic Summary: Created On: 18-Nov-2002 16:25 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
In attempts to lock down only portions of a module we are trying to setup two seperate modules that will stay in sync. One, the master, will contain the object text and some core attributes. The other, the slave, will contain only attribles, and no object text. The modules would be linked together so that every object in the mast points to an object in the slave which would have additional attributes for the master object. This would allow us to lock the master to certain groups, but still allow those groups the ability to change corresponding attributes in the slave module.
The problems is in a method of keeping these objects in sync so that there is always a one to one relationship and they remain linked to the correct object in the slave module. I originally thought to use triggers, but that would not provide a solution for moving objects, nor do I know if it would even support adding and deleting objects in the slave module, since your only events are on open, close, read, and modify. Has anyone else tried this type of a configuration, or have any ideas on how this effect could be achieved? Any and all help would be greatly appreciated. |
|
![]() |
|
![]() |
|
Hello
Have you thought about using views? You can do this 2 ways: Only show the user the information they can change by creating views and denying access to the views that the user should not changed or show the information and only give the user read access to that attribute. Better yet, you can do a combination of both. I hope this help. Email: dvreed@northropgrumman.com |
|
![]() |
|
![]() |
|
Have you tried Access Rights? They can be applied to individual Attributes (even "Object Heading" and "Object Text").
I wouldn't pursue any dual-module scenario until I was sure that the existing DOORS Access Rights features do not meet the need. Any other solution would be significantly more complex. Are these other groups internal to your company, or are they external contractors/vendors? ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
If you are insistent that you want two modules, I would suggest the following;
Create the second module and fill with a 'large' number of empty objects where large is more than the expected maximum number of objects in the main module. (Use dxl for this, and do not bother with hierarchy.) Create a text attribute in the second module and populate this with the text value of the absolute number of the objecct. (Another job for dxl) Link by attribute from the second module to the first. (You may need to alter the link by attribute dxl so objects which do not yet exist in the first module, and deleted objects are dealt with cleanly) A regular re-application of 'link by attribute' will keep the modules in line. This is not a fully automated solution, and will need managing, but if you don't like the suggestions for access controls, it may solve your problem. Hazel ------------------------- Hazel Woodcock |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Help syncronizing modules...
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.