Latest release

This page lists new capabilities, improvements and fixes coming with the latest Campaign Classic Release.

Understand Campaign build statuses in this page.

Release 21.1.4 - Build 9343

October 8, 2021

Patches

  • Fixed an issue which could prevent proper offer management when using the Interaction module with the Power Booster option. (NEO-39263)

  • Fixed an error ‘The ipaffinity xxx is not found on mid server xxx’ which could happen on delivery sending when using more than one IP affinity on a multi mid-sourcing instance. (NEO-37514)

Release 21.1.4 - Build 9342

September 7, 2021

Security enhancement

  • Fixed a security issue to reinforce protection against directory traversal attacks. (NEO-28547)

Improvements

  • Following its end of life, Flash has been removed from all related Campaign features and components, and replaced with HTML5. The Gauge type of chart has been removed. (NEO-30330) Read more
  • When installing the client console on Windows, the installer now checks if there is a parent registry node and creates one if it is missing. This prevents potential issues when launching the console. (NEO-34854)
  • The tracking signature feature has been improved to prevent errors linked to the way third-party tools (email clients, internet browsers, etc.) handle special characters. URL parameters are now encoded.

Other changes

  • Previously deprecated Microsoft CRM connectors (Office 365 and On-premise deployments) have been removed from the interface. Read more
  • Following the migration to Tomcat 8, the IIS setup script has been updated to fix IIS integration issues. (NEO-31019)
  • A guardrail has been added to only allow the billing technical workflow to run on the marketing instance.
  • The data source identification has been improved in the data and schema tabs of the workflow transitions’ View population window.
  • Missing database indexes were added to the following schemas to prevent database update issues: xtk:rights, nms:dlvExclusion, nms:seedMember, nms:trackingUrl

Patches

  • Fixed an issue which prevented the Hot clicks report from working when offers were linked to the delivery. (NEO-26295)
  • Fixed an issue with the Sub-worfklow activity when its execution did not generate an output table. (NEO-36242)
  • Fixed various issues when exporting the Descriptive analysis report to PDF. (NEO-25847)
  • Fixed an issue which could lead to deliveries failing when using an external mail delivery. (NEO-37435)
  • Fixed an error when connecting to Microsoft CRM using web API. The error message has been removed since functionalities were not impacted.
  • Fixed a tracking log deduplication issue when the mid server was set as a relay between tracking and marketing servers. (NEO-36285)
  • Fixed a regression which prevented Vault from being used as a specific code store.
  • Fixed an issue which prevented you from using variables in an Enrichment workflow activity when the incoming transition was from an FDA data source.
  • Fixed an issue that could lead to broken URLs in email messages.

Release 21.1.3 - Build 9330

June 5, 2021

What’s new?

New workflow activity: Change Data Source

The new Change Data Source workflow activity allows you to change the data source of a workflow's working table. This provides enhanced flexibility in managing data across different data sources (FDA & local database).

In Adobe Campaign workflows, data is managed using working (or temporary) tables. As the workflow executes, working tables share data across workflow activities. By default, working tables are created on the same database as the source of the data we query on.

For more information, refer to the detailed documentation.

Integration with Adobe Journey Orchestration

The integration between Journey Orchestration and Adobe Campaign Classic is now GA. It allows Journey Orchestration to send emails, push notifications and SMS using Adobe Campaign Classic Transactional Messaging capabilities.

The connection between the Journey Orchestration and Campaign Classic instances is setup by Adobe at provisioning time.

For more information, refer to the Journey Orchestration documentation. A step-by-step use case is presented in this section

LINE channel enhancements

The following improvements have been added to LINE channel:

  • Support for LINE video message type

  • Support for LINE Partner Registration API

  • Support retry of message sending in the event of LINE server-side error or network timeout

For more information refer to the detailed documentation.

Vertica FDA connector

You can now connect your Adobe Campaign Classic instance to your Vertica external database. This connection is managed through a new external account.

For more information refer to the detailed documentation.

Google Big Query FDA connector

You can now connect your Adobe Campaign Classic instance to your Google Big Query external database. This connection is managed through a new external account.

For more information refer to the detailed documentation.

Security enhancements

  • Access to the xtk:session#GetCnxInfo API method returning the full database connection details is now restricted to admin users only. (NEO-27779)
  • The deprecated decryptString function has been replaced with decryptPassword in CRM related JavaScript files.
  • The tracking signature feature has been improved to reduce the risk of tracking redirection errors when third-party tools (email clients, internet browsers, safe link security tools) modify the tracked link.
  • Fixed an issue which could prevent tracked URLs from working when containing uppercase characters. Tracked URLs signing mechanism is now case sensitive. (NEO-28414)

Compatibility updates

The following systems are now supported with Campaign:

  • Google Big Query FDA connector
  • Vertica FDA connector
  • PostgreSQL 13

Learn more in the Campaign Compatibility matrix.

Deprecated features

  • Starting Campaign 21.1 release, the Adobe Analytics Data Connector is deprecated. If you are using this connector, you need to adapt your implementation accordingly with the new connector Adobe Analytics Connector.
    For more information refer to the detailed documentation.
  • Support for Debian 8 is now deprecated.
  • Following the deprecation of Oracle CRM in 20.3, the related external account has been removed from the interface.

Learn more in the Deprecated and removed features page.

Improvements

  • Extra checks have been added when saving a workflow to make sure that activity names are unique and that transitions are always followed by an activity.
  • The Billing (billing) technical workflow now includes the tasks originally performed by the Number of active billing profiles (billingActiveContactCount) workflow, which has been removed. The email report sent each month by the workflow will now provide information on the number of active profiles on the instance. Read more.
  • New _keyOnMData attribute has been added to be able to use a key for operations on memo data.

Other changes

  • The openssl third-party for Windows has been updated to version 1.1.1h.
  • In the Debian package description, nlserver has been changed to Adobe Campaign Classic server.

Patches

  • Fixed an issue when editing the session timeout to log out users after a specific amount of time where users remained logged in even after the set time.
  • Fixed an issue where deliveries were displayed as read-only but could still be edited in the deliveries properties.
  • Fixed an error which caused the editing tool bar to disappear when designing a web application.
  • Fixed an error which displayed the text version of an email with Adobe Campaign Classic headers when adding a link to an email. (NEO-29211
  • When using FDA over HTTPs connection, the Mid-sourcing (delivery logs) (defaultMidSourcingLog) workflow was stuck in the timeframe set by the NmsMidSourcing_LogsPeriodHour option. This would prevent records from being updated with data that occurred after this set timeframe. (NEO-30833)
  • Fixed an issue which occurred after executing the message center synchronization workflow. Every time a delivery objects folder was moved to a custom folder, the workflow would move the deliveries back to the generic Transactional message history folder. (NEO-27445)
  • Fixed an issue which displayed an error message when trying to display the Broadcast statistics, Tracking indicators, and Statistics of the sharing activities reports.
  • The Oracle On Demand workflow activity has been removed from the interface following Oracle CRM connector deprecation.
  • Fixed an issue which stopped the execution of processing workflows after the daily restart of the workflow server (wfserver) module. (NEO-30047)
  • Fixed an issue that prevented the MX management document from being updated, which could negatively impact IP reputation. (NEO-29897)
  • Fixed issues that caused web process crashes when receiving a SOAP call. (NEO-28796) (NEO-29600)
  • Fixed an issue that caused the SAP HANA FDA index creation to fail. (NEO-29664)
  • Fixed an issue which could keep transactional messages in Waiting state when performing SOAP calls containing a header. (NEO-28737)
  • Fixed an issue that occurred when using the Teradata FDA connector: all the temporary tables were created on only one node of the cluster, which could end up consuming the whole spool space and make Teradata crash. The temporary tables are now generated on many nodes. (NEO-28230)
  • Fixed an issue when using web applications which led tracking tags to generate incorrect primary keys into the nms:trackingURL schema. (NEO-27931)
  • Compatibility to ODBC 3.x has been enhanced to ensure error message accuracy.
  • Fixed an issue which could lead to console crashes when custom content templates were used in email deliveries. (NEO-31547)
  • Fixed an issue that prevented Tomcat from sending valid responses due to a slow connection or large response size.
  • Fixed an issue which could occur when reading UUID from a PostgreSQL database.
  • Fixed an issue which could lead to performance issues when searching on proposition data linked to offers. (NEO-27554)
  • Fixed an issue which lead to the Web process not responding when the IMS service was activated but not responding.
  • Fixed an issue which prevented you from sending a delivery with a group of proofs due to a specific joining mechanism that failed the delivery personalization. (NEO-14391)
  • Fixed an issue which failed to send an alert with the alert activity if a query and an enrichment activity targeted the delivery table. (NEO-25157)

Release 21.1.2 - Build 9282

April 15, 2021

  • Password management has been improved to optimize security.
  • Fixed an issue that could cause MTA crashes.

Release 21.1.1 - Build 9277

February 22, 2021

Security enhancements

  • The console authentication mechanism has been improved to optimize security. (NEO-26944)
  • Fixed a security issue to reinforce protection against Server Side Request Forgery (SSRF) issues. (NEO-28532)

Compatibility updates

The following systems are now supported with Campaign:

  • Salesforce API version 49 is now supported when using Salesforce CRM external account.

Deprecated features

The Technical Deliverability Monitoring report is now deprecated.

Learn more in the Deprecated and removed features page.

Improvements

Email Feedback Service (EFS) is a scalable service which captures feedback from the Enhanced MTA directly, thus improving reporting accuracy. This capability is released as a private beta and will be progressively available to all customers in future releases.

  • All categories of feedback are now captured for complete and precise reporting.
  • Calculation of the Delivered indicator is now based on real-time feedback from the Enhanced MTA for improved accuracy and reactivity.
  • EFS solves the problem of delays with synchronous soft bounces reporting.

For more information refer to the detailed documentation.
If you’re interested in participating in this private beta, fill out this form and we’ll get back to you.

Other changes

  • Transfer speed has been improved for large tracking logs by using compression.
  • Workflow Heatmap has been improved to avoid timeouts when running workflows with multiple activities. (NEO-27423).
  • Fixed an issue which could allow an offer to be presented even if its end date was passed. Campaign Classic now takes into account the end date’s whole timestamp rather that the date only. (NEO-27590)
  • The Google+ link has been removed from the Social network sharing links personalization block.
  • Fixed an issue after the implementation of a bug fix in the last release. A check was added on the hostname when connecting using SSL/TLS which led SMS deliveries to fail. Hostname verification has been disabled for most protocols such as POP3, SMS and HTTP with proxy and the certificate check for the SMS external account has been improved with three values (NEO-29581). Learn more

Patches

  • Fixed an issue which prevented the Tab, Enter and Escape keyboard shortcuts from working on the new logon screen.
  • Fixed a refresh issue which caused the name of a newly created workflow to be replaced with the default value after saving (NEO-26106).
  • Fixed an issue that occurred when running workflows where a new field was added as part of an Enrichment activity prior to a Delivery activity using an External file target mapping: unwanted fields were added to the External file target mapping. (NEO-27687)
  • Fixed an issue that caused some characters in the source code to be altered when reopening a web application previously created and saved. (NEO-27597)
  • Fixed an issue that could occur when upgrading to a build including the new signature mechanism for tracking links (from Build 19.1.4 and Campaign 20.2): when several templates were associated to an event, upgrading could cause the wrong template to be selected when sending the transactional message. (NEO-28326)
  • Fixed an issue that caused the MTA to become unresponsive and unable to process deliveries unless restarted. (NEO-27455)
  • Fixed an issue on MSSQL database related to timestamp management during bulk load operations for a datetime type column.
  • Fixed a workflow query issue when using Redshift xtk functions. The SubDays, SubSeconds, SubMinutes and SubHours now accept both Redshift timestamp types (NEO-24962).
  • Fixed an issue which displayed a script error message when trying to preview a report with Anonymous access. (NEO-27081)
  • Fixed an issue which could reduce the memory usage on the server when performing delivery analysis.
  • Fixed an issue which could prevent the instance from working when trying to run specific complex queries.
  • Fixed an issue which could prevent the Synchronizing Twitter pages technical workflow from running. (NEO-28634)
  • Fixed an issue which could display an error message related to the decryptPassword function when trying to publish on Twitter using the Tweet (twitter) delivery template. (NEO-28216)
  • Fixed an issue which occurred when using a Javascript activity to make an HTTP request in a workflow. After defining the port number in the Host name, the call would fail with the following error (NEO-29146):
IOB-090020 Error in SSL library: 'IOB-090013 error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed (code 336134278)'
  • Fixed an issue that prevented new deliveries with target data personalization from being sent (NEO-30323).
  • Fixed an issue where several crashes occurred in the marketing instance causing core files.
  • Fixed an issue which led the Tracking workflow to fail with the following error (NEO-25206):
There is no index on the sourceId field of the 'NmsTrackingLogRcp' table required for the current Web tracking mode. Please add this index.
  • Fixed an issue which occurred when creating and saving a delivery within the Targeting & Workflow tab of a campaign: the preview would fail with the following error (NEO-29440):
XTK-170024 The temporary 'temp:deliveryEmail-all' schema is not defined in the current context
  • Fixed an error which occurred when setting up an external account between a marketing instance and an Adobe Campaign Standard instance or a Campaign Classic mid-sourcing instance and using the option “DisableFOH2=1”. When using the “DisableFOH2=1” option in the external account, connections were not properly closed and would pile up resulting in the following error (NEO-26258):
The maximum number of connections has been reached (50) by connections pool 'nms:extAccount:acsDefaultRelayAccount XXX'. The server is overloaded. Please try again later.
  • Fixed an error with SMS when connection issues occurred between the server and provider. The connection would then be automatically disabled by the MTA child. Adobe Campaign Classic would not try to connect to this failing connection as long as a new child had not been started.

On this page