Dev GuideAPI ReferenceUser Guide
HomeDev GuideRecipesAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunityOptimizely AcademySubmit a ticketLog In
Dev Guide
GitHubNuGetDev CommunityOptimizely AcademySubmit a ticket
Start typing to search…

Preview 4 release notes for CMS 13 pre-release

Explore detailed release notes for features in CMS 13 pre-release preview 4.

CMS 13 pre-release Preview 4 introduces a new .NET SDK for Optimizely Graph, REST API improvements, Visual Builder enhancements, and configuration updates across content management, hosting, and administration.

📘

Note

Preview 4 includes all functionality delivered in Preview 3 and Preview 2. This release adds further enhancements, stability improvements, and fixes on top of the previous previews.

Summary of changes by area

Optimizely Graph C# (.NET) SDK (early access)

New C# (.NET) SDK for Optimizely Graph, which provides a fluent API for querying content directly from C# code, similar to Optimizely Search & Navigation. The SDK supports searching on specific fields with boosting, filtering, pagination, and facets, and deserializes results into strongly-typed content models.

  • Added new Fluent API for building and executing Optimizely Graph queries, including field-level search with boosting, skip and limit pagination, and facet support.
  • Added the ability to cache Optimizely Graph query results with support for custom cache eviction policies.
  • Updated authentication and authorization to use a single key by default and have the option to opt-in Basic authentication per query, including support for IPrincipal and options to include deleted content.
  • Added tracking support for Optimizely Graph queries.
  • Added extensibility points in ContentGraph.CMS to enable extensions such as Graph.Commerce to build on top of the Optimizely Graph integration.

CMS REST API (early access)

See the early access API reference documentation.

  • Added the new experimental Application Management API exposing full CRUD and list operations for CMS applications (websites and headless websites) under /_cms/v1/experimental/applications, supporting both inProcessWebsite and website types with change tracking headers (ETag, Last-Modified) and precondition support.
  • Added the CMS REST API as a default inclusion and configuration in CMS 13 projects through AddCms(), with OAuth client configuration available through appsettings.json or environment variables on DXP.
  • Added validation for choice properties of type select list or drop-down list against their defined values when set through the API.

Visual Builder and content editing

Improvements to Visual Builder navigation and content modeling.

  • Added automatic updates to the selected item in the content tree when navigating inside preview for both in-process and headless websites in Visual Builder.
  • Added support for defining content type contracts as .NET interfaces inheriting from IContentData, enabling PaaS developers to model shared contracts through a new property on ContentTypeAttribute and use contract types in AllowedTypesAttribute.
  • Merged UploadOption and MediaFileOptions and moved them from EPiServer.Cms.Shell.UI to core. Marked the old option as obsolete.

Applications and host management

  • Added automatic migration of SiteDefinition settings to in-process web applications when upgrading to CMS 13, including site-specific assets, hostnames, and wildcard hostname handling.

Admin and configuration

Updates to license management, language settings, and module configuration.

  • Added a tooltip to the Cloud License tab that lists active server names for each URL on hover, with a detailed dialog available on click.
  • Added global fallback languages to the admin UI, previously hidden behind a feature flag.
  • Removed Content Manager and Content Graph from AddCms(). You must install each as a separate optional package.

Optimizely DAM integration

  • Added Optimizely Digital Asset Management (DAM) integration as a separate NuGet package (EPiServer.Cms.DamIntegration.UI), enabling the embedding of DAM directly in CMS 13. This integration requires Opti ID, an active Optimizely Graph service enabled through the DXP Management Portal, and CMP API client credentials configured through DamUIOptions and CmpClientOptions in code or appsettings.json.

Known issues

Upgrading to CMS 13 pre-release Preview 4 from certain versions of CMS 12 may result in an error. To avoid this, first upgrade to the latest version of CMS 12, then upgrade to CMS 13 pre-release Preview 4. This issue will be resolved in the CMS 13 release.

Updated 11 days ago