Hi Mal,
In general, in TestStand you use a step type that can use the Sequence Adapter in order to call a sequence (named subsequence in this context). The MainSequence is called from within the ProcessModel execution entry-points ('Test UUTs' and 'Single Pass' sequences in the TestStandModel.seq) when you launch the execution from "Execute->Test UUTs" or "Execute->Single Pass" menu or directly by the engine when you start an Interactive execution by selecting "Execute->Run MainSequence" menu option.
In the first case, after the sequence call step executes, the Sequence Adapter can set the step status. So, finally the property that contains the status of Main Sequence is a subproperty of the SequenceCall step that in the ProcessModel execution entry-points is named "MainSeque
nce Callback". The lookup string for this property depends from where you want to access it. For example :
a) if it's from a step you add as part of the Execution entry-points customization, then the lookup string for the property should be "RunState.Sequence.Main["MainSequence Callback"].Result.Status"
b) if it's from a step in the MainSequence, then the lookup string for the property should be "RunState.Caller.RunState.Sequence.Main["MainSequence Callback"].Result.Status" but special consideration should be taken if the MainSequence is run in Interactive mode, since the "RunState.Caller" property doesn't exist in this case.
In the second case the sequence status isn't available (see above).
Regards,
Silvius
Silvius Iancu
