Migrating Custom Process Model Components
- Updated2025-07-23
- 1 minute(s) read
In addition to modifying the existing components of the process model, you might have added completely new functionality to the process models. When migrating these types of customizations, consider creating a new process model plug-in to implement the same functionality. If it is possible to implement custom components as a process model plug-in, NI recommends you do so because it can greatly simplify migration of custom components in versions of TestStand later than 2012.
If you want to manage the configuration of the process model plug-in using a method other than the existing Results Processing dialog box, change the process model plug-in category. The Result Processing dialog box displays only process model plug-ins with a category (ModelPlugin.CategorySpecific.Name) set to ResultProcessor.
If you want the new process model plug-in to always execute independently of any configuration settings, configure the model plug-in as a plug-in add-on by storing the process model plug-in in the <TestStand Public>\Components\Models\ModelPlugins\Addons directory. Refer to the Dynamic Client Sequence File example in TestStand 2012 or later for an example of using a process model add-on.