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: Weird Behavior of Triggers
Topic Summary:
Created On: 22-Oct-2007 04:12
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.
 22-Oct-2007 04:12
User is offline View Users Profile Print this message


Rhea Castillo

Posts: 11
Joined: 7-May-2007

Hi all:

enlighten me on this one.

I have created two triggers where the scripts are mapped from another machine.

The thing is one of the triggers is working fine but the other is not.

However, when i changed the script path of the trigger thats not working to point to the local machine's script directory, it's working fine. both scripts mapped from the other machine and the local machine is the same. Why/How is this so?


Report this to a Moderator Report this to a Moderator
 22-Oct-2007 16:54
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

You may need to supply specifics.

Sounds like you are using an "#include" statement as the DXL when creating the Trigger. Understand that means that when the trigger runs, it evaluates the #include and retrieves the file. That means [1] the user who is doing the event that activates the trigger must have access to that file on the network [2] the path to the file must be useable by that user; i.e. if you've mapped a network drive and perhaps #include <m:\Path\File.dxl> then the other users must likewise have mapped the M drive to that server location.

When creating the trigger, I'd be tempted to read the network file and then use that in the Trigger instead of #include:
Instead of this:
.... Trigger trg = trigger(bla,bla,bla, "#include <//MyServer/MyPath/MyFile.dxl")
Do This:
.... Trigger trg = trigger(bla,bla,bla, (readFile("//MyServer/MyPath/MyFile.dxl")))

Doing that, the trigger works for everyone and they don't need access to the network file.

- Louie
Report this to a Moderator Report this to a Moderator
 23-Oct-2007 04:16
User is offline View Users Profile Print this message


Rhea Castillo

Posts: 11
Joined: 7-May-2007

I'm using readFile instead of #include but still getting this weird behavior

The thing is when i deployed the two triggers, namely:
updateRelease
updateFeature

Only updateFeature is working but the other does not. It does not display any errors also.  If i manually execute the script for the updateRelease trigger, it performs its actions..

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.