Adobe Campaign Classic Legacy Release Notes

All the Campaign Classic v6/v7 fixes and updates prior to 2018

View Campaign Classic Release notes 2018 and later




The following releases concern Campaign v6 and v7.



  1. Campaign v6/v7 - 17.9.15 Build 8903

    Improvements

    • Fixed an issue with the Send Full Phone Number checkbox (SMS). (NEO-9366)

    • Fixed an issue with the parameter management for receiver and transmitter ports. (SMS)

  1. Campaign v6/v7 - 17.9.14 Build 8902

    Improvements

    • Email archiving logs have been enhanced, which makes it easier and clearer to check which emails have been successfully delivered or have failed through BCC archiving. (NEO-10675)

    • Fixed an issue which could prevent the Deliveries and Deleted Deliveries folders from being displayed in the console after a postupgrade. (NEO-11094)

    • Fixed an issue which could cause, in some cases, a portion of the delivery target to remain in Pending state. (NEO-11336)

    • The process for calculating SMS delivery indicators has been improved.

    • Fixed an issue with the tracking payload creation process (push notifications).

    • Fixed an issue which caused the direct mail hypothesis workflow to fail.

  1. Campaign v6/v7 - 17.9.13 Build 8900

    Improvements

    • Email archiving logs have been enhanced, which makes it easier and clearer to check which emails have been successfully delivered or have failed through BCC archiving. (NEO-10675)

    • Fixed an error with LATIN1 encoding when using an FDA Connection to a PostgreSQL database. (NEO-11299)

    • Fixed an issue that occured when using the Prepare the personalization data with a workflow delivery option. (NEO-11047)

    • Fixed an issue when using calculated fields in a Survey answers workflow activity. (NEO-11382)

    • Fixed a random issue causing the properties of a delivery to be wrongly overwritten. (NEO-11015)

    • Fixed an issue which led to the display of load balancer IPs instead of customer IPs in the tracking broadlogs. (NEO-11295)

    • Fixed an issue which displayed useless errors in the postupgrade log when a Survey answers workflow activity was not fully configured.

    • FDA Teradata: fixed an issue with auto-incremented fields and indexes in SQL tables.

  1. Campaign v6/v7 - 17.9.12 Build 8898

    Improvements

    • Fixed a postupgrade issue related to web applications. (NEO-11248)

  1. Campaign v6/v7 - Build 8897

    Improvements

    • Fixed an issue in the Survey Result activity when using data stored in XML. The report was displayed incorrectly. (NEO-10816)

    • Fixed a performance issue which could occur with the inMail process when using a bounce mail server. (NEO-10641)

    • Fixed a database upgrade issue which could occur when upgrading more than 1000 schemas. (NEO-10979)

  1. Campaign v6/v7 - Build 8895

    Improvements

    • Improved performance for large amount of data loading in Teradata and fixed an issue which prevented from displaying the right value of data processed in the log. (NEO-10429)

  1. Campaign v6/v7 - Build 8894

    Improvements

    • Fixed an issue with tracking logs not getting synched correctly from Message Center execution instance to control instance. (NEO-7286)

    • Fixed an issue with the Generate complement option in targeting workflow activities when using FDA.(NEO-9878)

    • Fixed a postupgrade issue to automatically install the Hive package (needed for Hadoop) if the FDA package is installed. (NEO-10592)

    • Fixed a regression in data management that prevented index creation on Enrichment-like workflow activities.

    • Fixed an encoding issue that prevented connection to Teradata.

  1. Campaign v6/v7 - Build 8893

    Improvements

    • Fixed an issue which duplicated logs in the deliveryLogStats table when sending android push deliveries. (NEO-10234)

  1. Campaign v6/v7 - Build 8892

    Improvements

    • Fixed an issue that could lead to truncated SMS when sending in a multi-part delivery. (NEO-10047)

    • Fixed an encoding issue related to SMS tracking on Android. (NEO-8679)

    • Fixed possible console crashes that could happen when using an SQL query. (NEO-9943)

    • The SMS log messages have been improved.

    • The Mblox connection SMS connection provider has been replaced with CLX Communications in SMS external account.

  1. Campaign v6/v7 - Build 8891

    Improvements

    • Fixed an issue which prevented from viewing the target of an outbound when using an FDA SQL database. (NEO-8924)

    • The ability for administrators to set or reset the password of any operator has been restored. To do this, right-click on an operator, select Actions > Reset password and set the operator's new password. We recommend that operators change their password when they first reconnect.

    • Fixed an issue with the web process connection. (NEO-10221)

    • Fixed an issue which could prevent the synchronization from Message Center execution instance to control instance from working correctly. (NEO-9800)

    • The broadlog management for email and SMS (legacy) connectors has been improved. A broadlog with an event date in the future is not updated. Only broadlogs for which the latest update occurred less than one month before the current date and time are updated. (NEO-9520)

    • Leads: fixed an issue which led to incorrect exports of elements with negative IDs to Salesforce because of duplicate key errors in workflows. (NEO-9031)

    • Fixed an issue with the delivery preparation when a quote was used in the image URL (NEO-9112).

    • Teradata support for FDA has been improved. Fixed index creation, timezone management and encoding issues. (NEO-10196)

    • Fixed an issue with the Message Center archiving workflow which could fail due to an incorrect check on Unicode data (SQL Server only). (NEO-7661)

    • Fixed an issue with the delivery indicators which were not always properly updated on mid-sourcing. (NEO-9307, NEO-9454)

    • Fixed an issue with the inMail process which could be blocked by inBound messages. (NEO-9530)

    • Fixed an issue which could prevent proofs from being sent in recurring delivery activities. (NEO-7975)

    • Fixed an issue which could prevent text-format proofs from being sent to seed addresses. (NEO-9728)

    • Now, irrelevant IMS errors ("Error during useIMS verification") do not appear in the web logs anymore. (NEO-6344)

    • Fixed an input form creation error.

    • Fixed an issue linked to the protection against direct file access.

    • Fixed an issue which caused throughput issues when using the BCC email archiving feature.

    • The last commit ID now appears next to the build number in the "About" window.

    • The SMS connector has been improved: tsLastModified and tsEvent are now updated when updating broadlogs.

    • TLS connection: SNI (Server Name Indication) is now supported.

    • Fixed an s3 bucket format convention issue.

  1. Campaign v6/v7 - Build 8889

    This build has been recalled. Please upgrade to the latest build or contact technical support.

    Improvements

    • Fixed an encoding issue with FDA on Linux (timestamp was not retrieved). (NEO-9954)

    • Fixed an issue which could cause random nlserver crashes on Oracle 12c when 64bit columns were retrieved by SQL queries. (NEO-8453)

    • Fixed an issue preventing from using the DaysAgo function when querying a Redshift database via FDA. (NEO-7099)

    • Fixed an issue when using workflow queries using xml/sql fields. (NEO-9858)

  1. Campaign v6/v7 - Build 8887

    This build has been recalled. Please upgrade to the latest build or contact technical support.

    Improvements

    • Fixed an issue that led the MS Dynamics CRM connector to fail to pull data for the first 7 days of month. (NEO-8803)

    • Fixed a MSSQL regression on index type creation (when used as main data base).

  1. Campaign v6/v7 - Build 8886

    This build has been recalled. Please upgrade to the latest build or contact technical support.

    Improvements

    • Fixed an issue with FDA over HTTPs when using Message Center in a hybrid architecture, leading to connection drop or loss of connection (timeout).

    • Fixed an issue which prevented content blocks from working with HTTP/HTTPS URLs.

    • Fixed a tracking issue when using custom parameters in URLs.

    • Fixed an issue with high volume SMS campaigns not being processed.

    • Fixed an issue which prevented the preview from working in AEM based deliveries.

    • Fixed an issue which prevented the SMS automatic reply function from working.

    • Fixed an incorrect index creation issue.

  1. Campaign v6/v7 - 17.9 Build 8883

    This build has been recalled. Please upgrade to the latest build or contact technical support.

    Improvements

    Functionality

    Description

    ACS Connector Enhancement (v7 only)

    It is now possible to send back behavioral data from Adobe Campaign Standard to Adobe Campaign 7, thus allowing marketers and data analysts to build a 360° view of marketing campaigns; create advanced audiences and segments that incorporate ACS behavioral data; and more effectively measure the ROI of marketing activities.

    SAP HANA connector

    ‪Break the silos and leverage all your external data ‪in ‪Adobe Campaign in real-time with Federated Data Access ‪connectors, now also supporting SAP HANA. Federated ‪Data Access ‪allows users to connect multiple disparate, ‪external ‪databases with Adobe Campaign. Query data in real-time from any source without importing ‪the ‪dataset or storing it within the Adobe Campaign platform.

    For more information, refer to the detailed documentation.

    Hadoop Connector via HiveSQL

    When it comes to handling large data sets, Hadoop has the advantage over relational database management systems, and its value for any size business will continue to increase as unstructured data continues to grow. Adobe Campaign can leverage the power of Hadoop through the Hadoop Connector via HiveSQL where customers can access schemas directly from the Adobe Campaign UI to create advanced, highly segmented audiences in fast, flexible, and scalable manner.

    For more information, refer to the detailed documentation.

    LINE Channel: Messaging Enhancements

    This enhancement to the LINE Channel will allow you to optimize cost efficiency by paying per campaign and not for each piece of content that is sent; increase user engagement by sending rich messages (not just flat images); and simplify usability with multi-messaging by not needing to create multiple deliveries for a single campaign.

    For more information, refer to the detailed documentation.

    Patches

    Platform

    • Fixed a navigation issue when logging in to the web interface via IMS.

    • Fixed an issue that led to errors when using VARCHAR2 fields with a length greater than 2000.

    • Secure mirror page URL: this update can generate errors when accessing mirror pages previously generated. For more on this, refer to the migration guide.

    Security

    • This release includes several security fixes.

    Delivery

    • Fixed an issue that displayed wrong figures in the Success column for SMS deliveries.

    • Fixed an issue that could prevent from sending SMS deliveries with the IMI provider when using the Extended generic SMPP.

    • Fixed an issue that could prevent from sending recurring SMS deliveries with the Digitonic provider when using the Extended generic SMPP.

    • Fixed an issue at the MTA level that could prevent from sending SMS deliveries when using the Extended generic SMPP.

    • Fixed an issue which could lead to a delay before deliveries are sent.

    • Fixed an issue which prevented simulations from being applied on campaigns.

    • Fixed an issue which prevented proofs from being sent when using filters in typology rules.

    • Fixed an issue which led to an error when adding delivery properties in a personalization block.

    • Fixed an issue which prevented inbox rendering from working for campaign workflow deliveries.

    • Fixed an issue which prevented to add a Javascript expression to the extract format of a direct mail delivery.

    Workflows

    • Fixed an issue with the Update aggregate activity.

    • Fixed an issue linked to the Restart the workflow from this task option.

    Push notifications

    • The senderId field was updated to 256 characters to follow Google's new standards.

    • Fixed an issue which prevented control groups from being used in push notifications.

    Web applications

    • Fixed an issue which prevented web tracking from working correctly in microsites.

    Social Marketing

    • Fixed an issue that could prevent the import of Facebook pages.

    ACS Connector (v7 only)

    • Fixed an issue which led to errors during the quarantine synchronization.

    Known issues

    Image changes

    For on-premise installations (IIS users), several images may be missing after the upgrade. The procedure to fix this is described in the Production guide.

    Client executable

    The client setup executable folder has changed and is now /usr/local/neolane/nl6/datakit/nl/eng/jsp

    Users upgrading the client console from 17.4 build to 17.9 via the update notification pop-up may experience an unexpected stop of the older console. This issue does not affect the proper installation of the new client console.

  1. Campaign v6/v7 - 17.4 Build 8863

    Builds 8797, 8850, 8853 and 8857 have been recalled. Please upgrade to the latest build or contact technical support.

    No improvements

    Patches

    Platform

    • Fixed an issue that could prevent users from accessing certain parts of the interface on low resolution screens (less than 1366x768). A scroll bar has been added for such resolutions.

    • Fixed client performance issues when using a proxy server.

    Security

    • This release includes several security fixes.

    • We have restricted web application access. Now, only administrators are allowed to modify, edit and publish a non-anonymous web application. Each time such a web application is previewed, the operator's credentials are asked.

    • The document preview in campaign management now only allows to preview images.

    • The Tomcat version has been updated to 7.0.73. You have to ensure that requests with HTTP method names that are not tokens (as required by RFC 7231) are rejected with a 400 response. For example, URLs containing the following characters need to be URL-encoded: ' ' (space), '"', '#', '<', '>', ' \\', '^', '`', '{', '|', '}')

    Delivery

    • Corrected an issue that could stop processing SMS SR, in some rare cases.

    • Corrected an issue which could prevent emails to gmail.com from being sent because of IPv6.

    • Fixed a crash that could occur when many JavaScript objects were used for the personalization of a delivery.

    • Fixed an issue that prevented deliveries from being sent when an SSL error occurred during the preparation.

    • Fixed an SSL issue that could occur during email TLS encryption.

    Leads

    • Fixed an issue where login credentials were asked when displaying the marketing history for leads in a CRM tool.

    Technical evolutions

    URL permissions

    We have limited the default list of URLs that can be called by JavaScript codes (workflows, etc.). To allow a new URL, the administrator needs to reference it in the serverConf.xml file.

    <urlPermission action="blocking" debugTrace="true">
    <url dnsSuffix="abc.company1.com" urlRegEx="https://.*" /> 
    <url dnsSuffix="def.partnerA_company1.com" urlRegEx="https://.*" /> 
    <url dnsSuffix="xyz.partnerB_company1.com" urlRegEx="https://.*" /> 
    </urlPermission> 

    Refer to the Security configuration checklist for more information.

  1. Campaign v6/v7 - 17.2 Build 8795

    New features

    Functionality

    Description

    User Interface (v7 only)

    Campaign v7 comes with a new user interface: home page, styles and icons have been updated and redesigned to improve visibility, navigation and consistency within the solution. Both console and web UI benefit from an improved user experience.

    ACS Connector (v7 only)

    ACS Connector offers a pre-connection between Adobe Campaign v7 and Adobe Campaign Standard. Available in the Adobe Campaign Prime offering, ACS Connector automatically replicates profile data to Campaign Standard, enabling marketers to create, personalize and execute campaigns through the intuitive web UI of Adobe Campaign Standard.

    Web API for Microsoft Dynamics

    The Web API connector can now be selected as a deployment type when creating a Microsoft Dynamics external account.

    For more information, refer to the detailed documentation.

    Email archiving BCC method

    You can now archive emails using a BCC address (invisible to the message recipients) to transfer an exact copy of the sent emails to a remote server. Archiving can only be enabled at the delivery level.

    For more information, refer to the detailed documentation.

    Amazon Simple Storage Service (S3) connector

    The Amazon Simple Storage Service (S3) connector can now be used to import or export data to Adobe Campaign. It can be set up in a workflow activity. The configuration is done in an external account.

    For more information, refer to the detailed documentation.

    Patches

    Platform

    • Fixed an issue that could cause IMS users to be frequently automatically signed out.

    Deliveries

    • Fixed an issue that could prevent from using the Display the HTML diagnostics option when editing a delivery.

    • The HotClick report now handles correctly personalized tracked URLs.

    • The Extended SMPP connector now supports the Service ID of mBlox. A new field in the external account allows to customize the Service ID tag.

    • Fixed and issue that could cause the connection to the Extended SMPP connector to close right after being opened.

    Workflows

    • Script and External task activities are no longer available for new wokflows.

    • Fixed an issue that caused the console to crash when using the Load All option of the last transition's detailed view in a workflow.

    Security

    • Web applications: to improve security, the webapp operator (Web application agent) no longer has administrator rights. By default, this operator now only has read and write access to the standard recipient and visitor folders. If you have folders linked to custom recipient tables, or if you add recipient folders in a different node of the explorer, you need to add the webapp operator in the Security tab of these folders. This applies to new installations only. If your instance is migrated from v6, the webapp operator will have the same behavior as before. The WEBAPP named right has also been added.

    • Improved security for file upload. It is no longer possible to upload files in forbidden system folders on the Adobe Campaign server.

    • Improved access controls to prevent arbitrary code execution and file disclosure.

    Connectors

    • Fixed an issue preventing from using text strings in query parameters in Teradata (FDA).

    • Fixed an issue that could prevent from bulk loading double type data via FDA.

    Technical evolutions

    Security

    Command restriction: several commands are now blacklisted and can no longer be executed using the execCommand function. An extra-security is provided by a new dedicated Unix user to execute external commands. For hosted installations, this change is automatically applied. For on-premise installations, you can manually set up this restriction by following the dedicated documentation. In addition, Script and External task workflow activities are no longer available in newly installed instances.

    Web applications: the v6.x web application rendering engine has been improved to fix a security issue. If some of your web applications are using the v6.0 rendering engine, we recommend that you update them to the v6.x one. The rendering engine is defined in the Rendering tab of the web application's properties.

    Web applications: to improve security, the webapp operator (Web application agent) no longer has administrator rights. By default, this operator now only has read and write access to the standard recipient and visitor folders. If you have folders linked to custom recipient tables, or if you add recipient folders in a different node of the explorer, you need to add the webapp operator in the Security tab of these folders. This applies to new installations only. If your instance is migrated from v6, the webapp operator will have the same behavior as before. The WEBAPP named right has also been added.

    PostgreSQL 9.6

    PostgreSQL 9.6 is now supported. For more information on supported systems and components, refer to the Compatibility matrix.

    More help?

    Click here to view the list of all documentation updates.

    If you have a question about Adobe Campaign, visit our forum and ask the community.



The following releases concern Campaign v6 only.



  1. Campaign v6 - 16.11 Build 8779

    Builds 8767, 8770, 8771, 8773, 8774, 8775 and 8776 have been recalled. Please upgrade to the latest build or contact technical support.

    New features

    Functionality

    Description

    Mobile App Channel improvements

    Adobe Campaign is now compatible with the Apple HTTP/2 protocol. The new HTTP/2 connector will also enable new use cases such as rich notifications (notifications including images, GIFs, videos, etc.) brought by iOS 10.

    For more information, refer to the detailed documentation.

    SMS channel improvements

    The customer experience with the SMS channel has been enhanced: a new connector allows greater compatibility with the SMPP protocol.

    For more information on the new extended generic SMPP connector, refer to the detailed documentation.

    End-User Behavioral Tracking Opt-out

    A new feature has been added in Adobe Campaign that enables Customer to stop tracking web behaviors of end-users who opt-out of behavioral tracking via cookies or web beacons.

    The feature includes the ability to display a banner on web pages to present the end-user with that option.

    Please note that some jurisdictions may require that Customer present end-users with an opt-in before an opt-out can be offered (or have other legal requirements), and it is Customer’s responsibility to comply with applicable laws.

    For more information, refer to the detailed documentation.

    Deliverability exclusion rules

    An encrypted global suppression list is now managed in the deliverability instance to avoid being blacklisted due to malicious activity, especially the use of a Spamtrap.

    For each email delivery, two default typology rules compare the recipient email addresses with the forbidden addresses or domain names contained in this list. If there is a match, that recipient is excluded from the target population.

    For more information, refer to the detailed documentation.

    Delivery monitoring

    Delivery monitoring allows you to receive email alerts on the statuses of your deliveries (progress, success, failure).

    This new feature is available through a package installation for all customers except on-premise. If you need this feature to be implemented on your hosted/hybrid platform, contact your Adobe Administrator or Consultant.

    PII view restriction

    Some customers need Campaign users to be able to access data records but do not want them to see Personally Identifiable Information (PII), such as first name, last name, email. Adobe Campaign proposes a new way to protect privacy and prevent data from being misused by regular campaign operators.

    For more information, refer to the detailed documentation.

    Patches

    General

    • Fixed an issue that led to the web server crashing when exporting a report to Excel.

    Deliveries

    • Fixed an issue that led to incorrect visibility conditions being generated in the content editor.

    • Fixed an issue that allowed the user to cancel or pause a delivery in read-only mode. Now an error message is displayed.

    Message Center

    • Fixed an issue that prevented the LINE Message Center template from being installed if the LINE package had been installed after Message Center.

    Interaction

    • Fixed a display issue that occurred when creating an Inbound Web offer space. After saving it, the displayed channel was incorrect.

    Workflows

    • Fixed an issue that caused an error when trying to view the distribution of values for a date/datetime field in the console (only occurred on build 8720 or later).

    Federated Data Access

    • Fixed several errors related to the Mid-sourcing workflow (FDA over HTTP).

  1. Campaign v6 - Build 8763

    Builds 8757 and 8758 have been recalled. Please upgrade to the latest build or contact technical support.
    Important note

    Third parties are now included in the main package. To install this new build, you first have to uninstall the third party package.

    New features

    Functionality

    Description

    Localization in Japanese

    Adobe Campaign is now available in Japanese. Just as for French, English, and German, the installation language is selected when creating the instance.

    We recommend using the client console in Windows 10 for Japanese instances.

    Certain special features linked to creating instances in Japanese (fonts and server encodings) are detailed in the installation guide.

    Channel: LINE

    A new communication channel is available: LINE. LINE is an application for free instant messaging, voice calls and videos. It is available on all smartphones (iPhone, Android, Windows Phone, BlackBerry, Nokia) and on PC.

    Important: If you use Message Center and you would like to install the LINE package, please use build number 8754. Otherwise, you can use build number 8753

    For more information, refer to the detailed documentation.

    Inbox Rendering

    A new Inbox rendering service is now integrated into the application allowing you to test the rendering of your emails.

    To use this functionality, follow the steps below :

    1. After editing your email content, click the Email rendering button available in the email delivery editing window.

    2. Click the Analyze button to start the Email rendering process for this email.

    3. Click the Email rendering tab to view the different renderings of your email.

    Note: the content and the target must be defined before clicking the Email rendering button.

    Email archiving

    This new functionality allows you to save an exact raw copy of the emails sent to your contacts, for archiving or regulatory purposes.

    Please note that these copies use up storage, which can lead to extra hosting costs for Managed Services and Cloud-Messaging deployments of Adobe Campaign. If you are running Adobe Campaign in this type of setup and would like to use this feature, please get in touch with your account manager.

    For more information, refer to the detailed documentation.

    Unique error codes

    Unique error codes have been assigned to all of the Adobe Campaign error codes. This means that when error messages in German or Japanese, for example, are sent to the Support service consultants, they will be able to understand them easier.

    Deliverability for Japanese ISPs

    Several improvements have been implemented to optimize the deliverability of Japanese messages, particularly concerning the tracking and encoding of email messages and addresses.

    For more information, refer to the detailed documentation.

    Push Notifications

    This version offers several new features concerning Push notifications:

    • iOS: you can now configure the title and the action button (right button) for Push notifications on iOS.

    • Android: the latest messaging engine from Google, Firebase Cloud Messaging, is now supported and allows you to send Push notifications on Android devices.

    For more information, refer to the detailed documentation.

    Personalizing emails

    A new option, Prepare the personalization data with a workflow, is now available from the Analyze tab of a delivery's properties.

    This option allows you to optimize the preparation of email sends by transparently pre-computing the personalization data. It is particularly useful if the data used for the personalization is linked to a targeting dimension, such as an external database (FDA), for example.

    Depending on your environment and your usual personalization processes, this option can result in significant increases in performance of up to 90% for preparing sends.

    For more information, consult the detailed documentation.

    Barcodes

    Aztec codebars are now natively supported by Adobe Campaign.

    Patches

    Platform

    • Corrected an issue which led to custom MX rules being reset during a build upgrade.

    • Several security improvements have been implemented. These are particularly significant for preventing scripts from being executed in text fields or certain types of files from being uploaded to the server (JSP, etc.). This change in behavior is only found on the new instances. This restriction can be modified using the uploadWhiteList of the Adobe Campaign server's configuration file.

    • Fixed an error that prevented 128 codebars containing a "%" character from working correctly.

    • Fixed an error that could prevent the Adobe Marketing Cloud resource selector from opening correctly when Asset on Demand was active on the tenant used.

    Workflows

    • Fixed an error that prevented any Change dimensions between two targeting dimensions containing sysFilters with a sub-query.

    • Fixed a problem that prevented a file on an external SFTP file from being deleted.

    Social

    • Fixed an error that could prevent a connection to Facebook from a dedicated external account. The connection used for sending real-time updates must now be executed in secured mode (HTTPS).

    Message Center

    • Fixed an error that prevented quarantines from being recovered from execution cells on a control instance.

    • Fixed an error that could sometimes indicate"click" events as "undefined" in the Message Center delivery tracking logs.

    Connectors

    • Version 37 of the Salesforce API connector is now supported by Adobe Campaign.

    • Fixed an error that prevented queries on an external Redshift database from working with the operators "Starts with" and "Contains".

    • The DB2 10.5 databases are now supported by the FDA option.

  1. Campaign v6 - Build 8724

    Important note

    To use this build, it is imperative that you install the latest version of the console.

    New features

    Functionality

    Description

    Netezza 7.2 FDA connector

    Netezza 7.2 is now supported by the FDA connector. When creating a connection to an external database via external accounts, you can configure access to a Netezza 7.2 database.

    For more information on connecting to an external database, refer to the detailed documentation.

    MS Dynamics Online CRM connector

    A CRM connector is now available to exchange data with Microsoft Dynamics Online.

    For more information, refer to the detailed documentation.

    Adobe IMS/SSO

    Integration with the IMS (Adobe Identity Management System) is now available for 'on-premise' instances. This means that users can connect to the Adobe Campaign console using their Adobe ID.

    For more information on configuring and using this functionality, refer to the detailed documentation.

    Assets Core Service and Profiles & Audiences

    The Assets Core Service and Profiles & Audiences are now available for 'on-premise' instances.

    Workflows: new icons

    The workflow activity icons were updated to make them clearer and easier to recognize.

    Third-party libraries

    The following libraries were updated:

    • openssl: 1.01s

    • libcurl: 7.46.0

    • libpq: 9.4.5

    • libssh2: 1.7.0

    • c-ares: 1.10.0 (Windows)

    Mobile applications channel (NMAC)

    Build 24 of Android and iOS SDKs is available. Contact technical support or your Adobe Campaign consultants to obtain it.

    If you want to use the "Bitcode" encoded version of the SDK for your iOS application, this is now also available.

    On iOS, silent push is now available to send "silent" notifications which do not generate alerts and are only displayed when the application is opened. For more information on this, refer to the detailed documentation.

    TLS Protocol

    The TLS Protocol is now supported for sending emails. A new column in the MX management allows for the expected TLS behavior for each domain to be defined.

    Patches

    Platform

    • Fixed an error that could prevent the nms:offerContext form from being modified or extended due to an unknown attribute.

    • Fixed an error that prevented filtering on an int64 type field if the numerical value entered contained less than 11 characters.

    • Fixed '404' errors that could be returned by the Adobe Campaign console on rare occasions.

    • Fixed an incorrect filtering error for the predefined filter Opened but not clicked, which also returned recipients that had clicked a link in an email.

    • Fixed an error that prevented LDAP connection when the Integration with the Adobe Marketing Cloud package was installed.

    • When the IMS connection fails due to a lack of rights for Adobe Campaign, the user is now correctly logged out and redirected to the login page.

    • Fixed an error that would force the user to close and restart the Adobe Campaign console when a session expired.

    • The Next results button is available again in the reports universe when a significant number of reports are available.

    • Fixed an error that could prevent Adobe Campaign from being installed on CentOS 7.2.

    Deliveries

    • The option Maximum number of SMSes per message is now available for SMS deliveries whose routing is based on a Netsize, SMPP, or Mid-sourcing account.

    • Fixed an error that could prevent a file created from the Data extraction (file) workflow activity from being sent as an attachment.

    • Fixed an error that could prevent a delivery from being created from the Adobe Campaign home page.

    • Fixed an error that could prevent the content validation email from being sent when the Enable proof sending option was enabled in a delivery's properties.

    • Fixed an error that could lead to an entire collection of Message Center events being rejected even though only a single entry was incorrect.

    Workflows

    • Fixed an error that prevented the Test to see if file exists option from working correctly with an SFTP external account. Even when the file was absent, the test would indicate that the file existed.

    • Fixed an error that could prevent the tracking technical workflow from executing correctly for an installation in MS SQL 2008.

    Social

    • An update was made to the functionality that exchanges data with Facebook to take into account the latest modifications made to the Facebook Graph 2.5 API.

    • Fixed an error that could prevent the technical workflow that calculates Facebook statistics from executing.

    FDA

    • Fixed an error that could prevent data from Adobe Campaign from being correctly inserted into an external Oracle 11g database (via FDA).

    • Improved the logout function: a field was added in the operator configuration screen. This field allows you to adjust the delay before the FDA session timeout.

    • Fixed an error that limited the number of records imported to 5000 when exchanging data with Microsoft Dynamics CRM 2015.

    Interaction

    • Fixed an error that prevented offers from being correctly published from an editing environment.

    Evolutions

    To allow for a more in depth analysis of delivery failures and for deliverability optimization, the MTA logs were enriched and their format was improved. The ncs/var/INSTANCE/log/mtachild.log file now contains all of the delivery logs. For each log, the following information is displayed:

    • Delivery ID

    • Recipient address

    • MX and IP address

    • Status

    • Failure reason, in the event that the delivery send failed

    The old logs are not affected by this improvement. The new format is only applied to the new logs. Here is an example of the new delivery logs:

    2016-03-21 11:58:15.582+01 00001D77  00001D77    1  info  nlmta Connection to inner-relay-1.corp.adobe.com[153.32.1.51]:25; to:<test@adobe.com>; deliveryId=6072; status:retry
    2016-03-21 11:58:16.266+01 00001D77  00001D77    1  info  nlmta Connection to inner-relay-1.corp.adobe.com[153.32.1.51]:25; to:<test@adobe.com>; deliveryId=32557; status:sent (250 2.0.0 u2LAwBRh028632 Message accepted for delivery)
    2016-03-21 11:49:57.330+01 00001AB7  00001AB7    1  error  nlmta Connection to inner-relay-3.corp.adobe.com[10.128.4.236]:25; to:<test@adobe.com>; deliveryId=5922; status:failed (550 5.1.1 <test@adobe.com>... User unknown)
    2016-03-21 11:58:15.582+01 00001D77  00001D77    1  warning  nlmta Cannot find a connection; to:<test@adobe.com>; deliveryId=6072 ; status:scheduled
    2016-03-21 11:58:15.582+01 00001D77  00001D77    1  warning  nlmta Message too old; to:<test@adobe.com>; deliveryId=6072 ; status:deleted
  1. Campaign v6 - Build 8705

    New features

    Functionality

    Description

    Sybase IQ 16 FDA connector

    Sybase IQ 16 is now supported by the FDA connector. When creating a connection to an external database via the external accounts, you can configure an access to a Sybase IQ 16 database.

    For more information on connecting to an external database, refer to the detailed documentation.

    Debian 8

    Debian 8 is now supported.

    For more information on supported operating systems, refer to the Compatibility matrix.

    Sending on Japanese mobiles

    Due to encoding incompatibility between DoCoMo and Softbank the Japanese format is now divided into three parts: deco mail (DoCoMo mobiles), raku deco (Softbank mobiles) and Decoration mail (KDDI AU mobiles).

    For more information, refer to the detailed documentation.

    Patches

    Platform

    • Fixed an error that could prevent the technical tracking workflow from executing correctly; tracking, delivery preparation and cleanup logs are now correctly saved.

    • Fixed an error that could cause deliveries to be duplicated in case of an MTA crash. A new retryLostMessages option in the mta node of the serverConf.xml file lets you resend after an MTA crash. This option is enabled by default and does not have any impact on the usual MTA behavior.

    • Fixed several errors that could lead to dysfunctions when using negative IDs.

    Deliveries

    • Fixed an error that prevented bar codes and QR codes from being displayed correctly in deliveries. This correction is already included in the 8691 patch of the 15.9 version of Adobe Campaign.

    • Fixed an error that could lead to erroneous results for the Response Manager functionality when sending SMS deliveries.

    Integrations

    • Fixed an error that prevented the Adobe Marketing Cloud asset selector from being used from a security zone whose sessionTokenOnly attribute was set to 'false'.

  1. Campaign v6 - Build 8687

    New features

    Functionality

    Description

    Adobe IMS/SSO

    Thanks to the integration with the IMS (Adobe Identity Management System), users can now connect to the Adobe Campaign console using their Adobe ID. For more information on configuring and using this functionality, refer to the detailed documentation.

    This functionality is only available for hosted instances.

    To use this functionality, it is imperative that you install the latest version of the console.

    AEM Assets

    You can now directly insert images from your AEM Assets library into deliveries and landing pages created from Adobe Campaign.

    For more information on configuring and using this functionality, refer to the detailed documentation.

    Profiles & Audiences Core Service

    The integration with Profiles & Audiences Core Service now allows data to be exchanged from any Adobe Campaign targeting dimension and the declared IDs are now taken into account. It is now also possible to define one data source per targeting dimension.

    For more information on configuring and using this functionality, refer to the detailed documentation.

    Predefined filters

    New predefined filters are now available.

    For more information on filters, refer to the detailed documentation.

    Microsoft Dynamics CRM 2015

    The Microsoft Dynamics CRM connector now supports the 2015 version of Microsoft Dynamics On Premise.

    The Claim-based mode is the only authentication mode supported.

    For more information on configuring and using this functionality, refer to the detailed documentation.

    Amazon Redshift FDA Connector

    Amazon Redshift is now supported. When creating a connection to an external database via the external accounts, you can configure an access to an Amazon Redshift database.

    For more information on the connection to an external database, refer to the detailed documentation.

    WPAD (Web Proxy Autodiscovery Protocol)

    The WPAD (Web Proxy Autodiscovery Protocol) is now supported by Adobe Campaign.

    To use this functionality, it is imperative that you install the latest version of the console.

    JS API

    New APIs are available for the MemoryBuffer object:

    • fromHexString.

    • toHexString.

    • hmac.

    For more information, refer to the JS API documentation which can be found in the download center of Adobe Campaign support.

    Third-party libraries

    The following libraries were updated:

    • PCRE library updated to version 8.37.

    • minizip library updated to version 1.1.

    • bzip library updated to version 1.0.6.

    Patches

    Security

    • The algorithm for encrypting operator passwords was improved (Windows, Debian 7, RHEL).

    • Operators (as well as their passwords) can no longer be imported and/or exported between two different instances.

    Platform

    • Fixed an error that was caused when a server URL ended with the / character.

    • Fixed a conversion error that occurred when exporting reports to Microsoft Excel.

    • Fixed an Aztec barcode generation error. The barcode displayed in an email delivery could be incorrect and different from the mirror page barcode, which was correct.

    • Fixed an error that could prevent an FDA query from being carried out if the query went through a non-FDA link first.

    • Fixed an error that allowed an operator to start or stop a read-only campaign.

    • Fixed an error that caused the server to stop when an error was transmitted.

    Deliveries

    • Fixed an error that could prevent certain numerical values from being rounded correctly in an email's content.

    • Fixed an error that could return incorrect results when using a randomly selected control group in Oracle.

    • Fixed an error that could lead to the failure to take into account the recipient changes that were not manually saved before sending a delivery.

    • Fixed an error that could prevent the proof status of a direct mail delivery from being updated automatically.

    • Fixed an error that prevented Chinese characters from being used in tracked links.

    • Fixed an error that could prevent a recurring delivery from executing in a workflow if a seed address was used as a main target and the seed target.

    • Fixed an error that could lead to the number of recipients being limited instead of the number of seed addresses in a workflow delivery, if the seed population was defined to be randomly selected and grouped by data.

    • Fixed the size limit for SMS messages sent using the mBlox connector. The limit of 160 characters per message is now correctly taken into account.

    Interaction

    • Fixed an error that prevented an offer from being forced using an enrichment activity in a workflow if the offer category contained more than 10,000 offers.

    • 'Float' data can now be used in the conditions to define an inbound interaction.

    • Fixed an SQL error that could appear when an offer analysis report was displayed.

    Message Center

    • Fixed an error that could cause a popup to appear stating 'Invalid SQL" when recipients with a non NULL value in the @account field were deleted.

    • Fixed an error that could prevent tracked URL information from being recovered.

    Workflows

    • Fixed an error that could prevent a workflow from executing if the reconciliation conditions were not correctly defined.

    • Fixed an error that could prevent a Cells activity from being executed if it is placed after another Cells activity and if a segment code is entered in both activities.

    • Fixed an error that could cause a technical workflow for processing deliveryMgt deliveries to be executed twice.

    Shared audiences

    • Fixed an error that could prevent lists linked to the same segment, but coming from different data sources, from being updated after an Adobe Marketing Cloud shared audience was imported.

    • Fixed an error that could prevent a list of recipients from being saved as an Adobe Marketing Cloud audience via a workflow if the nms:recipient schema was extended or contained additional columns.

    • Fixed an error that could lead to the Asset picker opening (Adobe Marketing Cloud assets) instead of the audience selector.

    CRM Connector

    • Fixed an error that could prevent exporting to a CRM software from functioning correctly for the CRM Connector activity in a workflow.

    • Fixed an error that could prevent certain columns from being mapped correctly when importing data from Microsoft Dynamics CRM to Adobe Campaign.

    Production

    • Fixed an error that prevented the database cleanup workflow from deleting the delivery logs of canceled deliveries.

    Migration

    • Fixed an error that caused the postupgrade on non-Unicode instances with Oracle to fail when migrating from a 6.0.2 database.

  1. Campaign v6 - Build 8664

    Patches

    Social Marketing

    • Facebook permissions were updated. The publish_stream permission is no longer usable and is replaced by publish_actions.

    Security

    • Proxy management in the security zones has been changed. Authorized proxies must now also be entered in the all subnetwork of the serverConf.xml file. For more information, refer to the documentation on managing proxies.

    Query editor

    • Fixed an error that limited the number of figures after the comma in double constants when they were used in a query editor condition.

    • Fixed an error that prevented the correct formatting for values with a comma.

    Interaction

    • Fixed an error that prevented an offer from being viewed when using the charindex function in an eligibility rule.

    Reporting

    • Fixed an error that prevented exporting an empty pivot table in Excel format.

    • Fixed en error that prevented filters from working correctly in the Tracking indicators report.

    Workflows

    • Fixed an SQL error that prevented doing reconciliation, based on a proximity score which was calculated from linked objects' attributes, in an enrichment activity.

  1. Campaign v6 - Build 8653

    This build has been recalled. Please upgrade to the latest build or contact technical support.

    Improvements

    Functionality

    Description

    Delivery confirmation

    A new Nms_ActivateOwnerConfirmation option allows you to authorize the operator in charge of the campaign to confirm sending the delivery, even though an operator (or group of operators) is already assigned to this task.

    By default, this option is deactivated and the operator in charge of the campaign can only confirm sending the delivery if no other reviewer is defined in the delivery properties. The option can be activated by changing the value to 1.

    Managing automatic replies via SMS (American regulation)

    The following procedure makes up part of the certification process carried out by American operators for marketing campaigns in the US. When subscribers reply to an SMS message that was sent to them via Adobe Campaign, and they use a keyword such as STOP, HELP, or YES, it is necessary to configure messages that are automatically returned. This procedure is now available in Adobe Campaign.

    Refer to the detailed documentation.

    Workflows guide available in German

    A beta version of the Workflows guide is now available in German. Please note that the screenshots have been taken from the English instance.

    Message Center - Archiving workflows

    To resolve a certain number of problems relating to performance and errors, the Message Center archiving process has been modified.

    In previous builds, archiving was carried out by seven workflows, available in the control instance.

    From this build, the control instance now has one archiving workflow per execution instance. These workflows are created from an archiving workflow template that is provided out-of-the-box.

    For new installations, this new mode replaces the old one. Refer to the Message Center guide.

    If you update from an older build, please read the following information carefully:

    • The old and the new mode are not compatible, you will have to choose which you would like to use.

    • The postupgrade does not imply an automatic switch over to the new mode. The old mode will work just as before.

    • The previous mode is no longer supported and no patch will be added to it.

    • Moving from the old mode to the new mode is detailed in the How to switch to the new Message Center archiving workflows technote.

    Security

    Added an Adobe Systems Incorporated digital signature in the Windows security window.

    Thirdparty

    This build requires third-party software version 8635.

    Patches

    Adobe Analytics Integration

    • Fixed an error that prevented the Adobe Genesis connector from sending delivery indicators to Analytics.

    AEM Integration

    • Added a default user for all HTTP requests to AEM.

    Campaign

    • Default year was changed for the new plans and programs.

    Data management

    • Fixed an error in the Deduplication activity that caused the activity to fail if no data was received from the inbound transition.

    Delivery

    • SMS: Fixed a regression that prevented an SMS source number from being sent.

    • Fixed an error that caused scheduled deliveries to be sent in an incorrect time zone.

    • Fixed an error that prevented the Hot clicks report from being exported in PDF.

    Digital Content Editor

    • Fixed an error that caused the content editor to switch to edit mode even if no modifications had been carried out by the user.

    Federated Data Access - FDA

    • Fixed an error that caused crashes when synchronizing delivery logs from the mid-sourcing platform.

    • Fixed an error that blocked workflows following a remote server connection problem.

    • DB2: Added an optimized mode as a connection option.

    Interaction

    • Fixed an error that prevented a delivery contained within a workflow, and which itself contained an offer, from being previewed.

    • Fixed an error with the go live process that randomly disabled online offers if more than 10,000 offers were available.

    Distributed Marketing

    • Fixed Start and Approve labels (campaign planning in Distributed Marketing) that were modified to Automatic start and Submit for approval.

    Message Center

    • Fixed an anomaly that prevented the workflow that updates event statuses from executing correctly.

    • Fixed an error that caused excessive CPU usage when synchronizing workflows.

    NMX

    • Fixed an error that caused JavaScript errors when filtering on dates.

    • Fixed an error that caused the search to fail when selecting a dimension.

    • Fixed an error that allowed the week filter to appear in places where it could not be used.

    NSM

    • Removed the Action section from Facebook deliveries.

    • Fixed an error that prevented video thumbnails from appearing in Facebook deliveries.

    Platform

    • Fixed an error that caused malfunctions once 1000 packages had been installed.

    • Fixed an error that caused conflicts when using blank spaces in PostgreSQL instances that had come from the 6.02 version.

    • Fixed an error that prevented the "revVisibleIf" attribute from working in schemas.

    • Fixed en error that prevented the AddDays and SubDays functions from taking into account the Day-Light-Saving time change in PostgreSQL.

    Profiles and audiences Integration

    • Fixed an error that prevented access to the Marketing Cloud when only the Profiles and audiences integration was installed.

    Reporting

    • Fixed an error that prevented the Reporting aggregates workflow from working correctly.

    • Fixed an error that prevented Android devices from being detected.

    Response Manager

    • Fixed an error that prevented the "Received on mobile" status from being taken into account during hypothesis computation.

    Shared Assets Integration

    • Fixed an error that resulted in delivery content being deleted once the user had canceled selecting a Shared Asset.

    • Fixed an error that caused images selected from the Marketing Cloud to expand out of their containers when editing the content.

    • Improved the user interface with the resource selector.

  1. Campaign v6 - Build 8635

    Improvements

    Functionality

    Description

    Integration with Adobe Experience Manager

    You can now create your email content in Adobe Experience Manager, all while using the data from your Adobe Campaign database, and import it into your deliveries. You can also create Adobe Campaign forms in Adobe Experience Manager.

    Refer to the detailed documentation.

    Integration with Adobe Target Classic

    You can now insert images dynamically computed by Adobe Target into your Adobe Camaign emails. This allows you to offer several versions of the same email by personalizing its content according to the criteria specified in Adobe Target segments.

    Refer to the detailed documentation.

    Integration with Adobe Assets Core Service

    You can now use images shared within Adobe Marketing Cloud in your email deliveries and your landing page Web applications in Adobe Campaign.

    Refer to the detailed documentation.

    Integration with Adobe Profiles & Audiences Core Service

    You can now import audiences that are shared within Adobe Marketing Cloud via the other solutions that you use, into Adobe Campaign.

    In the same way, you can export your recipient lists in the form of audiences using a new dedicated workflow activity. You can then reuse these audiences in your other Adobe Marketing Cloud applications.

    You can only import and export audiences that are made up of recipients.

    Refer to the detailed documentation.

    The implementation of this integration is performed by Adobe technical administrators. Please be aware that it is a complex process which can take some time.

    Compatibility extension

    • Added MS SQL Server 2014 support

    • Added RHEL/CentOS7 and Apache 2.4 support

    • Added support for Oracle 12c

    • MySQL database creation is no longer authorized. MySQL is only supported in v6.11 when migrating from a 6.02 or 5.11 version using this engine.

    SFTP

    It is now possible to create external SFTP accounts. The external SFTP accounts can especially be used in File transfer activities within workflows.

    Patches

    Platform

    • Adobe Campaign is no longer providing the GeoIP library by default.

    • Workflows: fixed an error that occurred when a comma was used in one of the fields in the Distribution of values window when editing a query.

    • Fixed an error that caused image corruption when an NTLM proxy was used.

    • Fixed an error that prevented new instances from being created.

    • Fixed an error that occurred when using 'bigint' fields with PostgreSQL.

    • Data management / Workflows: Fixed a 'Could not find valid path to mainTargetData' error when accessing additional data in an enrichment activity.

    • Fixed an error that caused the application server to stop when using the Restart workflow from this task option.

    Delivery

    • Fixed an error that could prevent the delivery indicators from being updated when at least one log contained an empty address.

    • Fixed errors in HTML delivery content that were due to the 'nl_' prefix being automatically added.

    • Aztec codebars can now be encoded in binary format (provided you have a license).

    Campaign

    • Improved performance of the cost calculation workflow.

    • Fixed an error that prevented a delivery's content from being submitted for approval again after having been rejected the first time.

    • Fixed an error that occurred when creating a plan from the web interface.

    NMAC

    • Fixed an error that occurred when sending an iOS notification via a proxy.

    • Fixed an error that could cause child MTA processes to crash when sending notifications via a proxy.

    • Connection to the APNS via proxy is now possible.

    Distributed marketing

    • Fixed an error so that proofs can be personalized in the context of campaign orders.

    Federated Data Access - FDA

    • Fixed an error linked to the TruncYear function in Teradata.

    Social Marketing

    • Fixed various errors linked to the Facebook and Twitter API updates.

    Leads

    • Fixed an error that prevented an index on a tracking log table from being created.

  1. Campaign v6 - Build 8622

    Improvements

    Functionality

    Description

    Japanese email format support

    The Japanese email format has been added to the functionalities in Adobe Campaign v6.11.

    To write a message to be sent to a Japanese mobile, you must first write the Japanese message during email personalization and then the standard HTML message second.

    In the HTML tab, the message structure can be as follows:

    <%
    // Here 3 and 4 represent Deco-mail and Decoration Mail email format
    if ( recipient.emailFormat == 3 || recipient.emailFormat == 4 ){
    %>
      Japanese message content
    <%
    }
    else{
    %>
      Message content 
    <%
    }
    %>                
                  

    You can manage the email format, it is linked to the recipient profile in the Email format field.

    When the message is being processed and sent, the Japanese content will be sent to a recipient with a Deco-mail or Decoration Mail provided in his profile.

    This new functionality is delivered with a typology rule named Decomail Check. This rule allows you to check that the delivery contains at least one recipient linked to the Deco-mail format to start a verification.

    In order to use this new rule, you have to manually link it to the default typologies.

    This email format has certain particularities and they are detailed as follows:

    • If the email content contains images then the "multipart/related" and "Upload images" options must be activated.

    • Images cannot contain links (href). The opens tracking therefore cannot function.

    • Two ways to access the diagnostic have been added:

      • The first is linked to the content editing window and can be accessed via the Preview > Details > Deco-mail diagnostic.

      • The second is accessed when sending a proof: if the recipient has been configured to receive emails in Deco-mail format then a diagnostic is started during the analysis.

    jap_feature.png

    Patches

    Main

    • Adobe Campaign is now compatible with Internet Explorer 11.

    Security

    • Interaction: fixed a potential 'Server-Side Request Forgery' problem.

    Platform

    • Fixed an error with outbound HTTP requests. This error could send the 'Content-Type' field in the HTTP header twice, potentially causing compatibility issues with some external systems.

    • Web Analytics: fixed an error that caused incorrect delivery statistics to be displayed in Adobe Genesis.

    • Web Analytics: fixed an error that occurred when sending indicators with labels containing an '&' character to Adobe Genesis.

    • Workflows: fixed an error that occurred when using the Limit the selected records and By data grouping options in a Split activity.

    • Data management / Workflows: fixed an error that occurred when enriching recipients with offer propositions.

    • MySQL: fixed a postupgrade error on MySQL databases.

    • Fixed an error that prevented the platform from working with a 64 bit DB2 database.

    • Workflows: fixed an error that could cause an Excel file to fail to load on non unicode SQL Server databases.

    • SQL Server: the database server time could be incorrect in SQL Server in "multi timezone" mode. This error has been corrected.

    Social Marketing

    • Fixed errors that could cause the workflow that computes Facebook statistics to fail.

    • Fixed an error that caused an incorrect computation of impressions and reactivity.

    • Fixed an error that prevented visitors from being retrieved when starting the workflow that computes Facebook statistics.

    Campaign

    • Fixed an issue that caused a campaign workflow to stop when there was too high a number of deliveries with the Retry in progress status.

    • Campaign Optimization: fixed an error that could prevent commercial pressure rule filtering conditions from being applied.

    • Campaign Optimization: fixed an error that could cause incoherent results for capacity rules with validity periods that exceeded 22 days.

    Delivery

    • Fixed an error that prevented an external delivery's last modified date from being updated once it had been canceled.

    Message Center

    • Fixed an error that prevented an error message from being displayed when the archiving workflow failed.

    • Fixed an error that caused the archiving workflow to fail on SQL Server when synchronizing with execution instances (SOAP mode only).

    • Fixed an error that caused the events processing workflow to fail when the event type contained single quotes.

    • Fixed an error related to the access rights of the default 'mc' operator.

  1. Campaign v6 - Build 8612

    Patches

    Main

    • DCE: fixed an issue that allowed a user to select an incompatible content template.

    Security

    • Added the X-XSS-Protection HTTP header.

    • Fixed a potential denial-of-service security problem when parsing an XML document.

    Platform

    • Fixed an error caused when duplicating a report.

    • Removed unused activation.jar and mail.jar files.

    • Updated third-party zlib (version 1.2.8) and libpng (version 1.2.51) libraries.

    • Workflows: fixed an error in workflows using sub-workflows.

    • Fixed an issue that caused the target analysis function to fail when running a 6.11 client with a 6.02 server.

    • Fixed an error that caused a stack overflow when displaying a workflow.

    • Web application: fixed an error for Web apps containing pre-loading with encryption and an invalid profile ID. The Web app was still started.

    • Fixed an error that prevented reports from being exported in PDF when the SSL V3 protocol was disabled.

    Campaign

    • Fixed an error that caused the download links of direct mail deliveries to be incorrectly displayed in the campaign dashboard.

    • Approvals: fixed an error in campaign workflows that caused deliveries to be sent before their content had been approved.

    • Campaign Optimization: fixed an error that prevented pressure rules to work correctly with households.

    • Approvals: fixed an error in the delivery dashboard that prevented the extraction file approval option from being displayed.

    • Approvals: fixed an error in the campaign workflows that prevented extraction files from being approved when a proof had been sent manually before starting a workflow.

    • Approvals: fixed an error that allowed a campaign manager to confirm starting a delivery even when that operator was not specified as the owner or reviewer of the campaign in question.

    Distributed Marketing

    • Fixed memory errors (out-of-memory) when approving orders.

    • Fixed 'Parameter 'id' is invalid or missing' type errors that occurred when approving a campaign package.

    • Fixed an error that allowed deliveries of local entities, that were linked to a collaborative campaign, to be prepared even though the delivery did not yet have the "Ready for delivery" status.

    Interaction

    • Fixed an error that would occur when creating an offer from the Campaign universe. Only offers based on the recipient table were proposed.

    • Fixed an error that prevented a space from being deployed online when an additional storage field was configured for the space.

    • Fixed an error that could cause the approval of an offer assigned to a group of operators to fail.

    Reports

    • NMX: fixed a JavaScript error that occurred when a report execution using a cube was canceled.

    • NMX: fixed an error that occurred when a pivot table column was extended.

    Delivery

    • Memory consumption optimization for MTA child processes.

    • Fixed an error that occurred when adding or deleting filter conditions in the send a proof screen.

    • Fixed an error that occurred when using the import HTML function in the text content of a delivery.

    • Fixed an SQL error that occurred when starting a delivery without a linked workflow.

    • Fixed an error that, in some cases, could lead to personalization information being deleted after a delivery analysis.

    Surveys

    • Fixed an error that prevented the user from making a multiple choice question mandatory.

    Message Center

    • Fixed an error that caused the Update event status workflow to fail on SQL server.

    • Improvement to stop the Update event status workflow from running multiple times in parallel.

    • Fixed an error that caused the archive workflow to stop on SQL server via FDA.

    Federated Data Access - FDA

    • Fixed an error that occurred when using the SQL database in FDA. The attributes recovered by the archive workflow are now those from the database rather than those corresponding to the configuration of the external account in FDA.

  1. Campaign v6 - Build 8601

    Patches

    Main

    • Client console: fixed an error that caused the client console to close when using a seed address with a dynamic condition.

    Platform

    • SQL Server: fixed a Modulo (Mod) function compatibility error with SQL Server.

    • Web Analytics: fixed an error that caused a display problem with the Tag attributes in a delivery's properties.

    • Fixed an error that caused 'handles' files to leak when starting external processes or NetReport calls.

    • Fixed an error that stopped the server from restarting when the restart time was set to 00:00:00 (UTC).

    • IIS: fixed an error that occurred when configuring IIS8.

    • Migration: fixed an error that prevented a user who had migrated from a version 6.02 (or earlier) from connecting to an instance on which non-standard SQL functions had been added.

    • Fixed a 'getMaxValue is undefined' error on certain reports using percentages.

    • Fixed an issue that caused errors to be incorrectly displayed in campaigns when using IIS8.

    • Migration: fixed an error that occurred when migrating to a version 6.11 on an instance with the Microsites module and using SQL Server.

    • Fixed an error that prevented custom non-E4X methods from being implemented.

    • Data management/workflows: fixed an error that caused a workflow to stop when copying a Split activity using the By data group (in %) option.

    Interaction

    • Fixed an error that caused the cleanup workflow to fail when an offer environment was incorrectly configured (no linked proposition schema). A warning is now displayed.

    • Fixed an error that caused the cleanup workflow to fail when an offer environment had more than 1000 offers.

    • Fixed an error that prevented the Charindex function from being used in the eligibility rules.

    • Inbound interaction: fixed an error with the LoadLibrary function that could cause the following type of errors: Cannot open file '/usr/local/neolane/nl6/deprecated/wpp /xtk/deprecated/xtk/js/common.js'.

    • Inbound interaction: fixed an error that made the engine unavailable when publishing an offer space.

    • Inbound interaction: fixed an error that prevented inbound interactions from working correctly for anonymous visitors.

    • Outbound Interaction: fixed an error that prevented offer links, inserted in a text format delivery, from being tracked.

    • Fixed an error that prevented an offer assigned to a group of users from being published, when using a distributed architecture.

    Delivery

    • Tracking: fixed an error that prevented tracking information from being correctly recovered from iPod devices.

    • Fixed an indicator calculation error that would occur when analyzing a delivery containing an empty seed address. A warning is now displayed.

    • Fixed an error that could cause deliveries to be sent more slowly.

    • SMS: fixed an error that could prevent certain SMSs from being processed when the platform was overloaded.

    • Fixed a targeting error that would occur when an exclusion was used in a target definition.

    Campaign

    • Fixed an error that prevented the target from being submitted in manual validation mode.

    • Response Manager: fixed an issue that caused errors or incorrect hypothesis results when using control groups.

    • Fixed an error that allowed a proof to be sent before the delivery was saved, in targeting workflows.

    • Fixed a 'NullPointerException' type error when using an invalid locale.

    Security

    • Various corrections to security related issues (captchas, predictive marketing, cube editing).

    • Added an SQL rights verification for the sqlSelect and application.getConnection functions.

  1. Campaign v6 - Build 8591

    This build has been recalled. Please upgrade to the latest build or contact technical support.

    Improvements

    Functionality

    Description

    Sender name personalization (SMS)

    If you use the Netsize connector, you can now personalize the name of the delivery sender using a string limited to eleven alphanumeric characters. The field must not be made up exclusively of figures. This functionality is available in the Delivery tab of the delivery properties (Sender address field).

    Please check the legislation in your country regarding changing the sender name. You should also check with your operator whether this functionality is offered.

    rn_SMS_sender_adress.png

    Patches

    Main

    • Corrected an error that caused the wrong filter options to be displayed when adding a filter on a date type field.

    Security

    • LDAP: the TLS certificate is now also verified in Windows.

    • API: fixed an error that could cause the server to crash when performing SOAP calls with empty parameters.

    • Interaction: deleted unused interaction.jssp file.

    • Various security-related corrections.

    Platform

    • Fixed an error causing the server to crash when the simultaneous connection threshold was reached.

    • Fixed an error that could prevent the PhantomJS process from stopping correctly.

    • Fixed an error that would hinder the use of integrated security with versions 10 and 11 of SQL Server clients.

    • Data management / Workflows: fixed an error that caused an SQL error when the result of multiple aggregates computed was empty.

    • Fixed an error that could cause the tracking workflow to crash when working on several targeting dimensions.

    • Fixed an error that caused the server to crash when executing an empty sub-workflow.

    • Fixed an error that caused SQL errors when adding personalized SQL functions.

    • Imports: fixed an error encountered when using advanced parameters in a file import: 'error while executing the method TestCalcField of service xtk:dataTransfer'

    • Data management / Workflows: fixed an error caused when using multiple aggregates on the same attribute but with different conditions in an enrichment activity. Changing the value of one of these conditions would lead to the value of the other conditions being changed.

    • Workflows: fixed an error that could cause a workflow containing a Survey responses activity to crash.

    • Excel Exports: fixed a cell formatting error encountered when exporting reports to Excel format.

    • Fixed a 'GetLogFileContent' type error encountered when displaying mta log files in the Monitoring universe.

    • DB2: fixed an error that could cause deleted data to be displayed.

    • Fixed an error in the generic query editor that would stop the value breakdown from being displayed on the proposition schema.

    Distributed Marketing

    • Fixed a contact date update error that caused an error during the analysis of a restarted delivery.

    Interaction

    • Fixed an error that prevented the interactiond -dump command from executing when the interactiond process was enabled.

    • JavaScript Integration (client side): fixed an error that caused JavaScript variables defined in the web page code to be overwritten when the same variable names were used in the JavaScript Interaction code.

    • Fixed a client console error that could occur when opening a delivery with offers when using a distributed architecture.

    Reports

    • Fixed an error encountered when using filters in the User activities report.

    • NMX: fixed a value grouping error encountered when using an enumeration as a dimension.

    Delivery

    • Email: fixed a display error on the mirror page of a proof encountered when validating the content of a delivery.

    • SMS: mBlox connector: fixed a compatibility problem between the mBlox connector and T-Mobile and Verizon operators.

    • SMS: Fixed an error that could stop SMS text messages from being received.

    Social Marketing

    • Fixed a bug that caused an SQL error encountered when analyzing a Facebook delivery.

    • Fixed an error that stopped visitor information from being recovered from Facebook.

    Marketing Resource Management

    • Fixed a JavaScript error encountered when using forums with Internet Explorer 9.

    Federated Data Access - FDA

    • FDA / Security: fixed an access rights verification error encountered when using FDA with the HTTP protocol.

    Evolutions

    The behavior of the Message Center routing hook has been modified. Three cases are now supported:

    • If the template returned by the hook corresponds to a template published on an execution instance, this template is used.

    • If the hook returns a string of empty characters, the standard routing is used.

    • If the template returned by the hook does not correspond with any template published on the execution instances, or if a JavaScript error occurs when it is executed, the event status changes to Event not covered and the message is not sent.

    The first two cases worked in the previous builds. The third case is now also supported.

  1. Campaign v6 - Build 8580

    This build has been recalled. Please upgrade to the latest build or contact technical support.

    Patches

    Main

    • We recommend updating the Adobe Campaign console.

    • API documentation for Adobe Campaign has been updated. If you have subscribed to this option, please use the latest version.

    • Updated version of OpenSSL (v.1.0.1h)

    • Updated version of the CURL library (v.7.37).

    Platform

    • Fixed a regression that authorized a delivery to be deleted in a folder in which the operator did not have the adequate permissions to do so.

    • Fixed an error that prevented a list from being created without specifying an expiration date.

    • FDA / Data management: Fixed an error that generated an incorrect SQL code when creating multiple aggregates from an FDA collection and filtering on this collection with the data previously collected via the mainTargetData link.

    • Migration: Fixed an error that occurred during migration from a v5.11 to a v6.11 that displayed the following message: "The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'neolane.NmsCountry' and the index name 'NmsCountry_labelDe".

    Campaign

    • Fixed an error that caused the Cost calculation workflow to fail after sending a proof.

    Message Center

    • Fixed an error that displayed the message 'Error while parsing XML string' when publishing a template that referenced an incomplete personalization block.

    Interaction

    • Fixed an error that automatically attributed parent folder permissions to production offer categories, without taking into account their own configuration.

  1. Campaign v6 - Build 8571

    This build has been recalled. Please upgrade to the latest build or contact technical support.

    Patches

    Main

    • Fixed an error that resulted in a console crash when accessing a workflow containing a Union activity whose incoming transitions reference no schema.

    • DCE: Fixed an error that impacted visibility condition definition.

    Reports

    • NMX: Export buttons deleted in the client console.

    Interaction

    • Inbound: Fixed an error that prevented links to offers being tracked in text-format deliveries.

    • Outbound: Fixed a regression that prevented Interaction from working correctly in outbound mode when the offer space ID key was a string.

    Federated Data Access - FDA

    • Oracle / Mid-sourcing: Fixed an error that resulted in the failure of the workflow responsible for archiving FDA broadlogs when multiple deliveries on different mid-sourcing instances had the same ID.

    Distributed Marketing

    • Fixed an error that prevented a collaborative campaign (by target approval) workflow that contains a Local approval activity from working correctly when the 'Processing expected' option was activated.

  1. Campaign v6 - Build 8563

    This build has been recalled. Please upgrade to the latest build or contact technical support.

    Patches

    Main

    • User Interface: Fixed an issue that caused an extra comma to be displayed for large negative numbers (on int64-type fields). Requires a client-console upgrade.

    • User Interface/Workflow: Fixed an issue that caused an 'element is duplicated' error message when copying/pasting activities in between workflows.

    Platform

    • Fixed a regression that prevented use of 'Fast Forward Cursors' in SQLServer and impacted performance.

    • Fixed an issue that prevented a user from saving a delivery when an access right filter (sysfilter) was defined on deliveries.

    Delivery

    • Fixed an issue related to proof targeting that resulted in bulk deliveries being sent. Now, when a delivery's proof target is undefined, an error will be displayed during analysis.

    • Fixed an issue that caused an error message during delivery execution when an access right filter (sysfilter) had been defined on the external account schema.

    • DCE: Fixed an issue that prevented inserting a personalization block in a delivery content by double-clicking.

    • User Interface: Fixed a regression that prevented the recipient column displaying by default when displaying a delivery's tracking logs.

    Federated Data Access - FDA

    • Teradata: Fixed an issue that prevented Teradata UUID-type fields from being written. Added support for UUID fields for table creation for all database engines.

    Reports

    • NMX: Fixed an issue that caused an error when displaying an NMX report using a measure from a schema linked to the cube's schema.

    Interaction

    • Fixed a regression that prevented previewing a campaign delivery from a seed address and when the delivery contains offers.

    • Outbound: Allow storage of the offer proposition rank when calling Interaction from an enrichment activity.

    Distributed Marketing

    • Fixed an issue preventing the Distributed Marketing sample package (centralLocal.xml) from being imported.

    Leads

    • Fixed an issue that caused a 'duplicate id error' type error in SQL Server. 'Negative IDs' are now supported.

  1. Campaign v6 - Build 8552

    This build has been recalled. Please upgrade to the latest build or contact technical support.

    Patches

    Main

    • German: Fixed an issue that caused text to be truncated in the German installer.

    • User interface: Added a missing option to include or exclude sub-folders when filtering on a folder.

    • User Interface: Fixed an issue that prevented filtering by folder from working in overview lists.

    • User Interface: Fixed an issue when displaying objects with long labels in lists.

    • Documentation: Fixed a typo in the documentation of the formatDate API.

    Platform

    • Fixed an issue that caused an SQL error when saving a recipient record when there was a filter on both the folder and recipients belonging to a list.

    • Fixed an issue that caused possible encoding issues in Linux.

    • Fixed a regression that caused imports to fail when using load balanced servers.

    • Fixed an issue in the distribution of values when using several intermediate tables.

    Delivery

    • Fixed an issue that caused the spam checking to fail when using Spam Assassin 3.4.

    • Fixed an issue that impacted targeting when using the 'By Subscriptions' filter twice and with an exclusion in the target definition.

    NMAC

    • Fixed an issue that caused some English error messages to be displayed in non-English instances.

    SMS Channel

    • Mid-Sourcing/SMS: Fixed an issue that prevented use of several SMS messages for a single message in a mid-sourcing environment.

    • Delivery/SMS: Increased the verbosity of debug logs for inbound SMS.

    Microsites

    • Fixed an issue that caused the 'pURL publication successful' message to appear several times.

    Reports

    • Platform/NMX: Added technical troubleshooting logs in workflows generated by NMX.

    • Platform/Reporting: upgraded charting library Highcharts from version 3.0.7 to version 3.0.10.

    • Reports: Fixed an issue that caused some report categories to be missing from the report list.

    • Reports: Fixed an issue that caused the report legends to be incorrectly displayed in the "opens by user agent" report.

    NMX

    • Fixed an issue that caused long German strings to be truncated in the dimension configuration.

    • Fixed an issue that caused a javascript error when viewing an NMX report.

    • Fixed an issue that prevented the coloring of cells in a pivot table from working.

    • Fixed an issue that prevented filtering on date dimensions with the weekly filtering level activated.

    • Fixed an issue that let a user delete a measure, even if it was used as part of computed measures.

    • Fixed an issue in NMX reports that prevented the use of aggregates containing computed measures.

    • Fixed an issue with NMX report units exported in Excel.

    Message Center

    • Added an optional aggregate on Message Center archived event reports.

    • Fixed an issue (in a configuration with multiple control instances) that prevented the event history logs for one control instance from being synchronized with another when using the FDA synchronization option.

    • Fixed an issue (in a configuration with multiple control instances) that could lead to an incorrect template being used on the execution instance.

    • Fixed an issue that prevented Message Center deliveries from being cleaned up. They are now cleaned up after 7 days (max. limit).

    • Fixed an "invalid argument" type error when calling the PushEvent table from a JavaScript code.

    • Fixed an issue that caused an error when synchronizing events from a 6.1 execution instance and a 6.02 control instance.

    Distributed Marketing

    • Fixed an issue that caused inconsistency between labels used for campaign orders.

    • Fixed an error that caused an unrelated warning to be displayed when canceling a package.

    Security

    • Platform: Fixed an issue that caused random authentication failures.

    • WebApp: Fixed a regression that prevented anonymous web applications from working.

    Federated Data Access - FDA

    • Data Management: Fixed an issue that prevented writing in a table using Netezza.

    • Teradata: Fixed an issue that caused an error with the enrichment activity on Teradata when no sorting option is defined (Teradata requires the sorting to be defined).

    • Mid-Sourcing/FDA/Oracle: Fixed an issue that caused the delivery log synchronization to fail and 'duplicate key' errors when using Oracle and the FDA synchronization mode.

    Campaign

    • Fixed an issue that allowed a user to send a delivery without approval after the content was rejected.

    • Fixed an issue that caused an out of memory error in the operation management workflow.

    • Campaign Optimization: Fixed an issue with the 'Limit the deliveries' option in Campaign Optimization.

    • Campaign Optimization: Fixed an issue that cause incorrect indicators.

    Installation

    • Server Setup: Fixed the setup program by automatically creating a 'customers' folder when installing the Windows Server.

    • Instance Setup: Fixed an issue that caused an error when installing Campaign Optimization after Campaign and Interaction had been installed.

    Interaction

    • Fixed an issue that caused delivery exclusions for people not eligible for an offer to be incorrectly reported.

    • Fixed an issue that required an offer designer to have workflow access rights to validate an offer.

    • Fixed a regression that caused an error during an offer preview when an identification key was defined in the offer space.

    CRM connectors

    • Fixed an issue that prevented importing long text type fields through CRM connectors.

    Social Marketing

    • NSM/Facebook: Fixed the way we retrieve friends' names in Facebook.

    • NSM/Facebook: Fixed an issue that caused 'Couldn't verify signed_request from Facebook' error when synchronizing data from Facebook.

  1. Adobe Campaign

    New in Adobe Campaign 6.11

    Functionalities

    • "Neolane" is now "Adobe Campaign". This change is reflected across the entire application interface. The client console must be updated.

    • Integration with Adobe Experience Manager: Create email contents in Adobe Experience Manager and use these contents in your Adobe Campaign deliveries.

    • Translation of Web applications: Translate the content of your Web application pages created using the DCE.

    • Distributed Marketing: The Distributed Marketing option has evolved and now offers new functionalities, particularly concerning the types of operations available, validating campaigns, and localization.

    • Offer management: Use the weight and rank of offers in a workflow with the Enrichment activity.

    • New Message Center reports: Ensure the Message Center execution instances work correctly using the two new reports, Message Center service level and Message Center processing time.

    • Export reports: Export data from reports to Excel 2007 simply.

    • Enumerations in reports: Improve report relevance and readability by creating specific enumerations.

    Security

    • Security zone: Configure security zones so that they directly take into account the IP addresses of clients of a proxy.

    • Protect out-of-the-box schemas and system filters: Manage the read and write rights of schemas using the new readAccess and writeAccess filter system. In addition, certain out-of-the-box schemas can now be modified but solely by operators with admin rights.

    • Limit to the number of uploadable files: Limit the types of files that can be uploaded to the Adobe Campaign server using a new uploadWhiteList attribute. This can be used in the server configuration file.

    Technical evolutions

    • Acces to public pages: A new parameter, httpAllowed, is available in the relay rules. It allows you to authorize access to certain pages via the HTTP protocol.

    • Managing public resources: Synchronize public resources on several spare servers.

    • : Several improvements allow for a more thorough use of an FDA, particularly the possibility to create temporary schemas, etc.

    • Web app tracking: Follow and measure visits carried out on a Web application's pages by inserting tracking tags. In the previous versions, this functionality was not available for 'Microsite' Web applications. It can now be implemented for all types of Web applications (forms, online surveys, web pages created via Digital Content Editor, etc.).

    • Migration tools: Measure the impacts of migrating and identify potential problems using the new options that can be executed in the config command or at the postupgrade.

    • User passwords are no longer stored in the xtk:sessionInfo schema.

    • Users that have no rights can no longer connect to Adobe Campaign. They need to manually be assigned rights, for example, by creating a right named connect.

      The users impacted by this modification are identified and listed at the postupgrade.

    • The tracking no longer works if the password is empty. If this is the case, an error message will inform you of this and will ask you to reconfigure it.

    • The ooconv.jsp file, used to convert documents to PDF format, can no longer be called via apache/iis.

    API and functions

    • A new API named KillSession allows you to immediately disconnect the operator in question when modifying an operator from the console's administration interface.

    • The function xtk:builder:GetDbParams no longer returns the database password.

    • The function xtk:builder:CleanSqlTable was deleted and can no longer be used.

    • The administration rights are now required to be able to use the xtk:builder:EvaluateJavaScript and xtk:builder:EvaluateJavaScriptTemplate functions.

    • The unknown functions are no longer processed by the database engine if the SQL Injection mode is disabled.

      For example, when using the expression editor in the generic query, all unknown functions will result in an error.

      Nevertheless, you can add custom functions so that they are recognized and therefore executed correctly. To do this, refer to the Configuration guide.