Important similarities and differences exist in the way you use process model callbacks in TestStand 2012 or later and in previous versions of TestStand.

Overriding Process Model Callbacks

To customize result processing for a specific type of UUT, you typically override process model callbacks in a client sequence file. This technique remains the same in TestStand 2012 or later. You can override callbacks in the same manner as in earlier versions of TestStand. As a result of this similarity, you can seamlessly migrate client sequence files that override process model callbacks from earlier versions of TestStand to TestStand 2012 or later.

Migrating Modifications to Built-in Process Model Callback Definitions

Although the process of overriding callbacks has not changed, TestStand 2012 or later changes the location where it defines the callbacks. TestStand 2012 or later defines result processing callbacks in the process model and in the result processing model plug-in, but only the process model plug-in implementation contains any steps. The callback definition in the process model exists so that the client sequence file recognizes the 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.

Note The term definition describes only callback sequences that contain the steps to implement the callback code because this is the only callback definition you should modify.

If you modified the default functionality of a results processing callback by directly modifying the callback sequence in the process model, you must copy the modifications into the callback sequence in the corresponding process model plug-in sequence file. For example, if you added steps to the TestReport callback sequence in SequentialModel.seq in TestStand 2010 or earlier, you must migrate these changes to the TestReport callback sequence in the NI_ReportGenerator.seq result processing model plug-in.

The following table shows where TestStand 2012 or later defines the TestStand 2010 SP1 or earlier results processing callback sequences:

Callback Sequence Location of Callback Definition in TestStand 2012 or Later
TestReport

BatchReport

ModifyReportHeader

ModifyReportEntry

ModifyReportFooter

ReportOptions

ModifyBatchReportHeader

ModifyBatchReportEntry

ModifyBatchReportFooter

 NI_ReportGenerator.seq (report generation result processing model plug-in)
DatabaseOptions

LogToDatabase

 NI_DatabaseLogger.seq (database logging result processing model plug-in)

Migrating Custom Result Processing Callbacks

If you created custom result processing callbacks in TestStand 2010 or earlier, you must migrate these callbacks and any steps that call the callbacks to the process model plug-in sequence file. To invoke the callback, create a Sequence Call step in the appropriate Model Plugin entry point. For example, if you created a custom callback to log additional information to the report immediately after TestStand generates the report, move this callback definition from the process model to the NI_ReportGenerator process model plug-in, then call the callback sequence in the Model Plugin — UUT Done plug-in entry point. Maintain a blank definition of the callback in the process model itself so client sequence file developers know that the callback is available to override.