Version-Specific Patching with the requested_version Parameter

Background

In many managed environments, organizations standardize on specific application versions that have been validated against their internal security policy. End users' policy configurations define which application version is approved, and the newest release is not always the approved one — it may not yet have passed the organization's change-control process.

Problem

Patching always to the latest available version can conflict with these policies: customers need to install or update an application to the exact version defined in the policy configuration from their users, rather than whatever version is newest.

Solution Overview

The SDK supports version-specific patching through the requested_version parameter in both the GetLatestInstaller (50300) and InstallFromFiles (50301) methods, allowing customers to install or update an application to the exact version that matches the policy configuration from their users:

• In GetLatestInstaller, input a version in requested_version to download (or retrieve download information for) that specific application version.
• In InstallFromFiles, input a version in requested_version to install that specific version from local installer files, including older versions.

Version-specific patching with GetLatestInstaller requires the new patch database, patchv2.dat, which contains all application versions recognized by the SDK. Load it via LoadPatchDatabase (50302) by specifying patchv2.dat in the dat_input_source_file field. If the legacy database (patch.dat) is used and requested_version is specified, the SDK ignores the parameter. For details, see Introduction to patchv2.dat.

When requested_version is not provided, both methods behave as before: the SDK targets the latest available version.

Behavior

Error Codes

SDK Version

• Windows: 4.3.6110.0
• Mac: 4.3.5495.0

If Further Assistance is required, please proceed to log a support case or chatting with our support engineer.