API Changelog

Before upgrading to the latest version, review what's new and what has changed since the last version. This page provides a quick overview of the most significant enhancements and deprecations since the previous versions.

When you're ready to upgrade, first install the latest version of Synthesis on your computer. The Synthesis API object library file will be located in the folder where the Synthesis application is installed. You can then update the library reference of your custom applications to point to the file in that location. For VBA applications, use SynthesisAPI.tlb. For .NET applications, use SynthesisAPI.dll

For a complete list of all new classes and enumerations in the object library, see New Classes and Enumerations.

For a complete list of all new methods and properties in existing objects, see New Members and Constants.

For a complete list of all deprecations, see Deprecated and Removed Members.

What's New in Synthesis API Version 10.0
Improved flexibility
 * We've added all new classes and methods for accessing FMEA and related data from Xfmea, RCM++ and RBI.
 * We've added several new methods in the Repository class to provide more options for manipulating Synthesis resources. The most significant of these is the ability to get a single resource from a Synthesis repository. You are no longer limited to using arrays to access a particular resource item.

New features incorporated
 * We've added new properties and enumerations in the cAction class to take advantage of the expanded action-tracking capabilities introduced in the latest version of the Synthesis platform. This includes action properties relevant to the project planner and Xfmea/RCM++/RBI test plans.
 * For all resource objects (e.g., cModel, cURD, cCrew, etc.), we've added a new set of properties for accessing the Synthesis identifiers fields in the platform.

Deprecations
 * The Repository class has been restructured to organize its growing number of members. All of its members are now organized into fields named after the object type they apply to. For example, the  method, which returns a cModel object, has been renamed to  ; similarly, the   method has been renamed to , etc. The previous versions of the methods still exist so your code is not broken, but they are deprecated and may be removed in future versions of the API.