If you made changes to callback definitions in TestStand 2010 or earlier, you can use the following techniques for migrating custom code:

  • Modifying the callbacks in the process model file itself
    • Use this approach when you want to continue to use the default process model functionality.
    • You will have to migrate changes when you upgrade TestStand in the future.
  • Implementing the custom callback in a process model plug-in add-on
    • Use this approach when you made complex callback modifications or if you completely rewrote the callbacks.
    • You can easily migrate changes to future versions of TestStand because you do not make any changes to the process model.

The following table summarizes the recommended approach for migrating changes to callbacks.

Callback Name Recommendation
PreUUT

PostUUT

PreBatch

PostBatch

 If you created a custom dialog box, migrate the callback code to a custom process model plug-in add-on. Add a Sequence Call step in the correct process model plug-in sequence to call the new callback. To suppress the default callback code in the TestStand 2012 or later process model, set the element that corresponds to the callback in the Locals.ModelPluginConfiguration.RuntimeVariables.ModelDialogsEnabled container to False in the Begin sequence of the process model plug-in. You can migrate changes to a modified version of the default dialog box. If you are using the default dialog box, you can integrate changes with the TestStand 2012 or later process model files.
PreUUTLoop

PostUUTLoop

PreBatchLoop

PostBatchLoop

ProcessSetup

ProcessCleanup

 Because these callbacks are empty by default, migrate the callback code to a custom process model plug-in. Add a Sequence Call step in the correct process model plug-in sequence to call the new callback.
ModelOptions Because the ModelOptions callback must have access to the process model properties, migrate changes to this callback to the ModelOptions callback in the ModelSupport.seq sequence file.
Custom Callbacks Migrate the custom code to a custom process model plug-in and add a Sequence Call step in the correct process model plug-in sequence to call the new callback. Create an empty definition for the custom callback in the process model file so that the client sequence file recognizes the custom callback at edit time, meaning that the callback icon appears green in the Sequences pane and is present in the Sequence File Callbacks dialog box.