Platform and CAD Support Updates
aPriori 2025 R1 SP3 adds support for several recently released CAD versions, as described below. For a complete and up-to-date listing of all versions of supported CAD systems, operating systems, database platforms, and graphics cards and drivers, consult the 2025 R1 SP3 versions of the aPriori On-Premise System Requirements and Cloud System Requirements.
If your company is planning to upgrade to a CAD, database, or operating system version that is NOT listed in the System Requirements, contact aPriori Customer Support.
- Updates to Supported CAD Systems and Versions
- Pending De-Support of MySQL 8.0
- Export to STEP AP242 Format from Analyze in aPriori Plug-ins
- Plug-in Workflow Improvements
Updates to Supported CAD Systems and Versions
aPriori 2025 R1 SP3 adds support for several recently released CAD system versions. aPriori no longer officially supports several older versions.
aPriori 2025 R1 SP3 adds support for the following CAD system versions, including providing compatible Analyze in aPriori plugins (formerly called “Cost-in-aPriori” plug-ins):
-
Creo 12
-
NX 2506
-
Inventor 2026
aPriori 2025 R1 SP3 drops official support for the CAD system versions listed below. aPriori will no longer regularly test these older versions, and will not address issues that occur only in these older versions. The Analyze in aPriori plugins may not function properly for these older versions.
-
Creo 8
-
NX 2212 series
-
Inventor 2022
Note that even when aPriori no longer officially supports an older CAD version, aPriori generally will continue to be able to analyze CAD files saved in that version, via the Open CAD File option in aP Pro and the Import CAD File option in aP Design. However, aPriori reserves the right not to investigate or address issues that occur only in these older, unsupported versions.
Pending De-Support of MySQL 8.0
aPriori 2025 R1 SP3 is the last release of aPriori to support use of the MySQL 8.0 database version. The next release of aPriori will support MySQL 8.4 instead.
MySQL 8.0 will reach end of life in April 2026. Oracle no longer will provide security patches, bug fixes, or technical support after this date. Customers using MySQL as part of an on-premise deployment of aPriori are advised to plan an upgrade to MySQL 8.4 in conjunction with moving to aP Pro 2026 R1 (available in March 2026).
Export to STEP AP242 Format from Analyze in aPriori Plug-ins
All Analyze in aPriori plug-ins except the Creo plug-in now can export to STEP AP242 format, as well as other STEP formats and the native CAD format.
The SolidWorks plug-in co-released with aPriori 2025 R1 SP3 supports export to STEP AP242. The NX and Inventor plug-ins provided support for STEP AP242 as of the aPriori 2025 R1 SP2 release. The plug-ins for CATIA and Solid Edge also support export to STEP242, as the plug-in respects the user preferences for STEP export set in the CAD application.
For the SolidWorks plug-in set the STEP export standard option to AP242 in the plug-in Options dialog, as shown below:
Note that the user must have an appropriate MBD license for STEP AP242 support. If the plug-in options specify STEP AP242 but the user does not have the appropriate CAD license, the plug-in will warn the user and export to a licensed STEP format instead (such AP203 or AP214).
For more information about installing and configuring Analyze in aPriori plug-ins, please see the relevant Analyze in aPriori Plug-in Installation Guide.
Plug-in Workflow Improvements
The Analyze in aPriori plug-ins now allow you to set the company code during the plug-in installation, so end users do not have to remember it during login. Additionally, the dedicated browser which is launched by the plug-ins now supports multiple tabs. Users can more easily keep track of different components and scenarios they are analyzing in aP Design, as each now is displayed in a separate tab of the same browser window instead of having multiple open browser windows.
The aPriori Dedicated Browser install wizard now has the option to set the customer code, so end users do not have to remember this code during login:
If the code is entered incorrectly during installation, it can be updated manually in the aPrioriBrowser.properties file which is located in the users AppData directory (…\AppData\Local\aPriori).
Now when a user is working with multiple scenarios in aPriori, the browser allows each scenario to exist in its own named tab, as shown below. This is particularly useful when working with assemblies or trying to compare different CAD options for a part.


