![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Limiting access to attributes Topic Summary: Created On: 5-Dec-2007 18:19 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: You may try something like this: trigger("Prevent_Modify", module->object->attribute, pre, modify, 5, "if (notHappy) then {set trigPreConFail ; ack \"Can't change it!\"}") Of course, you have to replace notHappy by your actual checking. It does not prevent *trying* to modify, but undo unwanted changes. (Who will be lost !) You may prevent modifying specifics attributes with: trigger("Prevent_Modify_OT", module->object->attribute->"Object Text", pre, modify, 5, "if (1 == 1) {set trigPreConFail ; ack \"Can't change it!\"}") | |
![]() |
|
Does anyone have any ideas on a method of preventing a set of users from editing an attribute without locking out the access rights of other attributes in the object and other objects in the module. Would have liked to use a trigger but cannot find a way of getting the attribute about to be editted, without already editting it. Or can you roll back an edit?
Thought was to: Check flag for object ( = limited attribute access) Check user check attribute ( is now limited access) prevent change!!!! if user not allowed A number of people are accessing the module with the data within the module at difference levels of maturity Triggers have been a pain to get right. The open trigger not giving the attribute details and the attribute edit trigger not preventing change! I might have got it all wrong Any thoughts, Thanks Kevin Tarling |
|
![]() |
|
![]() |
|
To prevent users changing customer provided text (contractually agreed) I used the setVal function to users write/edit rights on attributes. This still allows us to have user editable attributes (responses, comments etc) in the same module.
setVal was also used to amend the 'edit attribute' rights, but do remember to keep one person with modify rights on attribute editing, usually someone who is not a regular DOORS user. This does affect all objects. |
|
![]() |
|
![]() |
|
You may try something like this:
trigger("Prevent_Modify", module->object->attribute, pre, modify, 5, "if (notHappy) then {set trigPreConFail ; ack \"Can't change it!\"}") Of course, you have to replace notHappy by your actual checking. It does not prevent *trying* to modify, but undo unwanted changes. (Who will be lost !) You may prevent modifying specifics attributes with: trigger("Prevent_Modify_OT", module->object->attribute->"Object Text", pre, modify, 5, "if (1 == 1) {set trigPreConFail ; ack \"Can't change it!\"}") |
|
![]() |
|
![]() |
|
Hi Louise, Eric and Robert. Thanks for the help. The bit I missed was the set "trigPreConFail" conditions. I now have module attributes that define a list of user groups and a list of attributes. Then, when a flag is set for each object, that list of attributes is locked out to all users except those listed. This allows us to progressively mature the contents of a module without locking everything out.
|
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Limiting access to attributes
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.