241.0.0

Release notes for version 241.0.0
Platform API version: 9841

Changes in this version

• Major changes: 0
• Minor changes: 0
• Point changes: 0

For the full changelog, read the releaseNotes.md file in the repo.

240.0.0

Release notes for version 240.0.0
Platform API version: 9841

Changes in this version

• Major changes: 9
• Minor changes: 195
• Point changes: 12

For the full changelog, read the releaseNotes.md file in the repo.

239.0.0

Release notes for version 239.0.0
Platform API version: 9791

Changes in this version

• Major changes: 1
• Minor changes: 10
• Point changes: 0

For the full changelog, read the releaseNotes.md file in the repo.

238.0.0

Release notes for version 238.0.0
Platform API version: 9782

Release Notes

This release implements a change in the computePKCECodeChallenge method, used in the loginPKCEGrant method and flow. Until now, the SDK source code was making use of Buffer.from method to compute the PKCE Code Challenge.

When building the web-cjs version of the library, we injected polyfills to manage methods, like the Buffer.from, which are not supported in browser based javascript. The loginPKCEGrant method was therefore fully functionnal without making additional configuration in a javascript project when using the web-cjs version of the Javascript SDK.

For the node version of the library, used for a web client oriented project, no specific action was taken. In the past, bundlers (like webpack) used to inject these polyfills by default, allowing the node version library to also be functional in a project using a web framework (like vite, react, ...) and a bundler. These bundlers (like webpack) have ceased to import polyfills by default and they must be specifically declared in the web project configuration.

To avoid this additional configuration when using the node version of the library in a web client oriented project, the computePKCECodeChallenge method has been updated to use native Web API methods instead of Buffer.from. This change also applies to the web-cjs version of the library. Therefore, no specific bundler configuration should be necessary to manage the loginPKCEGrant method and flow.

Changes in this version

• Major changes: 0
• Minor changes: 0
• Point changes: 0

For the full changelog, read the releaseNotes.md file in the repo.

237.0.0

Release notes for version 237.0.0
Platform API version: 9782

Changes in this version

• Major changes: 3
• Minor changes: 76
• Point changes: 0

For the full changelog, read the releaseNotes.md file in the repo.

236.0.0

Release notes for version 236.0.0
Platform API version: 9766

Changes in this version

• Major changes: 5
• Minor changes: 46
• Point changes: 1

For the full changelog, read the releaseNotes.md file in the repo.

235.0.0

Release notes for version 235.0.0
Platform API version: 9727

Changes in this version

• Major changes: 17
• Minor changes: 72
• Point changes: 1

For the full changelog, read the releaseNotes.md file in the repo.

234.0.0

Release notes for version 234.0.0
Platform API version: 9685

Changes in this version

• Major changes: 55
• Minor changes: 90
• Point changes: 1

For the full changelog, read the releaseNotes.md file in the repo.

233.0.0

Release notes for version 233.0.0
Platform API version: 9648

Changes in this version

• Major changes: 12
• Minor changes: 12
• Point changes: 2

For the full changelog, read the releaseNotes.md file in the repo.

232.0.0

Release notes for version 232.0.0
Platform API version: 9635

Release Notes

The Platform API SDK for JavaScript was ignoring (filtering out) query parameters of type boolean when the value is false, and query parameters of type integer/number when the value is 0.
API endpoints with a boolean query parameter whose default value is not false (or has no default specified) are impacted.
Examples:
Impacted: getDownload – issueRedirect default value is true
Not impacted: getOutboundDnclistExport – download default value is false
This behavior will be corrected in future versions of the Platform API SDK for JavaScript.

Given that this issue has existed for a long time and could affect applications that rely on such parameters (set to false or 0), the following approach is being taken:
The SDK will initially continue the legacy filtering behavior (ignoring boolean false and integer/number 0 values).
A new property is introduced at the ApiClient level to control this behavior.
When UseLegacyParameterFilter is true (default), the SDK applies the legacy filter.
This default facilitates a safe transition to modern, accurate filtering without risking unintended behavior changes in existing applications.
To enable accurate filtering, set UseLegacyParameterFilter to false.

Changes in this version

• Major changes: 13
• Minor changes: 93
• Point changes: 5

For the full changelog, read the releaseNotes.md file in the repo.