01-04-2010 10:49 AM
Solved! Go to Solution.
01-04-2010 09:16 PM
Hi,
If you'd like to maintain the engine callbacks in one place <Process Model> instead of many places <Called Sequence File>, then use ProcessModelPostStep and ProcessModelPostStepRuntimeError in your process model sequence file. These will be fired after each step in the client sequence. TS Reference Manual Table 10-1, "After the engine executes each step in any client
sequence file the process model calls and each step in any resulting subsequence calls."
The equivalent of this would be to use SequenceFilePostStep and the SequenceFilePostStepRuntimeError callbacks in all of your client sequence files. BTW if you wanted a comprehensive error handler you could use ProcessModelPostStepRuntimeError and SequenceFilePostStepRuntimeError in your process model. This would cover all the steps in the process model sequences, and in the client test sequences.
I think engine callbacks are enabled and disabled, as opposed to overridden.
cc
01-05-2010 01:43 PM - edited 01-05-2010 01:44 PM
Thank you dowNow,
I've followed the engine callbacks description from the TestStand I Course Manual. It says: " You can override engine callbacks for a specific sequence file or override them within a process model to affect any sequence file that uses that model." No more details there.
So, while at the second look it looks obvious that "SequenceFile" prefix is for sequence files and "ProcessModel" prefix is for process models, this idea did not come to my mind. I was fixed on the idea that override is always use the same name for a callback. Thanks again.