![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: How to block users to edit an object? Topic Summary: Created On: 25-Apr-2005 16:32 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I have a DXL script which allows users to edit a specific object in a current module, but I need to block users to edit that object directly. Can you please show me how to block users editing a specific object and force them use the DXL script?
For example, an object is read only, but is editable by my DXL script. Or when an user edits that specific object, it will call my DXL script. Thanks in advance!! |
|
![]() |
|
![]() |
|
Good luck.
I'd write an Pre-Attribute-Save trigger that fires whenever this attribute is being "saved", meaning someone is trying to modifyit. This Trigger would reject the save (set(trigPreConFail)) if the value of some other attribute is false, and allow the save (set(trigPreConPass)) if its true. That boolean attribute "Allow Obj Mod" should probably not have History etc defined. Your DXL script with a dialog would set the value of that other attribute to true before making a change, and then set it false. Thus, when the script modifies the attribute the trigger allows it. The Trigger can understand the "current Trigger" via Trigger trg = currrent; the "current object" via "Object oCurr = current"; and the Attribute being saved is "AttrDef ad = attrdef(trig)" (the manual is incorrect on that). The Trigger would need to be sensitive to your Policies; specifically having some list of Attributes that it will protect figuring to allow all edits to all the other attributes. This way, you can define the Trigger to be a module based one. Like I said, good luck. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
How to block users to edit an object?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.