Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Edit Mode Default - Exclusive Edit, can this be changed??
Topic Summary: Configuring DOORS to have a edit mode default to not be Exclusive Edit
Created On: 12-May-2008 18:01
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 12-May-2008 18:01
User is offline View Users Profile Print this message


Brenda Cornell

Posts: 29
Joined: 7-Jul-2005

We just started trying to use Shareable Edit capability on a project that have a lot of BSA's capturing requirements. We went through the Shareable Edit routine, but now someone is asking if there is a way to make a module default to open to 'Shareable Edit' when you double click on the module?? They are presuming someone will forget and get into Exclusive Edit directly thus locking out all others.

The Help indicates to 'Configure DOORS' but I'm not coming up with anything there.

From what I can tell, there isn't any way of configuring DOORS to indicate that when you double click on a module to have it go into any other mode other than Exclusive Edit. Thus in order to switch to a different mode, you have to go into Edit>EditMode and select Shareable Edit (or Read Only).

Can anyone confirm this for me, such that I can get back to this person and indicate this is a training/communication issue. If people are opening modules in Exclusive Edit, it's just a matter of time before they get tired of getting the perverbial call telling them they are in Exclusive Edit and they need to switch to Shareable Edit.

Thanks.

-------------------------
Brenda Heiss Cornell
Report this to a Moderator Report this to a Moderator
 12-May-2008 18:11
User is offline View Users Profile Print this message


Scott Boisvert

Posts: 348
Joined: 14-Apr-2006

See the section in the DOORS help titled "Summary of command line switches". You can change the default double click to open a module in either "READ_ONLY", "READ_WRITE" or "READ_WRITE_SHARED". This can be done either in the registry or by using the -o switch in the Target field of the DOORS Icon properties.

The target field will look something like this:

"C:\Program Files\Telelogic\DOORS_8.1\bin\doors.exe" -o READ_WRITE_SHARED -O READ_WRITE_SHARED

Keep in mind this will cause you to open every module in Shareable edit (the -O causes the module to open in Shareable edit when a link is followed that opens a module).

If it is just one particular module you want to open in shareable edit, you could write a trigger script that would force the module to open in shareable edit if the user had RMCD access and read-only if they do not.

-------------------------
Scott Boisvert
Engineering Tools Administrator
L-3 Communications - Avionics Systems
scott.boisvert@l-3com.com
Report this to a Moderator Report this to a Moderator
 12-May-2008 19:05
User is offline View Users Profile Print this message


Brenda Cornell

Posts: 29
Joined: 7-Jul-2005

Thanks for the reply Scott.

In our situation, we typically don't have admin access to change our registry so that option is out.

I tried the other option and that did work, and as you indicated it opens any module in Shareable Edit mode whether you've made it sharable or not.

Seems like this is an option for those people that can't get it straight in their heads to switch to a different edit mode (shareable in this case). But it wouldn't be something I'd be readily agreeable to rolling out to everyone because we haven't roled out Shareable edit to many project and we only intend to with a limited projects.

Thanks.

-------------------------
Brenda Heiss Cornell
Report this to a Moderator Report this to a Moderator
 12-May-2008 19:06
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Expanding on Scott's fine post:

You cannot change the behavior for individual modules. The default open mode when double clicking and when following a link is defined on each client.

Letting folks by default open Edit was a disaster right from the beginning, as folks back in version 4 days could 'Edit' a module to which they had only R rights, and would effectively lock everyone else out while they left it open all day. Even default to Shared is bad as it prevents the Admins from Editing the module when they need to.

These two parameters exist in the Registry on each client, which as Scott said can be overridden via command line switches.

We've forced every client to default to READ_ONLY for both double clicking on a module and for following a link. Folks must then explicitely decide to Edit or Share a module, before its open via the Open menu or after its open via the Edit >Edit Modes menu. This is only slightly inconvenient but its enough to stop the bozos from Editing a module that they only intend to look at anyway.

Now we are 'forcing' this in two ways [1] somehow the install folks managed to set up these parameters [2] we've got a database wide post-module-open trigger that fires once per day per user, and we just set the registry values (HKEY_CURRENT_USER) each time.

- Louie
Report this to a Moderator Report this to a Moderator
 12-May-2008 19:19
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

You need admin rights to change the HKEY_LOCAL_MACHINE area of the registry which would apply to everyone who uses that machine, but you don't need Admin rights to change the HKEY_CURRENT_USER area which applies to that user on that machine, and has precedence over HKEY_LOCAL_MACHINE.

With DXL, you can set the registry with the various setRegistry commands, but in this case these registry entries are also 'environment variables' so you can simply use 'setEnv' to set them, which goes to the HKEY_CURRENT_USER area.

You could also have a *.reg file that sets them and instruct folks to run it off the network.

Another option is to have a post-module-open database wide trigger that, when a module is opened Edit or Shared, forces the user to confirm the desire otherwise downgrading the module to Read-only. I suppose that trigger would have to have some mechanism for not doing that, say to accomodate folks and scripts who are opening lots of modules edit for some reason.

- Louie
Report this to a Moderator Report this to a Moderator
 12-May-2008 19:39
User is offline View Users Profile Print this message


Scott Boisvert

Posts: 348
Joined: 14-Apr-2006

I have a startup script that runs on our clients to configure the our customizations. The script only runs when the configuration versions don't match or it the version file doesn't exist on the local computer. But as part of my configuration I always set the modules to read only with the following DXL commands.

-------------------------
Scott Boisvert
Engineering Tools Administrator
L-3 Communications - Avionics Systems
scott.boisvert@l-3com.com
Report this to a Moderator Report this to a Moderator
 12-May-2008 20:36
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

This will do the same thing:

setenv("defopenmode", "READ_ONLY")
setenv("defopenlinkmode", "READ_ONLY")

Cleaner than setting registry and automatically works when you upgrade DOORS.

However, the 'getenv' perm will get the HKEY_LOCAL_MACHINE version even when the HKEY_CURRENT_USER exists, but is null.

- Louie
Report this to a Moderator Report this to a Moderator
 16-May-2008 16:56
User is offline View Users Profile Print this message


Gordon Woods

Posts: 35
Joined: 2-Mar-2007

and don't forget that if you are using thin clients and network products such as Citrix that the registry settings can be made at the presentations servers and not on the local machines or the data server - in that way one single change can be applied to all users of the database.

Since this such a common practice (and everyone I have spoken to has had to change to read only mode as the default), why is it not an option in the database properties - such a simple enhancement that would bring control from the IT department back to the Database Manager.


----------------

Gordon Woods
gordon.woods2@baesystems.com
Report this to a Moderator Report this to a Moderator
 16-May-2008 17:55
User is offline View Users Profile Print this message


David Pechacek

Posts: 674
Joined: 5-Dec-2006

I agree Gordon. There should be the option to specify certain things that affect all users at the database level. Here's hoping for DOORS 9.0.

-------------------------
David Pechacek
AAI Services Textron
dpechacek@sc-aaicorp.com
David.Pechacek@gmail.com
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.