![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: post open project trigger Topic Summary: Created On: 10-May-2004 22:25 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi, There,
I'm trying to create a post open project trigger which will check the DOORS build number and closes the project if the build number is smaller than my latest build number. But It doesn't do anything. Here is my trigger: Trigger t = trigger("openDoors", project->"Xyan Test", post, open, 10, "#include <//pet-filer01b/projects/otbuprojects/DOORS/scripts/TT/Lib/Triggers/doorsOpen.dxl>") Here is the content of <//pet-filer01b/projects/otbuprojects/DOORS/scripts/TT/Lib/Triggers/doorsOpen.dxl>: int latestBuildNumber = 70215 int curVersion = intOf(doorsInfo(infoBuildNumber)) ack("cur is " curVersion ", latest is " latestBuildNumber ".") if (curVersion < latestBuildNumber) { ack("You don't have the latest patches installed. Your build number is " curVersion " while the latest is " latestBuildNumber ". Please check with doors-system-admin to get your newest patch!") closeProject() } Thanks! Catherine |
|
![]() |
|
![]() |
|
There are no triggers events associated with Projects. The documentation says this but also has residual artifacts from DOORS v4 that DID have such triggers. Project "level" triggers mean where the trigger is stored and thus to which they apply.
Yup, its confusing. That's where I come in... Your code defines a post-open-module trigger that applies to modules in the "Xyan Test" project. Try opening a module and notice the trigger fires. Perhaps you want a pre-open module trigger. Instead of "closeProject" you could insert a "set(trigPreConFail)" command that would prevent the module from opening. Perhaps you could have a mod = current command and close the module if someone opens it Edit or Share (if (isShare(mod) or isEdit(mod)). I'd also be tempted to modify you ack message, suggesting that access to THIS project requires the patch. And I'd includes the batch number associated with your build 70215. Curiosity has me. Why does this project require the patch? - Louie IIRC, the "closeProject" command only removes your lock from it; not actually closing it in the DOORS Explorer. |
|
![]() |
|
![]() |
|
Thanks a lot, Louie!
set(trigPreConFail) is exactly what I need. We want to force install the new patch because Telelogic told us that having users on different patches could cause data corruption. Thanks again! Catherine |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
post open project trigger
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.