![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Possible to change the value of NO ACCESS Attribute!! Topic Summary: Is it a bug?? Created On: 2-Jun-2006 14:23 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: There are two access rights for an attribute: one access right for the attribute definition and one for setting the attribute value. I have a feeling that your excamples are mixing these two. | |
![]() |
|
Hello All,
I found an interesting thing... Lets consider the following scenario: 1. Open any test formal module. 2. Change the access right to "None" of a user defined text attribute for any user other than the current user. 3. Open a DOORS session with that user name who has None access to a particular text attribute of a module. 4. Run the following code: Object o = current o."Your Text Attribute Name" = "Hello World" I suppose we can not modify "none access" attribute (if I open the attribute GUI, I can see that it is mentioned as <Access denied> ) from dxl. Is it a bug? Did any one notice it before? I tried the following as well: AttrDef ad = find(current Module, "Paragraph Style") if(!null ad) { /* */print "Attribute Exists\n" } else { /* */print "Attribute Not Exists\n" } //I got here "Attribute Not Exists" message as I have none access to this attribute. Object o = current if(canWrite(o."Paragraph Style")) { /* */print "Can write\n" /* */o."Paragraph Style" = "Hello World" } else { /* */print "Can not write\n" } //I got here "Can write" message and the value is updated. To check it I had to open the module with another user name. I am using DOORS 7.1. ** This exists also for DOORS 8.0. Try this, you can create text attribute and include this attribute to one view and save it. Then change the access right of this attribute to NONE for some users. Then login to another DOORS session with any of those users name and try to open that module and view... you still can see the attribute even you can modify the value which is not correct (as the previous user set it none access to this user.) Greetings, Rony ================= Iftakher Uddin (Rony) HOOD Group Edited: 2-Jun-2006 at 15:58 by Iftakher Uddin |
|
![]() |
|
![]() |
|
There are two access rights for an attribute: one access right for the attribute definition and one for setting the attribute value. I have a feeling that your excamples are mixing these two.
------------------------- Pekka.Makinen@softqa.fi SoftQA Oy -http://www.softqa.fi/ |
|
![]() |
|
![]() |
|
Mäkinen is correct. You can protect the 'Def'inition of an attribute (e.g. prevent someone from changing the default value or from deleting the attribute altogether) and you can also protect the 'Val'ues of an attribute (e.g. prevent someone from setting it to "Passed").
In DXL you'll see some odd looking functions, 'inherited', 'inheritiedDef', 'inheritedVal' to support these notions. - Louie |
|
![]() |
|
![]() |
|
I got the point...
Thank you both. - Rony |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.