HIPPO CMS and Hippo DX 11.1 Release Notes - BloomReach Experience - Open Source CMS

HIPPO CMS and Hippo DX 11.1 Release Notes

October 31, 2016


Hello everyone!


We are excited to announce the release of Hippo CMS and Hippo DX 11.1.

We decided to refer to the ‘Hippo Enterprise release’ from now on as ‘Hippo DX’. With this new name, we want to emphasize that the Hippo Enterprise release is much more geared to be a Digital Experience Platform than the powerful underlying CMS that we deliver as an open source community product. Things like content analytics and performance, relevance and experiments are features that reach well beyond the capabilities of a basic CMS, directly in the domain of digital experience platforms. We want to reflect this in the product name Hippo DX. The name of the community release will remain Hippo CMS (Community release).

After the successful release of Hippo CMS 11.0 GA last September, we have been working hard to create a follow-up minor release, incorporating new functionality as well as many usability improvements as a result of feedback we received from you.
For Hippo Enterprise Customers and Partners also a new Upgrade Verifier to upgrade from version 10.2.3 to 11.1.0 is available.

Hippo CMS and Hippo DX 11.1 contain new functionality and improvements, listed below in this message.

If you have any questions, don’t hesitate to contact us at [email protected]

On behalf of everyone that made this release a reality,


Mark Peerdeman

Product Management


New functionality and improvements

Channel manager (Hippo CMS and Hippo DX)

  • Channels now can be deleted using the Delete Channel functionality. The operation deletes the channel and a minimum set of associated data. As this operation cannot be undone we have built in several safeguards to prevent things going terribly wrong:

    • only users with administrator privileges are allowed to delete a channel

    • only channels explicitly marked deletable can be deleted

    • If a project requires the deletion of more than just the minimum set of associated data, it can subscribe to the BeforeChannelDeleteEvent and delete e.g. associated content or other data. This event can of course also be used to provide additional custom safe-guards.

  • The Edit Content button now provides a message when a document is opened for editing while a publication request is pending and opens it in view mode instead.

  • Logging out of the CMS now logs out preview sites in the Channel Manager as well.

Relevance (Hippo DX)

The Relevance module is majorly improved and extended after collecting customer requests and field information:

  • Characteristics now can be OR-ed. Besides the logical AND, the user now can also perform a logical OR between data collectors. This means that much more sophisticated characteristics expression evaluations can be performed in real-time when using the relevance engine.

  • Javascript goals. Next to the general purpose page goal, it is also possible now to use Javascript to score experiments goals. This means that anything you can Javascript can be used as a goal - so virtually anything. This feature is made available for developers to incorporate in their projects.

  • Trends facets now have a ‘Show more’ link to show more than the top 5 most popular facets.

  • The segments tab in the audience perspective is redesigned and improved. The definition of persona is optional now.

  • Consent cookie now can be set to provide a full opt-out of personalisation/relevance to be implemented easily in the project.

  • The default collector set now ships with often used basic data like days of the week and continent names.

Enterprise Forms (Hippo DX)

  • Enterprise Forms includes a new field type ‘anti-spam’ with options ‘slider’ (user action to unlock the form) and ‘honeypot’ (hidden by CSS). This makes it much harder for spammers to automatically submit forms.

For developers

  • Creating HST Queries just became a lot easier. We added the Fluent Query API, removing the complexity that was there with filters to construct queries. Constraints make queries much better readable, mandatory null checks are removed and varargs are used at many places.


Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?