![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Weird Behavior of Triggers Topic Summary: Created On: 22-Oct-2007 04:12 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
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? |
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
I'm using readFile instead of #include but still getting this weird behavior |
|
![]() |
Telelogic DOORS
» General Discussion
»
Weird Behavior of Triggers
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.