10-30-2018 02:24 PM
I am trying to write a Configuration Entry point that will operate on the SequenceFile that is currently loaded. Let's say for now that I simply want to query the path of the SeuqenceFile.
I see that there is a "Entry Point Ignores Client File" checkbox on the sequence properties of my new Configuration Entry Point... this implies to me that the Entry Point should be able to access the Client SequenceFile somehow... but how?
I have tried RunState.ProcessModelClient.Path, and it's empty.
Any other ideas?
10-30-2018 04:58 PM
RunState.InitialSelection.SelectedFile.Path should do it.
I think that flag you are referring to has to do with loading modules or not for the client. This is from the help:
Entry Point Ignores Client File—Prevents the sequence from using the client file. This option prevents TestStand from preloading the client sequence file when you run the entry point, even if the client sequence file is set to preload when execution begins. For example, the Configure Result Processing entry point uses this option so the Configure»Result Processing command is available for you to use even when TestStand is unable to preload the modules in the active sequence file.
Note If you are using the equivalent legacy TestStand 2010 process models, the Configure Report Options entry point uses this option so the Configure»Report Options command is available for you to use even when TestStand is unable to preload the modules in the active sequence file. |
10-30-2018 05:00 PM
BTW- I should note that a sequence file only becomes the client file when it was the selected file that kicked off the entry point.
11-07-2018 10:19 AM
I will try it and let you know, thanks!