I have a subsequence that I point the user to when they are asked to isolate a board failure. To provide them with some flexibility, I have a popup that gives them a number of opetions (see attachment). I have a test procedure that instructs them to select/run individual steps (i.e. '1' or '3' in the png). The flow control (denoted by '2') is noise they don't really need to worry about, and may/will cause confusion (and possibly problems for me if they select them accidentally). Is there a way to hide these Flow Control steps during runtime so that the user only sees '1' and '2' (and the other similar 'valid' selections?
Solved! Go to Solution.
I thought of that, but once I move the select statement (and the associated case statements) into a subsequence file, I lose scope, and the Select and Goto statements no longer have visibility into the labels found in the parent subsequence (i.e. MR_RPack_R55).
You could use a subsequence to evaluate the result of the Message Popup ButtonHit,
By passing in the Result.ButtonHit and the subsequence shall return the unique step id for the appropriate step -
The subsequence would use the select/case structure to set Locals.NextStepUniqueId:
The top-level sequence could then call the returned step id as a post-action to the subsequence:
If there wasn't an explicit need to have the logic as flow control, then I'd be tempted to compact it all into the post-action of the Message Popup;
By setting the Message Popup Post Action to Goto Step, <Specify by Expression>, Use Custom Condition (TRUE):
And using the following Expression:
Step.Result.ButtonHit == 1 ? RunState.Sequence.Main["MR_RPack_R55"].UniqueStepId : Step.Result.ButtonHit == 2 ? RunState.Sequence.Main["End_PCI_Isolation"].UniqueStepId : Step.Result.ButtonHit == 3 ? RunState.Sequence.Main["MR_R103"].UniqueStepId : Step.Result.ButtonHit == 4 ? RunState.Sequence.Main["PCI_Intf_PT"].UniqueStepId : ""
This should goto the appropriate step following the Message Popup.
I hope this helps.