![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Setting the default view for multiple users? Topic Summary: Created On: 4-Jun-2007 16:49 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: EDITED TO FIX ERROR Awesome! I just made a few minor changes, some of which Tony suggested offline: In the DXL: I removed the last ELSE IF so that users in any other group get their user default view or the module default view. In the trigger: There is a missing quote in the trigger name (the first parameter), it should be as below (I can't include this inline in this message; the parser interprets the symbols as html tags) Using READFILE one needs to include the full pathname, but I couldn't get this to work for some reason (maybe someone can spot an error in my trigger command). Instead, I used an INCLUDE as below. This is easier, although apparently more prone to errors if the addin file is removed. I saved this command as another DXL so I could run it in multiple modules (see below) Finally: I used the "Run All" DXL written by A. Norkus which I downloaded from this forum to set the trigger on several modules I used the "Remove Persistent Triggers" DXL to confirm the triggers were in place (and check there were no other spurious triggers on any other modules in the database) Logged in using a variety of test users to verify they get the correct view Thanks, Ken. | |
![]() |
|
It appears that you have to log on as a user to set a default view for that user. This is very tedious if you have to repeat it for several users. What I want to do is create a new view and make that the default view for a group of (but not all) users. Has any one figured out a way to do this in DOORS 7.1?
Thanks, Ken. |
|
![]() |
|
![]() |
|
You cannot set the default view for another user.
Even more frustrating is that you cannot clear the default view for users either. The only way to achieve this that I can think of is to use a module open trigger and load the view based on membership of a group. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Here's how to do it.
Create a DXL file containing the attached and save to say addins/setView.dxl. Create a persistent trigger that fires when the module is opened and calls the dxl you just created. Open the module and run the following to do this. trigger("setView, module, post, open, 5, "readFile(\"addins/setView.dxl\")") ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Tony,
This looks almost exactly what I need. The only questions I have are: - In the last "else if" statement, how would I load the default view for all other groups; just enter a dummy statement to do nothing? - If I need to back this out, how do I remove the trigger? Many thanks, Ken. |
|
![]() |
|
![]() |
|
For the default case, add an else as follows:
else { load(view "Standard view") } Triggers are quite hard to remove - one of the reasons I don't use them that much. However, Michael Sutherland provides a script for removing triggers on his Galactic Solutions website downloads page The script is called Remove Persistent Triggers v2.2.1. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
EDITED TO FIX ERROR
Awesome! I just made a few minor changes, some of which Tony suggested offline: In the DXL: I removed the last ELSE IF so that users in any other group get their user default view or the module default view. In the trigger: There is a missing quote in the trigger name (the first parameter), it should be as below (I can't include this inline in this message; the parser interprets the symbols as html tags) Using READFILE one needs to include the full pathname, but I couldn't get this to work for some reason (maybe someone can spot an error in my trigger command). Instead, I used an INCLUDE as below. This is easier, although apparently more prone to errors if the addin file is removed. I saved this command as another DXL so I could run it in multiple modules (see below) Finally: I used the "Run All" DXL written by A. Norkus which I downloaded from this forum to set the trigger on several modules I used the "Remove Persistent Triggers" DXL to confirm the triggers were in place (and check there were no other spurious triggers on any other modules in the database) Logged in using a variety of test users to verify they get the correct view Thanks, Ken. Edited: 8-Jun-2007 at 14:02 by Ken McNair |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.