ÃÛ¶¹ÊÓƵ

DocumentationCampaignCampaign Classic v7 Documentation

Deprecated and removed features deprecated-and-removed-features

Last update: Tue Sep 10 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Beginner
  • User

ÃÛ¶¹ÊÓƵ constantly evaluates product capabilities to identify older features that should be replaced with more modern alternatives to improve overall customer value, always under careful consideration of backward compatibility. As ÃÛ¶¹ÊÓƵ Campaign Classic works with 3rd party tools, compatibility is updated on a regular basis, in order to implement supported versions only. Versions which are no longer compatible with ÃÛ¶¹ÊÓƵ Campaign Classic are listed below and in the Compatibility matrix.

To communicate the impending removal/replacement of Campaign Classic capabilities, the following rules apply:

  • Announcement of deprecation comes first. While deprecated capabilities can still be available and supported for existing users, they will not be further enhanced, nor documented.
  • Removal of deprecated capabilities will occur in the following release at the earliest. Actual target date for removal is announced in this page.

This process gives customers at least one release cycle to adapt their implementation to a new version or successor of a deprecated capability, before actual removal.

NOTE
ÃÛ¶¹ÊÓƵ Campaign releases and new capabilities are listed in the Release Notes.

Deprecated features deprecated-features

This section lists features and capabilities that have been marked as deprecated with latest Campaign Classic releases.

Generally, features that are planned to be removed in a future release are set to deprecated first. These features and capabilities are either no longer available for new Campaign Classic customers, or should not be used for any new implementation. They are also removed from product documentation.

Customers are advised to review if they make use of the feature/capability in their current deployment, and make plans to change their implementation. Please refer to the target removal date to plan your environment and project updates accordingly.

Feature
Details
Campaign (Neolane) legacy SDK

The Campaign (Neolane) SDK for mobile applications is now deprecated. Instead, use the ÃÛ¶¹ÊÓƵ Experience Platform Mobile SDK by configuring the ÃÛ¶¹ÊÓƵ Campaign extension in the Data Collection UI. The ÃÛ¶¹ÊÓƵ Experience Platform Mobile SDK helps power ÃÛ¶¹ÊÓƵ's Experience Cloud solutions and services in your mobile apps. SDKs configuration is managed through the Data Collection UI for flexible configuration and extensible, rules-based integrations. Learn how to configure the Mobile App channel in Campaign v8 documentation.

Target removal date: Summer 2025

Social Marketing with Facebook

Social Marketing with Facebook is now deprecated. You can use X (formerly known as Twitter) integration to post on social media, or work with ÃÛ¶¹ÊÓƵ to create a custom channel.

ACS Connector

ACS Connector (Prime offering) is now deprecated. You can use Campaign export/import capabilities to extract and inject data in both products.

Removed features removed-features

This section lists features and capabilities that have been removed from Campaign Classic.

Feature
Details
ÃÛ¶¹ÊÓƵ Analytics Data Connector

The ÃÛ¶¹ÊÓƵ Analytics Data Connector has been removed on August 17,2022. It had been deprecated with Campaign 21.1.3 release.

If you are using this connector, you need to adapt your implementation accordingly. Learn more

Technical Deliverability Monitoring Report

The Technical Deliverability Monitoring Report is no longer available. It had been deprecated with Campaign 21.1.3 release.

OAuth Authentication (OAuth and JWT)

Triggers integration authentication originally based on OAuth authentication setup to access pipeline has now been changed and moved to ÃÛ¶¹ÊÓƵ I/O. This authentication mode had been deprecated with Campaign 20.3 release.

If you were using Triggers integration, learn how to adapt your implementation in this page.

For more information on OAuth Authentication depreciation, refer to this

Reporting
Following ÃÛ¶¹ÊÓƵ Flash Player EOL, the Gauge report and Chart rendering engine are no longer available. Learn more
Fax channel
Starting Campaign 21.1.3 release, the Fax channel is no longer available. Learn more
Demdex domain
Starting Campaign 21.1.3 release, the demdex domain used to import and export audiences to the ÃÛ¶¹ÊÓƵ Experience Cloud is no longer available. Learn more
Windows NT authentication
Starting Campaign 20.3 release, Windows NT authentication has been removed from the available authentication methods when configuring a new database with a Microsoft SQL Server.. Learn more
File-based email archiving
Starting Campaign 20.2 release, file-based email archiving is no longer available. Email archiving is now available through a dedicated BCC email address. Learn more
Lead management
Starting Campaign 20.2 release, the Leads Management package is no longer available. Similar functionality can be implemented via other native workflow activities and data model modifications.
Campaign APIs documentation - jsapi.chm file
Starting Campaign 19.1 release, Campaign Classic APIs are available in a dedicated page. If you were using the legacy jsapi.chm file, you should now refer to the new online version.
Campaign Orchestration - Predictive marketing
Starting Campaign 18.10 release, the predictive marketing capabilities are no longer available.
Web applications - Microsites
Starting Campaign 18.10 release, Microsites are no longer available. You can improve security by restricting access to only dedicated domains on ÃÛ¶¹ÊÓƵ Campaign configuration files, and use personalized URLs in Campaign by using DNS aliases.
Push Notifications - iOS Binary Connector
Per Apple's recommendation, ÃÛ¶¹ÊÓƵ has removed the legacy iOS Binary Connector starting Campaign 18.10 release. The more capable and more efficient HTTP/2-based connector is already available.
decryptString API

Starting Campaign 18.6 release, for security reasons, decryptString API is no longer available by default for new installations.

In the context of a postupgrade to 18.6 (and later), this API is no longer activated, and has been replaced by the decryptPassword function. Learn more

Mobile channel - MMS and WAP Push messages
Starting Campaign 18.4 release, MMS and Wap Push channels are no longer available. As a replacement, you can leverage SMS and Push deliveries.
Mobile channel - LINE v1
Starting Campaign 18.4 release, LINE Connect package is no longer available. ÃÛ¶¹ÊÓƵ recommends using the new LINE Channel package as a replacement. Learn more

End of compatibility end-of-compatibility

CAUTION
ÃÛ¶¹ÊÓƵ Campaign Classic is compatible with all the systems and tools listed in the Compatibility matrix. When specific versions of these 3rd party systems and tools reach end-of-life (EOL) with their respective creators, ÃÛ¶¹ÊÓƵ Campaign is no longer compatible with those versions: they are announced as deprecated, and then are 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.

Client console client-console-eol

ÃÛ¶¹ÊÓƵ Campaign Classic Client Console can no longer run on the following systems as they have been deprecated by their editor. Customers running Campaign Client Console on one of these versions need to upgrade to newest version before target removal date. Refer to the Compatibility matrix.

  • Windows Server 2003, 2008, 2008 R2
  • Windows 7, XP, Vista
NOTE
Starting Campaign 20.1 release, Campaign Classic Client Console 32 bits is no longer compatible with Campaign latest versions. You need to use 64 bits Client Console.

Operating systems o-s-eol

  • Starting 7.3.1 release, ÃÛ¶¹ÊÓƵ Campaign is no longer compatible with Windows 8 and Windows Server 2012.

  • Starting 22.1 release, ÃÛ¶¹ÊÓƵ Campaign is no longer compatible with CentOs 8.x (64 bits). CentOS Linux 8 reached End Of Life (EOL) on December 31st, 2021. .

    If you were using this operating system, adapt your implementation accordingly. CentOS 7.x (64 bits) and RHEL 8.x/7.x (64 bits) are still supported.

  • Starting 21.1.3 release, ÃÛ¶¹ÊÓƵ Campaign is no longer compatible with Debian 8.

  • Starting 19.1 release, ÃÛ¶¹ÊÓƵ Campaign is no longer compatible with the following operating systems.

    • CentOS 6.
    • Debian 7.
    • RHEL 6.x.
    • Windows Server 2008.
    • SLES 11.

Web servers web-server-eol

Starting 19.1 Spring Release, ÃÛ¶¹ÊÓƵ Campaign is no longer compatible with the following web server.

  • Apache 2.2.
  • Microsoft IIS 7.

Tools tools-eol

Starting 19.1 Spring Release, ÃÛ¶¹ÊÓƵ Campaign is no longer compatible with the following tools.

  • Java JDK 7.
  • Libre Office 3.5 / 4.3 / 5.x, except when embedded in another tool.

Database engines dbe-eol

ÃÛ¶¹ÊÓƵ does not support the following database engines as they have been deprecated by their editor. Customers running in these versions need to upgrade to newest version or move to another one.

Refer to Campaign Compatibility matrix to access the list of compatible versions.

FEDERATED DATA ACCESS (FDA)

Starting 20.2 release, ÃÛ¶¹ÊÓƵ Campaign is no longer compatible with the following FDA Server:

  • DB2 UDB 10.5

Starting 19.1 Spring Release, ÃÛ¶¹ÊÓƵ Campaign is no longer compatible with the following FDA Servers:

  • PostgreSQL 9.3.
  • MySQL 5.5.
  • DB2 9.5.
  • Teradata 14 – 14.1.

Campaign Classic is not compatible with the following servers in Federated Data Access (FDA). Please use more recent versions, or systems.

  • DB2 UDB 9.5, 9.7.
  • Oracle 9i, 10G R2.
  • PostgreSQL versions up to 9.6 reached end of life.
  • MSSQL 2000, 2005, 2008 R2.
  • MySQL 5.1.
  • InfiniDB reached end of life.
  • Teradata 13, 13.1.
  • Netezza 6.02, 7.0. Netezza reached end of life.
  • AsterData 5.0. AsterData reached end of life.
  • Sybase IQ 15.2, 15.4, 15.5 and Sybase ASE 15.0.
  • Hadoop via HiveSQL: Hadoop 2.7.3, HiveSQL 1.2.1. ÃÛ¶¹ÊÓƵ Campaign Classic still support the listed versions of Hadoop via HiveSQL through Federated Data Access (FDA), but these versions are merged with: HortonWorks (HDP 2.4.X, 2.5.x, 2.6.x) and HDInsight 3.4 (HDP 2.4), 3.5 (HDP 2.5), 3.6 (HDP 2.6)

RDBMS SERVER

Starting 19.1 Spring Release, ÃÛ¶¹ÊÓƵ Campaign is no longer compatible with the following RDBMS Servers:

  • Oracle 10GR2
  • PostgreSQL 9.0 to 9.3
  • SQL Server 2005
  • MySQL 5.1
  • DB2 UDB 9.7

PostgreSQL versions up to 9.6 reached end of life. They are therefore not supported by ÃÛ¶¹ÊÓƵ Campaign.

SMS connectors sms-eol

Starting 20.2 release, Legacy SMS connectors are deprecated. ÃÛ¶¹ÊÓƵ Campaign is not compatible with:

  • Generic SMPP (SMPP version 3.4 supporting binary mode)
  • Sybase365 (SAP SMS 365)
  • CLX Communications
  • Tele2
  • O2
  • iOS

CRM connectors crm-connectors

Starting Campaign 21.1 release, the following CRM connectors are no longer compatible with Campaign:

  • Soap API - On-premise: 2007, 2015, 2016
  • Soap API - Online: 2015, 2016
  • Web API – Microsoft Dynamics CRM 2016
  • Web API – Microsoft Dynamics CRM 2016 Update 1
  • Oracle On Demand API
recommendation-more-help
601d79c3-e613-4db3-889a-ae959cd9e3e1