Expand my Community achievements bar.

Announcing the launch of new sub-community for Campaign Web UI to cater specifically to the needs of Campaign Web UI users!

Introducing new Campaign Classic version: Adobe Campaign v7


Level 10

Here is an overview of the new Adobe Campaign Classic version: v7, which has been released on the 30th March 2017. To see the complete list of changes, consult the release notes.

v7 introduces a new major feature which will allow you to use Adobe Campaign Standard's Web interface, MTA and reporting capabilities, and much more. See below for more details.

Note: A new build has also been released for Adobe Campaign v6 (build 8795). You can consult the release notes here.


New features





User Interface

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

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.

For more information, refer to the detailed documentation.


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.


Technical evolutions




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.


Standard packages: for hosted instances, only Adobe Campaign administrators can now install standard packages.

Installation directory: you can now install both Adobe Campaign server and client on the same machine. Server’s default installation folder is now $PROGRAMFILES$/Adobe Campaign v7, while Client’s default installation folder is now $PROGRAMFILES$/Adobe Campaign v7 Client.

Build update

If you upgrade from Adobe Campaign v6 to v7, we recommend the following guidelines.

On Windows, for both the client and server upgrade, uninstall Adobe Campaign v6 before installing v7. Don't forget to back up your log and configuration files beforehand.

On Linux, for the server upgrade, remove the Adobe Campaign v6 package before installing v7.

More help?

Click here to view the list of all documentation updates.



0 Replies