![]() |
Telelogic DOORS (steve huntington) | ![]() |
Topic Title: Can I set the default Edit Mode on the server, so it applies to all users? Topic Summary: Created On: 9-Sep-2004 19:45 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: If the user used "setenv("defopenmode", "SHARE") it would take affect the NEXT time he logged in. Default share is a disaster as it opens share (and locks other out) even if the user doesn't want to edit it. Use default "Read" and train folks to explicetely use share or edit if that's they intend to do work. Default edit is even worse, and lots of times some bone-head who as only "R" access will "edit" a module and leave it open all day, and not realize nobody else can modify it. The other command is "defopenlinkmode" for when you open a module by following a link. We are struggling with custom code run from the server. If everyone has "R" access to the server file system (or shared folder), you can find a way to add a file containing "#include <//server/DXL/ExtraStartupStuff.dxl" onto everyone's client startup directory. You could alternatively modify everyone's client DOORS.exe icon to include the "-dxl" switch. As an admin, you would modify the contents of ExtraStartupStuff.dxl over time (e.g. adding and removing "doors going down Thursday pm" advisories). But all this presumes EVERYONE has access to the server, which isn't the case here. Too bad there isn't a database-login trigger (and in fact a logout trigger). But I have simulated one by using a post-module-open trigger that creates a new Config File once per day for each user. Such a trigger could realistically open another Configuration File containing this weeks Admin DXL code, and run it with the eval_ command. Are you really asking how to permanantly deploy useful DXL scripts such that everyone conveniently has access to the latest and greatest scripts? That's done by adding the "addins" and "projectaddins" commands to your registry, pointing to DXL on some server constructed appropriately. Admins just drop in the new DXL and the users automatically get them loaded into then module and explorer menus. - Louie | |
![]() |
|
I need to set the default edit mode to Shareable Edit for all modules. I would like to do this on the server side, rather than reconfiguring each client to do this by default. Is there a way to do this? Can I do it and still start the DB Server as a Windows Service?
------------------------- Shawn Stepper shawn.e.stepper@wellsfargo.com |
|
![]() |
|
![]() |
|
There is no way to do what you want.
The default edit mode is determined by the DOORSDEFOPENMODE environment variable (or registry setting). If this is not defined then the default double-click action is to open for exclusive edit. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
It seems like I could use the setenv command to set the default edit mode when the user opens the project. But this leads to my next question:
Is there a way to automatically distribute DXL code to users when they log in the the database server? It seems like there must be a way to do this. I expect to frequently update our custom codebase, and I don't want to have to repeatedly email the latest code to the whole group. Thanks for your response! Shawn ------------------------- Shawn Stepper shawn.e.stepper@wellsfargo.com |
|
![]() |
|
![]() |
|
If the user used "setenv("defopenmode", "SHARE") it would take affect the NEXT time he logged in.
Default share is a disaster as it opens share (and locks other out) even if the user doesn't want to edit it. Use default "Read" and train folks to explicetely use share or edit if that's they intend to do work. Default edit is even worse, and lots of times some bone-head who as only "R" access will "edit" a module and leave it open all day, and not realize nobody else can modify it. The other command is "defopenlinkmode" for when you open a module by following a link. We are struggling with custom code run from the server. If everyone has "R" access to the server file system (or shared folder), you can find a way to add a file containing "#include <//server/DXL/ExtraStartupStuff.dxl" onto everyone's client startup directory. You could alternatively modify everyone's client DOORS.exe icon to include the "-dxl" switch. As an admin, you would modify the contents of ExtraStartupStuff.dxl over time (e.g. adding and removing "doors going down Thursday pm" advisories). But all this presumes EVERYONE has access to the server, which isn't the case here. Too bad there isn't a database-login trigger (and in fact a logout trigger). But I have simulated one by using a post-module-open trigger that creates a new Config File once per day for each user. Such a trigger could realistically open another Configuration File containing this weeks Admin DXL code, and run it with the eval_ command. Are you really asking how to permanantly deploy useful DXL scripts such that everyone conveniently has access to the latest and greatest scripts? That's done by adding the "addins" and "projectaddins" commands to your registry, pointing to DXL on some server constructed appropriately. Admins just drop in the new DXL and the users automatically get them loaded into then module and explorer menus. - Louie |
|
![]() |
|
![]() |
|
Thanks Louie. Putting the dxl on a shared drive is definitely the simplest solution! Thank you also for the idea of setting the defaul open mode as read only. That definitely makes the most sense.
Shawn ------------------------- Shawn Stepper shawn.e.stepper@wellsfargo.com |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.