API Changelog

The latest version of the Synthesis API is Version 10.

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 major points to consider before upgrading. Detailed lists are provided in the following pages:


 * For a complete list of new classes and enumerations, see New Classes and Enumerations.
 * For a complete list of new methods, properties, events and constants, see New Members and Constants.
 * For a complete list of deprecated, changed or removed members, see Deprecated and Removed Members.

When you're ready to upgrade, first install any Version 10 Synthesis application on your computer. The 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

What's New in Synthesis API Version 10
Here’s a quick overview of the most significant enhancements and deprecations in the latest version.

Improved flexibility

 * 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.
 * We've created all new classes and methods for accessing FMEA and related data from Xfmea/RCM++/RBI.

New features incorporated

 * New properties and enumerations in the cAction class take advantage of the expanded action-tracking capability in the latest version of the platform.
 * For all resource objects (e.g., cModel, cURD, cCrew, etc.), a new set of properties were added for accessing the improved 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.