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: Need Help with Sharable Edit Mode
Topic Summary: Locking and Inserting an Object
Created On: 19-Jul-2006 20:23
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.
 19-Jul-2006 20:23
User is offline View Users Profile Print this message


Nekeeta Miliam

Posts: 8
Joined: 6-Jul-2006

Can Somebody Help Me? I am in the shareable edit mode within my module.  I want to insert an object after the object that I have locked.  However DOORS is only giving me the insert object below option.... Am I doing something wrong or is it a DOORS 7.1 temp Hick-up?

Report this to a Moderator Report this to a Moderator
 19-Jul-2006 20:43
User is offline View Users Profile Print this message


Reik Schroeder

Posts: 361
Joined: 28-Jul-2003

Hi Nekeeta,

this problem can be solved very simple
To create Objects you need to lock the parent Object, not one on the same level you want to insert.
If you need to insert Objects on top level, you have to open the hold Module in exclusive edit mode.

Greetings
Reik Schr?der

-------------------------
Evosoft GmbH
for Siemens Industry Sector


Berlin, Germany
Report this to a Moderator Report this to a Moderator
 19-Jul-2006 21:36
User is offline View Users Profile Print this message


Dan Hopping

Posts: 75
Joined: 21-Nov-2002

If you have a module open in shared edit you can only 'insert under' from the object level at the top locked level. All other levels you can insert under or after.
Example.
Assume you have sharing set to 'level 2' and you have applied a lock in level 3.1.2
all sections will be locked for edit as shown and all else not editable.

lev 1
lev 1.1
lev 2
lev 2.1
lev 2.2
lev 2.3
lev 2.3.1
lev 2.3.2
lev 2.3.3
lev 2.3.4
lev 3
lev 3.1 <- locked for edit (you can only insert under at this level)
lev 3.1.1 <- locked for edit (you can insert either after or under)
lev 3.1.2 <- locked for edit (you can insert either after or under)
lev 3.1.3 <- locked for edit (you can insert either after or under)
lev 3.2
lev 4
lev 4.1
etc.....

This is because if you were to insert at the highest level of your locked data (lev 3.1 in this example) you would have to change the levels of unlocked data which you do not have permission to edit. (i.e. you would be creating a new lev 3.2 which would make the current lev 3.2 change to lev 3.3 but you do not have permission to edit the current lev 3.2). Make sense?
Report this to a Moderator Report this to a Moderator
 20-Jul-2006 00:06
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Let me try to say the same thing as the others, in an even more confusing way. Background: in order to support Shared Edit a module must be first set up with shared sections: the admin chooses which objects mark the shared sections and which objects do not. In a regrettable design decision years ago, one 'marks' the shared sections by specifying which objects have Specific Access, the others have Inherited access.

A 'shared section' is a Specific Access object and all its descendant objects that are Inherited themselves and can be traced directly through Inherited Access objects only.

3.2 Specific
3.2.1
3.2.2 Specific
3.2.2.1
3.2.2.2
3.2.3

In this example you have two objects that are Specific Access and the others have Inheritied access. There are two shared sections. Objects 3.2.2, 3.2.2.1, 3.2.2.2 are in one section and 3.2, 3.2.1, and 3.2.3 are in the other. Notice that 3.2.2 is not in 3.2's shared section since 3.2.2 has specific access.

If you lock any object in a section you unlock all other objects in that section.

Now if you select 3.2.2 and unlock it you have NOT unlocked 3.2. If you create an object 'after' 3.2.2 then it would actually be created in 3.2's shared section (becoming the new 3.2.3), which is still locked.

- Louie
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.