Release 19.1

Release 19.1.8 - Build 9039

April 15, 2021

  • Fixed a client console regression which caused persistent error messages on the IMS connection screen. (NEO-34821)
  • Fixed a regression that could block the workflow data export to an FDA database (Teradata, Snowflake).

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.

March 22, 2021

  • Fixed a regression preventing the usage of some components of the console, such as the date picker and images management in deliveries. (NEO-31453, NEO-31454)

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 16, 2020

  • This release comes with a new connection protocol: if you are connecting to Campaign through Adobe Identity Service (IMS), upgrade is mandatory for both Campaign server and client console to be able to connect to Campaign after June 30, 2021. Learn more
  • This release comes with a security fix: upgrade is mandatory to reinforce your environment security.
  • If you are using the Experience Cloud Triggers integration through oAuth authentication, you need to move to Adobe I/O as described in this page. Legacy oAuth authentication mode with Campaign has been retired on September 2021. Hosted environments benefit from an extension until Febuary 23, 2022. As an on-premise or hybrid customer, contact Adobe Customer Care to extend support to Febuary 2022. You must provide the AppID of the OAuth application to Adobe.


  • 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 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 causing the deactivation of the SMPP connector after a connection error, preventing other SMS deliveries from being sent and leading to performance issues.
  • Fixed an issue that displayed incorrect percentages when generating a descriptive report via a workflow activity. (NEO-14314)
  • Fixed a delivery preparation issue when the Exclude duplicate address during delivery option was unselected. (NEO-13240)
  • Fixed an issue that could cause workflows to fail when running an Enrichment activity. (NEO-17338)
  • Fixed an issue in workflows when fetching records from an external database and inserting them in the Campaign database. (NEO-26359)
  • Fixed a server crash issue by preventing memory corruption when cleaning the expression parser.
  • Fixed an issue which prevented the NoNull function from working in Oracle databases after upgrading to build 9032. (NEO-26488)
  • Fixed an issue when editing a campaign template description that prevented the Save button from displaying when copy-pasting symbols like, for example, Japanese characters. (NEO-27071)
  • Fixed an issue which prevented the description of a campaign or campaign template from being saved when clicking outside of the window before clicking the Save button. (NEO-27449)
  • Fixed an issue at the proxy configuration level that prevented you from logging into Adobe Campaign after the latest Windows 10 update. (NEO-27813)
  • Fixed an issue related to the management of empty lines in log files, causing failures in the MTA process behavior and leading to performance drops in delivery sending.

Technical evolutions

Tomcat has been updated from version 7 (7.0.103) to version 8 (8.5.57). The tomcat-7 directory is replaced with a tomcat-8 directory. On windows, iis_neolane_setup.vbs and apache_neolane.conf are now installed in the conf directory (instead of tomcat-7/conf previously). On linux, apache_neolane.conf is now installed in the conf directory.

On Linux, the nlserver service startup now uses a systemd unit instead of the /etc/init.d/nlserver6 script. The migration to the new startup scheme is performed automatically when you install the 19.1.8 package. The /etc/init.d/nlserver6 is still provided but for interacting with the nlserver service (start, restart, stop, etc.), we recommend that you use the systemctl command directly.

Release 19.1.7 - Build 9036

September 15, 2020


  • Improved nlsrvmod for Apache 2.4 thread usage to fix nlsrvmod crashes.
  • Fixed an issue when using the File Transfer activity with an Azure external account and an SSL encryption. The connection was performed through HTTP instead of HTTPS. (NEO-26720)
  • Fixed an issue with the url cache mechanism which did not retrieve the label or category.
  • Fixed an issue which led to mirror page URLs being incorrectly defined in email deliveries (due to improper ASCII character control). (NEO-26084)
  • The jarsToSkip list in has been updated to remove the reference to a jar file that was no longer used (iOS notifications).
  • Fixed a regression issue which prevented after publication after postupgrade.
  • Fixed a regression with out-of-the-box delivery reports which appeared truncated when exported to PDF. (NEO-25757)
  • Fixed an issue that deleted the encoding parameter value when redirecting from a tracking URL (impact on Japanese characters). (NEO-25637)
  • Fixed an issue which led to unsigned links from personalized domains being blocked when they should be allowed. (NEO-25210)
  • Fixed a regression impacting calculated fields in a workflow causing the workflow to fail. (NEO-25194)
  • Fixed a compatibility issue with Microsoft Dynamics (from version 8.2) that could prevent some API calls from executing (RetrieveAllEntities). (NEO-24528)
  • Fixed a regression issue when using the ACS Connector feature which prevented the connection to a Campaign Standard instance (incorrect management of the FOH/FOH2 connection). (NEO-23433)
  • Fixed a regression issue on database connection causing the web server to constantly restart due to a database encoding problem. This could lead to overconsumption. (NEO-23264)
  • Fixed an issue with the database cleanup workflow which could fail due to unmanaged data source. (NEO-23160, NEO-23364)
  • The cleanup workflow now purges expired lists by batches of 100 instead of one by one.
  • Following the switch to the new sequence ID mechanism, all web applications that are updating the recipient table are republished during postupgrade.
  • Fixed an issue preventing emails from being sent when there was Javascript code outside of the HTML content tag. (NEO-18628)
  • Fixed an issue that prevented the transactional messages tracking indicators from being updated by the Tracking workflow. (NEO-17770)
  • Improved the performance of the database update wizard to make fewer SQL statements in order to optimize response time.
  • Fixed a console crash issue that could occur when unchecking tracked URLs in an email, from the Text content tab due to a non-initialized variable. (NEO-13545)
  • Fixed an issue which prevented you from uploading files in a File Transfer activity using an Azure Blob Storage external account due to a non-initialized variable (m_pCurlReader). (NEO-13717)
  • Fixed a postupgrade issue which turned off Apache and the web server before the web application republication. (NEO-27155)
  • Fixed a regression which led to an incorrect timezone being picked when setting time in a Scheduler workflow activity.

Release 19.1.6 - Build 9035


This build is for on-premise installations only. For hybrid deployments, hosted instances will keep running the 9032 build. Do not upgrade your marketing instance to the 9035 build as it is not compatible with 9032.

October 3, 2019


  • Fixed an issue when using the CRM Connector for Salesforce. (NEO-17712)
  • Fixed an index issue which could cause performance issues when sending transactional messages.
  • Fixed a performance isssue when sending messages. (NEO-17558)
  • Fixed an issue which could lead to certain messages not being processed by the Mid-Sourcing server. (NEO-12395)
  • Fixed an issue which prevented the full use of the SQL Data Management activity (the “SQL Data Management” named right was missing).

Release 19.1.5 - Build 9033

August 13, 2019


  • Fixed an issue with the SQL statement ‘SELECT COUNT’ which was executed on the default database rather than the FDA database during Data extraction in Data Management activity.
  • To improve customer infrastructure capabilities, an SFTP proxy declaration is now available in the server configuration file.
  • Fixed a crash issue when the Add linked table field was empty in the Data Loading (RDBMS) workflow activity. (NEO-12213)
  • Fixed an issue with the midEmitter package installation through command line.
  • A new authentication option has been added to support OAuth credentials within the AC connector with Microsoft Dynamics. (NEO-11982)
  • Fixed an issue with UUID (Unique Universal Identifier) management causing the Query and Data loading workflow activities to fail with Hive FDA.
  • Fixed a regression on Oracle causing some functions to be considered as invalid after postupgrade. (NEO-12759)
  • Fixed a regression leading to an incorrect time zone being picked when setting the time in a Scheduler workflow activity.

Release 19.1.4 - Build 9032


19.1.4 Gold Standard releases are listed in this page.

Release 19.1.2 - Build 9029

June 21, 2019

Security enhancements

  • To optimize security, the Java library (Netty) has been updated to the latest version (4.1.34). (NEO-12788)


  • Fixed a regression linked to sdomain column management which prevented emails from being sent on certain configurations.
  • To improve performance, a _operation=“none” attribute has been added to rtEvent SOAP calls to avoid “SELECT FOR UPDATE” requests.
  • Fixed a workflow display issue with outbound transitions after the Test activity. (NEO-12727)
  • We now allow the deletion of dummy records created in Microsoft Dynamics during import workflow.
  • Improved permissions to execute the security zone package when using internal account.

Release 19.1 - Build 9026

May 30, 2019

What’s new?

Control Panel

To increase efficiency in your work as an Admin user, manage settings of your SFTP servers by monitoring storage, add IP addresses to allowlist, and installing SSH keys for each instance. Please note Control Panel is only available for customers hosted on AWS as of today (login through the Experience Cloud today).

For more information, refer to the detailed documentation and the how-to video.

Note: upgrading to the latest Campaign build is not required to access the Control Panel.

Audit trail

As admin, increase productivity by monitoring and managing changes made within the Adobe Campaign Classic instance. The Audit Trail will log actions made on Source Schemas, Workflows and Options. You can quickly see if an element has been created, modified or deleted.

For more information, refer to the detailed documentation and how-to video.

Guardrail, Robustness & Scalability
A series of improvements has been added to Campaign Classic. Guardrail, robustness and scalability improvements are listed below.
Compatibility Matrix Update
With this new version, Adobe Campaign now supports the following database systems. Refer to the Compatibility Matrix.
  • Oracle 18c

  • MySQL 5.7 (FDA)

  • SQL Server 2017

  • Teradata 16 (FDA)

  • PostgreSQL 11

Security enhancements

  • For security reasons, you can no longer insert arbitrary commands when using the Pre-process the file option in a Data loading (file) workflow activity. A drop-down list is now available allowing you to select from 3 options: None, Decompression (zcat) or Decrypt (gpg). The XtkSecurity_Disable_Preproc security flag has been added. For new customers, this option will be set to 0. For existing customers, this option will be set to 1 by the postupgrade in order to keep the previous behavior. Refer to this section.
  • Fixed a password visibility issue that occurred when testing the connection of an FDA external account with no time zone set.
  • The PDFBox library has been removed.
  • Tomcat has been updated to version 7.0.93.
  • Fixed a token visibility issue that occurred when the security token was invalid.
  • Fixed a potential XTK injection issue in the WSDL JSP (schemawsdl.jsp).
  • The credential and password storage in the application’s source code and memory has been optimized.
  • PII view restriction has been optimized. (NEO-12339, NEO-12396, NEO-12398, NEO-12339, NEO-12667)
  • Fixed inconsistency issues in secret key management.
  • The same generic error is now displayed for failed login attempts with a valid or invalid username.
  • The naming of uploaded files has been enhanced.
  • A new XtkSecurity_Disable_GetSetEnv option has been added to block the use of setEnv and getEnv functions.
  • Sensitive information is now hidden in the application stack trace.

Guardrail, robustness & scalability improvements

  • Lifespan - XtkNewId sequence usage optimization: the most consuming tables have been moved from the xtkNewId sequence to dedicated sequences. Read more
  • FDA over HTTP v2: the FDA over HTTP protocol is widely used on Hybrid deployments, especially for broadLog retrieval and delivery preparation. Robustness has been enhanced to avoid network issues and possible errors as retrieving or pushing data. This requires that builds at both ends of the connection are up-to-date, otherwise the old protocol will still be used.
  • Tracking workflow: the tracking workflow robustness has been enhanced. Several issues related to tracking log inserts/updates and URL tracking customization have been fixed. In addition, the tracking workflow now detects tracking log issues that could lead to errors and stop the workflow. These issues are now discarded and not processed.
  • Cleanup workflow: the cleanup workflow has been improved to avoid potential errors and stops. This optimizes database size and performance.
  • Embedded images in transactional messages: we have added the full support of embedded images in transactional messages, to avoid possible crashes or missing images.
  • Database size - XtkJobLog: a purge mechanism has been added to this table. This has a positive impact on the database size.
  • BCC archiving: the default parameters for BCC archiving have been changed to increase archiving velocity. Read more
  • Database structure update: SQL requests generated by the Database Structure Update Wizard have been improved for faster execution.
  • Guardrails for operator actions: several guardrails have been implemented to prevent operators from performing actions which could impact the platform’s integrity. Built-in schemas can no longer be deleted through the interface. Also, the workflow source XML can no longer be edited by non-admin users.
  • Two new options have been made available: XtkSecurity_Restrict_EditXML (allows you to disable the edition of deliveries’ XML code) and NmsOperation_OperationMgtDebug (allows you to monitor the operationMgt technical workflow execution). Read more

Other changes

  • Push notifications: we now support the Thread ID option for iOS push.
  • Improved the management of long name indexes which could cause postupgrade issues.
  • Now, during the analysis of a decomail delivery, if the publication mode is set to None in the deployment wizard, an error is logged and the analysis is stopped: “Publication mode is set to ‘none’: Cannot embed image. Images won’t be displayed on feature phone.” (NEO-12208)
  • The broadlog management has been improved for transactional messaging. When broadlogs are synchronized from the execution instance to the control instance, the @lastModified field is updated to the system’s current date. The MC_Update_BlLastModified option has been added for control instances. True means that the current date will be used on the control instance (default behavior). False means that we use the execution instance broadlog’s @lastModified date. (NEO-12579)
  • Indexes were added in the coupon temporary tables to optimize delivery sending. (NEO-12437)
  • In the Analytics integration, the retrieval of AAM segment data with % character is now allowed. (NEO-12025)
  • Removed the 10,000 record limit in Workflow Heatmap to fix a missing data issue. (NEO-12329)
  • Open Office is not supported and is now fully removed from the application. If you were still using it, move to Libre Office as it will not work anymore starting 19.1.
  • You can now limit Write access to Update data activity in Workflow using sysfilter attributes. Read more


  • Fixed an issue which prevented the certificate from being uploaded for iOS mobile push notifications.
  • Fixed potential recurrent server crashes for transactional push notifications. Other crash issues have been fixed.
  • Fixed an issue which caused reporting discrepancies between user activities and tracking reports for the open delivery indicator. (NEO-11742)
  • Fixed an issue with the IMS login.
  • Fixed an issue which could lead to missing images in a delivery when adding an image from the library. (NEO-11900)
  • Fixed an issue that could occur when extracting offer details in a direct mail delivery. (NEO-11700)
  • Fixed an issue that could affect SMS transactional message performance. (NEO-9812)
  • Fixed a console crash that could occur when using the Defined in an external file option for the main target of a delivery. (NEO-12349)
  • Fixed an issue when analyzing a message which targeted recipients for Japanese (.JP) domains. (NEO-12246)
  • Fixed a display issue when using a distribution of values with a 1:N link. (NEO-12212, NEO-11820)
  • Fixed an issue which could cause NmsMxDomain errors in the MTA logs after a postupgrade. (NEO-12752)
  • Fixed an issue when using the “Keep all additional data from the main set” option in an enrichment workflow activity. (NEO-13291)
  • Fixed a Tomcat crash issue when sending push notifications using HTTP2. (NEO-12701)
  • Fixed an issue with the HTTPRequest API which did not wait for all callbacks to finish. (NEO-12628)
  • Fixed an issue with the computing process of tracking indicators for transactional messages. (NEO-12529)
  • Fixed an issue with the use of themes in offer management. (NEO-11804)
  • Fixed a performance issue when sending push notifications. (NEO-11787)
  • FIxed an issue when previewing an outbound XML or CSV file in offer management for a direct mail delivery. (NEO-11290)
  • Fixed an issue when installing the Managing social networks (Social Marketing) package. (NEO-12081)
  • Fixed an issue which prevented you from deleting a web application even if you had the correct access rights. (NEO-12072)
  • Fixed an issue which could cause some values to be overwritten when exporting and then importing an object via XML. The XtkExport_IncludeDefaultValues option has been added. When set to True (default behavior), all values are exported. When set to False, modifications are overwritten with the default value. (NEO-11979)
  • Fixed an issue which caused the Alert workflow activity to fail when an enrichment activity was added after a query. (NEO-12132)
  • Fixed an issue on Oracle setups where pipeline (triggers) offsets were not retrieved successfully from the database causing duplicates. (NEO-12121)
  • Fixed an issue which could cause diplay errors in pivot tables when using the Analytics integration (NEO-12103)
  • Fixed an issue with the Descriptive Analysis report. (NEO-11414)
  • Fixed an issue with CRM connectors when the remote table contained a field with an underscore in its name.
  • Fixed a issue which could cause a display issue for currency symbols in the Hypothesis reports. (NEO-11634)
  • Fixed a redirection and tracking issue when using certain characters in tracking links.
  • Fixed an issue which prevented offer preview from working correctly.
  • Fixed an issue with soft bounces not being removed from the address table.
  • Fixed a JAVA error when using barcodes.
  • Fixed a translation issue in web applications (NEO-12460)
  • Fixed an issue with the s3 File Transfer workflow activity. (NEO-12473)
  • Fixed an issue with date fields in web applications. (NEO-12496)
  • Fixed an ID exhaustion issue when using seed addresses in a delivery. (NEO-11842)
  • Fixed an issue with phantomjs and Debian 9 compatibility.
  • Fixed an error when approving the content of a proof. (NEO-12725)
  • Fixed an issue with the “Exclude this subset from the population” workflow feature. (NEO-12441)
  • Fixed an issue with the HTTPRequest-wait API which did not wait for all callbacks to finish. (NEO-12628)
  • Fixed an issue with the “Update Shared Audience” task in a split activity. (NEO-11562)
  • Fixed a web server crash issue. (NEO-12904)
  • Fixed an issue with the Nature parameter in transactional templates. (NEO-12334)
  • Fixed a console crash issue when displaying the tracked URLs in the email text editor. (NEO-13122)
  • Fixed an issue with the Split File activity when importing audiences from Audience Manager. (NEO-11550)
  • Fixed an issue which caused errors in the hot click report. (NEO-11459)
  • Fixed an issue with offer rendering. (NEO-11565)
  • Fixed an issue with the List Update activity when importing audiences from Audience Manager. (NEO-11226)
  • Fixed an issue with the Schedule activity and time zone configuration. (NEO-11662)
  • Fixed an issue that caused the tracking workflow to fail in case of malformed URLs.
  • Fixed an issue with external accounts after importing the mobile application package.
  • Fixed an issue when assigning a time zone to an operator. (NEO-12464)
  • Fixed an issue which could cause errors in the mtachild logs. (NEO-11539, NEO-8978)
  • Fixed an issue when clicking the History icon in a saved report. (NEO-11620)
  • Fixed an issue when editing a pivot table in a report. (NEO-12068)

On this page