(Released December 3, 2013)
These release notes describe the new features included in version 7.5, in relation to the previous version of EPiServer 7.
EPiServer version 7.5 includes the following:
The new features included in version 7.5 of EPiServer Commerce, EPiServer CMS and the EPiServer platform are described below.
Catalogs are a central part of an e-commerce solution and in this version we have added an intuitive user interface for managing catalogs, based on the user interface introduced with EPiServer 7 CMS.
From the new Catalogs interface you can:
This allows for e-commerce managers to accommodate multiple stock locations by defining multiple warehouses and inventories, and to show product availability across all of these. The warehouse and inventory system can be extended and customized, or entirely replaced.
You can do the following:
The market features open up for targeted merchandising and a more personalized user experience by applying specific products, languages, currencies or promotions to selected customer groups.
With the new multi-market functionality you can do the following:
You can now add customer groups including both contacts and organizations. Both pricing and promotions that are targeted to specific contacts and organizations can be inherited by using customer groups.
A typed content model makes it quicker and easier to develop new sites based on inheritance and strongly-typed access to data and properties.You can use CatalogRouteHelper to register routes based on catalog hierarchy, and/or SEO URI information for catalog nodes and entries. With the routes enabled, it is possible to implement IRenderTemplate<T> to declare renderers for the built-in catalog content classes.
Partial routing makes it possible to extend routing beyond pages. In EPiServer Commerce, partial routing is now used for presenting catalog data for editing in the new Catalog editing interface, and for product and catalog references.
With this release, the EPiServer Find search provider has been included with EPiServer Commerce. This allows you to extend the built-in search to create advanced search options for navigating products on e-commerce websites.
The following has been improved to make it easier to install and configure EPiServer Commerce for multi-site environments:
A new sample site has been developed for EPiServer Commerce, with basic e-commerce functionality demonstrating the use of multi-markets and warehouses, multiple shipments and in store pick-up features, as well as the typed content model and responsive design using Bootstrap. The sample site is available in the installation package.
The fly-out editor has been removed for longstring and XHTML properties to make the editing experience more integrated. The property names are now also displayed when editing on the page by hovering the mouse cursor over the properties in question.
All content in the Pages gadget is shown by default when you switch to edit the website in another language. If you change language in the page tree structure, it will also change in the block folder structure. Other improvements have also been made for language handling, such as that for deleting language versions.
The reference dialog has been improved to be more descriptive regarding the consequences of removing folders with content, pages, blocks and media files.
Blocks and media files share the same folder structure in the assets pane.
The following predefined folders are available:
You can define display options for any content that is displayed within a content area. The display option makes it possible for editors to vary the design or layout of, for example, blocks that are placed on a page. For developers this means that you can define tags that can be selected by the editor and then define specific renderings for these tags. In the Alloy templates this is implemented to let the editors select from “full”, “wide” and “narrow” layout.
Click Create a new block in the content area, either when editing directly on the page or in the All Properties editing view. When you use this option, the block will be saved locally in the For this page folder for the selected page.
A link collection contains a group of links to content, for example, the footer on the start page of the Alloy templates. It is a quick way to add and rearrange links to pages, media, e-mail or external links. Pages and media on the website can be added through drag-and-drop to a content area.
Define Shell modules that this module has a dependency on on the client side by configuring module.config <moduleDependencies>/<add> Element attributes. The type of dependency has the following options (which can also be combined):
The new asset system is based on content types and is fully integrated with both CMS and Commerce, with possibilities to convert VPP resources to assets. Assets now include both blocks and media files (images, documents, videos), as well as products in the Commerce catalog. Access rights for all content types are managed from the CMS administrative interface, as with pages in previous CMS versions.
Some of the features in asset management:
Deploy sites simply by copying application files without any prerequisites on the web server (FTP deployment is supported). Supports both deployment in cloud environments and traditional deployments. NOTE that currently this feature only applies for CMS sites.
Some of the changes in the platform:
* The requirement on Windows Service’s scheduler is removed so that you can run a scheduled job without a Windows service. The scheduling logic has been moved inside the web application and both Azure websites and traditional IIS deployment are supported.
Support for running and deploying CMS in Azure and Amazon. As a developer you can now, for example, easily deploy CMS projects on Azure Web Sites backed by SQL Azure.
The new cloud providers for events enables elastic load balancing using cloud services. A new provider model is also available for storage of binary data (BLOBs) used by the new media system, the new cloud providers for BLOBs enables an efficient way of storing large data volumes in the cloud.
The following new providers will be released on the EPiServer NuGet Feed shortly after release:
As a developer you can now easily deploy CMS projects as Azure websites with SQL Azure, Azure BLOB Storage, and Azure Service Bus configured. The Azure Event provider is implemented to support elastic scaling in Azure.
It is now possible for webmasters to launch new sites, for instance for campaigns, directly from the CMS administrative interface without involving IT. The system will keep track of the license status and the number of launched sites.