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: NEED DXL Help
Topic Summary: Want field to change automatically if object changes.
Created On: 19-Jan-2007 16:49
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.
 19-Jan-2007 16:49
User is offline View Users Profile Print this message


Tracy Monteith

Posts: 33
Joined: 21-Dec-2005

DXL Beginner.   I have a boolean Attribute called "REVIEW_READY".  We are using it determine if the object / or row is ready to be sent ot the customer.    Default value is false.  As we review internally we set rows to true. 


If we change anything in the object we want the field to revert automatically to false. 

We think DXL is how we accomplish this??

  Beginner Level - -  Step by Step please?
Report this to a Moderator Report this to a Moderator
 19-Jan-2007 18:34
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Let me see... You want an attribute to remain 'true' so long as changing it to true was the last thing changed; if anything else in the object changed you want this attribute value to be false.

[1] You could have a pre-save-attribute trigger that sets the value of a specific attribute to false, unless you are triggering on that attribute.
[2] You could have a pre-close-module trigger that reviews changes during this sesssion, setting the obj-attr to false as appropriate.
[3] You schedule a nightly script that basically does [2] for all modules.

However, Triggers are a nightmare even for the best of us, and are definately not for DXL newbees. Scheduling is tricky business. Lets go a different route:

You have a boolean attribute that records History and everybody knows that they should not edit its value, except the review team. You write a background attribute DXL whose job it is to plow through the History of the object. If the last History changes anything except that first attribute, then set that first attribute's value to false. If the last History was setting the attribute value to true, then this attrDxl can verify that the Author was authorzied to do so and take steps if not; typically setting it to to false.

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