This section contains the change log and information about known issues, breaking changes, API changes and the data warehouse for v2022.3.
2022.3.8.0 is a HotFix release that contains one bug fix.
There are no additional breaking changes, breaking API changes or known issues for this release.
The change log for 2022.3.8.0. contains detailed information about the bug fix that was included in this release. A downloadable copy of the Bug Fixes Change Log is available below which includes the bug fixes for all of the 2022.3 builds up to 2022.3.8.0.
2022.3.7.0 is a HotFix release that contains four bug fixes and one enhancement.
There are no new breaking changes, additional breaking API changes or additional known issues for this release.
The change log for 2022.3.7.0. contains a detailed list of the enhancements and bug fixes which have been included in this release. A downloadable copy of the New Features & Enhancements Change Log and the Bug Fixes Change Log are available below.
2022.3.6.0 is a production release that contains a number of enhancements and bug fixes.
The change log for 2022.3.6.0. contains a detailed list of the enhancements and bug fixes which have been included in this release. A downloadable copy of the New Features & Enhancements Change Log and the Bug Fixes Change Log are available below.
Below is a document with details of all API Changes in 2022.3 including breaking API changes.
Below is a copy of the breaking changes document. This contains details for all breaking changes within the Data Warehouse and the Enate APIs.
This document lists all the validation codes for the 2022.3 release.
Recommendation for best use of API breaking changes documentation is as follows:
Read through the breaking changes information for APIs.
Upon finding reference to an API which you currently use and which has changed, go to your Swagger environment for the quickest way to view the overall impact and new API content definition. Your Swagger environment should always be your go-to place for the definitive explanation of the current API structure. See the Swagger explanation in our main Help section for more info.