Update runtime copy ALONE of a step within another Sequence

[Priyadarsini]

Hi all,

I have a custom SequenceCall step. The pre-step of this custom step needs to modify some properties of steps (in runtime copy only) within the Sequence called by this step. So I first get the reference to the called Sequence using the below expression. And then I obtain the reference to all steps within that Sequence. The problem is that this modifies the properties of the edit-time copy also which is not intended. Please suggest how to modify a property of a step within another Sequence and in RUNTIME ONLY.

RunState.SequenceFile.GetSequenceByName(Step.Module.AsSequenceCallModule.SeqName)

Thanks,

Priyadarsini S

[RoxtheFox]

Hey Priyadarsini,

Can you explain what you are trying to accomplish? It does not look like what you are asking for is possible. We also don't recommend coupling your custom step type with a client sequence file. 

[inniwhoni · Accepted solution]

Roxana is correct, built-in step properties are shared between edit and runtime. From this TestStand help document:

TestStand shares built-in properties of steps and sequences at run time. For these shared properties, TestStand does not create a unique run-time copy but instead references the edit-time copy. Any changes to the run-time reference of these built-in properties edits the original Step or Sequence object in the sequence file.

If you want the changes to not persist after runtime, you can set the desired property in the Pre-expression and then set it back in the post-expression, assuming that your sequence call is not running in a new thread/execution.

Best,

Kevin F.

Product Support Engineer | Automated Test Software

National Instruments

[Priyadarsini]

Hi Roxana, Kevin,

Sure, I understood that we can access the runtime copy of the steps within the current Sequence only. We did consider the pre & post expressions but had another workaround for our need.

Thanks,

Priyadarsini S