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: Triggers for Dummies?
Topic Summary: Does anyone have some good documentation on Triggers?
Created On: 10-Jun-2005 14:24
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.
 10-Jun-2005 14:24
User is offline View Users Profile Print this message


Brant Stoner

Posts: 30
Joined: 2-Aug-2004

Hello all, I'm attempting to learn about Triggers in DOORS. The documentation in the DXL help seems fairly cryptic to me....does anyone have some good introductory material on Triggers?

I know this is a pretty general question, but any starting points would be helpful...thanks!
Report this to a Moderator Report this to a Moderator
 30-Jun-2005 20:20
User is offline View Users Profile Print this message


Ewen Miller

Posts: 99
Joined: 20-Nov-2002

Check out the DXL manual which is downloadable from the DOORS support area of the website.


Ewen Miller
Report this to a Moderator Report this to a Moderator
 6-Jul-2005 18:19
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

There is no Triggers for Dummies.

There are two DXLs of interest for each trigger [1] the code of the trigger itself. This code gets executed when the trigger is Triggered [2] the code that defines and sets up the trigger. This code should also be written to have an option to remove the trigger, where the "delete" and the "trigger" commands match up.

[1] Can be in a separate file and the trigger code #includes it. That tricky for multiple users since all have to have access to the file. You can also define a "string TriggerCode = ..." variable that houses the trigger code itself. Slashes and quotes need to be preceeded with a slash. You could use the "eval_" function to test the trigger code before you install it as a trigger. You could also have the code in a separate file on you client, and the defining program opens the file and reads it into a variable.

Once the trigger code works you'll have to decide the Event and the Scope which together decide when the trigger Fires. You are going to have to practice to figure out all that. I'd have a dxl that simply does this "infoBox(\"Hello from Trigger MyTrigger\")'

There are several commands that are accessible only from INSIDE a trigger. You are also going to have to practice which ones. Often the trigger will need to "Trigger tCurr = current" to get a handle on its own Trigger. I found out that the "attrDef" command returns the name of the Attribute in question when dealing with Attribute Save Triggers.

Be sure to do a lot of error handling and gracefully deal with them. Deal with usually means ignore and abort.

Triggers are bad enough; triggers that modify stuff is a nightmare. Avoid them untill you are VERY confident in your DXL and trigger abilities.

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