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: 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
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.
 25-Apr-2005 16:32
User is offline View Users Profile Print this message


Ed Roland

Posts: 12
Joined: 13-Apr-2005

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!!
Report this to a Moderator Report this to a Moderator
 25-Apr-2005 17:15
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

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