You can find in this page release notes and compatibility matrix for Gold Standard releases.
September 7, 2021
The build 9032@554dbcd includes the following fix:
August 27, 2021
The build 9032@99a3894 includes the following fixes:
April 14, 2021
The build 9032@d030c36 includes the following fix:
Console upgrade only is mandatory. No server upgrade is required.
Learn more in the Gold Standard section
March 2, 2021
The build 9032@10c2709 includes the following fix:
Console upgrade only is mandatory. No server upgrade is required.
Connect to Adobe Software Distribution to download the new version. Learn how to propose the console update to all end users in this page.
December 22, 2020
The build 9032@d3b452f includes the following improvements and fixes:
The connection protocol has been updated to follow the new IMS authentication mechanism.
Triggers integration authentication originally based on oAUTH authentication setup to access pipeline has now been changed and moved to Adobe I/O. Learn more
Following the end of support for iOS APNs legacy binary protocol, all instances using this protocol are updated to HTTP/2 protocol during postupgrade.
Fixed a security issue to reinforce protection against Server Side Request Forgery (SSRF) issues. (NEO-27777)
Fixed an issue that could cause workflows to fail when running an Enrichment activity. (NEO-17338)
July 7, 2020
The build 9032@efd8a94 includes the following fix:
Fixed an issue which prevented tracking from working when the signature feature was disabled. (NEO-26411)
We recommend that you upgrade the client console with the one available in this release. Refer to this page
22 June 2020
The build 9032@800be2e includes the following fixes:
The following fixes are related to the tracking link security mechanism (learn more in the Security and Privacy checklist):
April 29, 2020
The build 9032@3a9dc9c includes the following fixes:
If you experience issues with push notifications using tracking links, or deliveries using anchor tags, we recommend that you disable the new signature mechanism for tracking links. The procedure is detailed in this page
March 9, 2020
The build 9032@19f73c5 includes the following fix:
December 17, 2019
The build 9032@d6b8062 includes the following fix:
December 11, 2019
The build 9032@bc4a935 includes the following fix:
November 20, 2019
The build 9032@3468c7b includes the following fixes:
September 19, 2019
The build 9032@cee805c includes the following fixes:
August 13, 2019
The initial 19.1.4 build includes the following fixes:
This section lists all systems and components supported for Adobe Campaign Classic Gold Standard 19.1 builds. Products and versions that are not part of this list are not compatible with this version of Adobe Campaign.
Unless mentioned otherwise, all minor releases are supported.
Adobe Campaign Classic is compatible with all the systems and tools listed in this page. As specific versions of these 3rd party systems and tools reach end-of-life (EOL) with their respective creators, Adobe Campaign will no longer be compatible with those versions, and they will be removed from our compatibility matrix in the subsequent product release. Please ensure you are on supported versions of any systems listed in the compatibility matrix to avoid any issues.
CentOs |
8.x (64 bits) 7.x (64 bits) |
Debian |
9 (64 bits) 8 (64 bits) |
RHEL |
7.x (64 bits) Important: If you are using RHEL, you must be willing to disable SELinux or to have your architects write custom SELinux rules to check that an enabled SELinux is not causing issues with Campaign operations. |
Windows Server |
2016 2012 R2 2012 |
Microsoft IIS |
10.0 on Windows Server 2016 8.5 on Windows Server 2012 R2 8.0 on Windows Server 2012 - Windows 8 |
Apache |
2.4 for RHEL7 - CentOS 7, Debian 8/9, Windows (64 bits) 2.2 for RHEL6 - CentOS 6 only (64 bits) |
Java Development Kit (JDK) |
8 The application has been approved for the Java Development Kit (JDK) developed by Oracle as well as for OpenJDK. |
Libre Office |
6 (and previous versions if embedded in your system) |
SpamAssassin |
3.4.x |
RDBMS driver must match with RDBMS server version.
Oracle |
18c 12c 11g R2 |
PostgreSQL |
11.x 10.x 9.6.x 9.5.x 9.4.x Note: you can also use Amazon RDS for PostgreSQL with the versions specified above. |
SQL Server |
2019 2017 2016 2014 2012 - SP1 and SP2 Warning: Microsoft SQL Server is not supported as the primary database when the Campaign server is running on Linux. |
DB2 UDB |
9.7 Warning: DB2 UDB is not allowed for new installations. |
PostgreSQL is the default database server for Hosted environments.
Salesforce connector API |
API version 37 |
SFDC API |
API version 21 API version 15 |
Microsoft Dynamics |
Soap API - On-premise: 2007, 2015, 2016 Soap API - Online: 2015, 2016 Web API - On-premise and Online: 365, 2016, 2016 Update 1 |
Amazon Redshift |
|
Oracle |
12c 11g |
PostgreSQL |
11.x 10.x 9.6.x 9.4.x |
SQL Server |
2019 2017 2016 2014 2012 SP1 and SP2 |
MySQL |
5.7 |
Teradata |
16.20 16 15.10 15.0 |
Netezza |
7.2 |
Sybase |
IQ 16 ASE 15.7 |
SAP HANA |
version 1 SPS 12 |
Hadoop via HiveSQL |
HortonWorks HDP 2.4.X, 2.5.x, 2.6.x HDInsight 3.4 (HDP 2.4), 3.5 (HDP 2.5), 3.6 (HDP 2.6) |
:warning: The following operating systems and browser are required to use Campaign Client Console.
Microsoft Windows Server |
2016 2012 |
Microsoft Windows |
8 10 (recommended for Japanese instances) |
Microsoft Internet Explorer |
11 |
Android |
7.x, 8.x, 9.0 with mobile SDK build 1.0.27. |
iOS |
iOS 9 - 14 with mobile SDK build 1.0.26, compatible with 32 and 64-bit versions. |
The following browsers are compatible with Campaign for Web Access.
Microsoft Edge |
Latest version |
Mozilla Firefox |
Latest version |
Google Chrome |
Latest version |
Safari |
Latest version |
Microsoft Internet Explorer |
11 |