At a Glance

Released on
End of Life
Issues Resolved
Customer Votes Satisfied

Next Release: 7.8
Previous Release: 7.4.1

Cascade Server 7.6

This release includes a new file creation and upload interface, the ability to include Velocity code from one Format in another Format, support for SQL Server 2012, and improvements to a number of existing features.

  View Requirements

File Upload Improvements

The File create and edit screens have been improved to allow for easier uploading and naming of Files in Cascade.  A new drag 'n' drop File upload "drop zone" has been added that allows users to drag files from their desktop directly into the Cascade interface.  The system name field for Files will now also be updated automatically to match the name of the file that is uploaded. While the file is being uploaded, a progress bar appears and submit buttons get disabled until the uploading process is complete.

This functionality has also been implemented for file upload fields in Templates, Blocks, Formats, Workflow Definitions, Data Definitions, Site Import, Site creation, Zip Archive tool and LDAP Configuration screen. The contents of Templates, Blocks, Formats, Workflow Defintions, Data Definitions and LDAP configuration will also be refreshed once a file has finished uploading.

File Upload UI

new file upload drop zone

Locator Tool: API Improvements

Improvements have been made to the Cascade Server API which make it easier to process assets retrieved using the Locator Tool when writing Velocity Formats.  It's now possible to:

  • Retrieve dynamic metadata fields by name
  • Retrieve a single dynamic metadata field value
  • Retrieve multiple data definition fields by name - This makes a huge difference when handling data definition fields that are declared as multiple="true"
  • Retrieve a child (or children) of a data definition group by name

See the Cascade Server API changelog for a more detailed description of changes.

Velocity Format Includes

It is now possible to include Velocity code from one Format in another Format.  Common Velocity macros and other general purpose code can now live in a single Velocity Format and be reused instead of having to copy and paste the same macros from Format to Format.  Headache eliminated!

Google Analytics Overhaul

The Google Analytics Connector has undergone some changes.  The connector verification process now requires that an access token be copied and pasted from Google into Cascade.  This is similar to how Facebook Connector verification works.

The Analytics Connector is also now more up-to-date with Google's Core Reporting API.

Important! All Google Analytics Connectors in Cascade will be automatically unverified on startup of 7.6 to force all Connectors to be compliant with the latest version of OAuth.  Existing analytics data for each connector will remain in the system and can still be viewed once a connector has been reverified.  See below for instructions on how to re-verify connectors.

Site Import/Export Performance Improvements

We have taken a look at the Site Import and Export tools to see where we could improve on memory usage, import/export times, and overall export size for larger Sites and have made some significant improvements.  Sites with a large number of files and large files in general will use significantly less memory during both import and export (Note that importing an export file that was created by a version of Cascade lower than 7.6 can still consume a large amount of memory).  Likewise the size of the export file for File-heavy Sites should also be reduced.  This alone speeds up the import and export processes, but other changes have also resulted in speed improvements.

SQL Server 2012 Support

SQL Server 2012 is now officially supported by Cascade Server!  See the Upgrade Guide for information about moving to SQL Server 2012.


  • [CSI-610] - Google Analytics Connector - Use OAuth2 for authorization and authentication
  • [CSI-611] - Support for SQL Server 2012
  • [CSI-614] - Velocity LocatorTool: API Improvements
  • [CSI-616] - Reorder hours drop-downs to start with 12
  • [CSI-620] - Allow users to import Velocity code from other Velocity Formats in Cascade
  • [CSI-621] - Reduce memory usage during Site Import/Export
  • [CSI-623] - Drag n' Drop and File Upload

Issues Resolved

  • [CSI-522] - Users can not save Drafts in parent Folders to which they do not have Write access
  • [CSI-533] - Update Google Analytics Quota Error Codes
  • [CSI-592] - Search and replace no longer finds search results
  • [CSI-615] - Unable to add special characters Dynamic Metadata Field configuration's values
  • [CSI-617] - Asset Factory Plugins + Auto-save as Draft strips file extension from uploaded files
  • [CSI-618] - No error message when submitting invalid XML within XML Block
  • [CSI-622] - Help id for recycle bin checker is incorrect

Re-verify Google Analytics Connectors

We overhauled our Google Analytics Connector in Cascade Server 7.6 to work with Google's new Core Reporting API v3. This included using OAuth2 to authorize and communicate with the API. As a result, users will need to re-verify their Google Analytics Connector to allow Cascade Server to access their Google Analytics data. 

  1. Visit each Google Analytics Connector in Cascade
  2. Click "Verify"
  3. Follow the prompts to authorize Cascade Server to access Google Analytics
  4. Paste the authorization code from Google's website into Cascade Server
  5. Complete the verification.

We're sorry about the inconvenience, but this will allow us to better handle errors and take advantage of higher rate limits as well as any new functionality that Google's APIs have to offer. Plus, they were removing the old API we were using :-).

Support SQL Server 2012 and Deprecated Support for SQL Server 2005

This release introduces support for SQL Server 2012. You'll need to upgrade to this version before attempting to run Cascade Server against SQL Server 2012. We recommend you upgrade using SQL Server 2005 or 2008, verify that the upgrade completes successfully, then move your database to SQL Server 2012 and verify that Cascade Sever can run against it.

We are announcing deprecated support for SQL Server 2005 in this release and will remove support for this version of SQL Server in an upcoming Cascade Server release.

Cascade Server Java API Changes

The Cascade Server Java API has changed and will require that all plugins be re-compiled against the latest version of the API.  While the API changes should be backwards compatible, it will be best to re-compile and test these plugins in a test environment before upgrading in production.

See the Cascade Java API changelog for details about what has changed.

Upgrade Steps

First Time Installation?

Be sure to import our default database schema prior to installing Cascade Server for the first time. Then follow our standard installation instructions.

Upgrade Steps

  1. Shut down your currently running Cascade Server instance.
  2. Before you upgrade, we strongly recommend that you back-up your production database. as well as set up a test instance and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.
  3. Read the release notes and upgrade guides for all releases between your version and the latest version.
  4. If your current version of Cascade is earlier than 7.0, then you must use the full installation instructions.
  5. If your current version of Cascade is 7.0 or later, you can perform a full installation or upgrade in place using the ROOT.war installation.


Organizations upgrading to 7.8.2 or above for the first time may notice a delay during the initial startup accompanied by messages like these in the log file:

2014-01-01 11:53:25,405 INFO  [OptimizeDatabaseServiceImpl] Clearing orphaned assets...
2014-01-01 11:53:25,405 INFO  [OptimizeDatabaseServiceImpl] Clearing orphaned Data Definition nodes...
2014-01-01 11:54:09,508 INFO  [OptimizeDatabaseServiceImpl] Deleted 7 orhpaned Data Definition nodes
2014-01-01 11:54:09,508 INFO  [OptimizeDatabaseServiceImpl] Repeating the operation until there are no more orhaned nodes to delete
2014-01-01 11:54:57,350 INFO  [OptimizeDatabaseServiceImpl] Deleted 14 more orhpaned Data Definition nodes
2014-01-01 12:02:30,529 INFO  [OptimizeDatabaseServiceImpl] Repeating the operation until there are no more orhaned nodes to delete
2014-01-01 12:02:58,724 INFO  [OptimizeDatabaseServiceImpl] Deleted 0 more orhpaned Data Definition nodes
2014-01-01 12:02:58,725 INFO  [OptimizeDatabaseServiceImpl] Finished clearing 224 orphaned Data Definition node record(s)
2014-01-01 12:02:58,725 INFO  [OptimizeDatabaseServiceImpl] Fixing Structured Data with missing owner entity property
2014-01-01 12:03:29,712 INFO  [OptimizeDatabaseServiceImpl] Found 211 broken Structured Data nodes
2014-01-01 12:03:32,451 INFO  [OptimizeDatabaseServiceImpl] Fixed a total of 9 assets with broken Structured Data nodes
It is important that the Cascade Server process not be stopped during this time. Once the orphaned Data Definition nodes have been removed, the application will start up normally.


If you are upgrading from Cascade Server 7.4.1 or later, you should rebuild search indexes after the upgrade is complete and the application is running. To do so, navigate to System Menu -> Utilities -> Search Indexing, check the Rebuild Index? checkbox and then click Submit.


You must upgrade to at least Cascade Server 5.5 before upgrading to Cascade 6 or Cascade 7.

Contact Hannon Hill Support ( if deploying Cascade Server for the first time in a load-balanced environment as this will require a special license.