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: Limiting access to attributes
Topic Summary:
Created On: 5-Dec-2007 18:19
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.
Answer This question was answered by Eric Piallat, on Wednesday, December 19, 2007 9:18 AM

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!\"}")
 5-Dec-2007 18:19
User is offline View Users Profile Print this message


Kevin Tarling

Posts: 9
Joined: 8-Nov-2006

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
Report this to a Moderator Report this to a Moderator
 6-Dec-2007 09:11
User is offline View Users Profile Print this message


Robert Swan

Posts: 86
Joined: 14-Apr-2005

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.
Report this to a Moderator Report this to a Moderator
 6-Dec-2007 09:48
User is offline View Users Profile Print this message


Eric Piallat

Posts: 4
Joined: 27-Nov-2007

Answer 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!\"}")
Report this to a Moderator Report this to a Moderator
 19-Dec-2007 09:18
User is offline View Users Profile Print this message


Kevin Tarling

Posts: 9
Joined: 8-Nov-2006

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.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 2 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 2 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.