Previously, these Conversion Optimization-related workflows created through Marketer MCP or Agent API could encounter issues. As a result, personalizations and experiments created through these tools did not appear in the SitecoreAI UI.

What changed

With this update, related requests now use the appropriate service, so personalization and A/B/n testing workflows created through Marketer MCP or Agent API appear correctly in the SitecoreAI UI.

Impact

• SitecoreAI users can now create and manage personalization and A/B/n testing workflows through Marketer MCP and Agent API.

• Personalizations and experiments created through Marketer MCP or Agent API now appear correctly in the SitecoreAI UI.

• Users of the standalone Sitecore Personalize product are not affected.

• You can still access site settings using the existing method by clicking Options > Settings on a site tile in Channels.

• You can now open site settings directly from the Dashboard by selecting the Settings tab.

• The Open Settings button that previously opened a separate window has been removed to streamline the experience.

What you asked for - now in Page builder

• Custom Editing Interfaces
  You wanted more flexibility for business-specific fields. With Marketplace Custom Fields, developers can now create tailored UI components and rendering parameters directly in Page builder.

• Modern Developer Experience
  You needed a faster, cloud-native foundation. The Content SDK replaces legacy approaches with a stable, scalable platform. Combined with Local Editing Host and optimized architecture, it allows developers to build enterprise-grade pages up to 3× faster.

• Inline Editing & Content Management
  You asked for smooth inline editing. Page builder now offers an enhanced floating panel with inline text editing, configurable toolbars, direct item editing, and drag-and-drop component management all without leaving the canvas.

• Clarity in Page Structure
  You wanted visibility into how pages and components are organized. With Layers, you can now visualize and interact with page hierarchy in a clear, structured way.

• Personalization & Testing
  You asked for integrated optimization tools. Page builder now brings personalization and A/B testing directly into the canvas, with analytics built into the authoring flow.

• Content mode 
  A full‑screen experience for creating, finding, and editing content without switching to Content Editor was needed. Content mode provides a fast, distraction‑free way to work with pages and content items, including datasources, using guided creation and powerful search.

• Publishing/unpublishing enhancements
  You need greater control and improved visibility to help control publishing and unpublishing in Page Builder to give clearer control and confidence over what is live. Authors can now unpublish pages directly from Page builder to quickly take content offline without deleting it, while keeping all versions intact for future reuse. New publishing status badges make it easy to see at a glance whether a page or version is draft, approved, live, or scheduled, reducing guesswork and unnecessary tool switching.

What This Means

With these capabilities in place, Page builder now covers everything you previously relied on Experience Editor for and more.

 Note that if you are still using JSS in chromes mode, you will effectively loose your only WYSIWG Editor as Page builder only supports Metadata Mode.

 We encourage all teams to begin transitioning to Page builder now. The Page builder readiness recipe, associated documentation, and support channels are ready to help ensure a smooth move.

Use Content mode instead of Explorer

You can use Content mode to perform the most common Explorer workflows, including: 

• Creating pages, folders, and content items using guided insert options

• Finding content through fast, flat search rather than browsing a deep tree

• Opening content items directly in a full‑screen editing experience

• Searching within an item to quickly locate and edit specific fields

Content mode is optimized for speed and scale and reduces context switching by keeping creation, discovery, and editing in a single focused Page builder experience.

What this means for existing users

If you currently rely on Explorer:

• There is no immediate action required, but we recommend transitioning everyday content authoring workflows to Content mode.

• Some advanced or administrative scenarios may still require Content Editor, depending on your setup and roles.

Content is now labelled with clear status indicators, including live, scheduled, no workflow, draft, and approved. These labels are visible across key areas of the authoring experience, including the version drop-down, the page items context panel, the page references view used for publishing, and the right-hand panel.

In addition, you can now also create a new content item version, and update its workflow state directly from the right-hand side configuration panel.

These enhancements provide greater transparency into content status and behavior, improved accuracy when publishing or updating content, and increased confidence in what will appear on the live site.

• Updated serialization handling in a number of system components.

The latest release of the SitecoreAI base image 1.7.118 includes the following resolved issues:

• Fixed an issue where the Multiroot Treelist field did not resolve its datasource query correctly when an item name contained a hyphen or a reserved word (e.g., "child", "parent"), causing the field to display unexpected content tree nodes instead of the intended items.

• Resolved a defect where blobs were missing when media items were transferred from a source to a target environment.

• Updated thumbnail event handler to use sitecore\ThumbnailsGenerator user for auto thumbnails instead of context user in order to allow thumbnail generation to continue regardless of the access rights of the current user.

• Fixed an issue where publishing media items could fail when media field-level fallback was enabled.

• A new checkbox in the Publish dialog lets authors control whether related items of references are included, reducing publish scope and improving performance for large reference trees.

• The Rich Text Editor now includes an enhanced Clear formatting plugin that removes styling and non-essential markup while preserving clean semantic HTML structure.

• The anchor and query string sections in Link fields now automatically expand when they contain values, so set values are always visible.

• In addition to page name and display name, the Sitemap search now also includes the content of page fields that matches the search term.

• You can now search for pages by item ID. The ID can include or omit hyphens and is case insensitive. For partial ID searches, use lowercase.

The latest release of Page builder also includes the following resolved issues:

• The page now retains its scroll position after saving changes from the right hand side panel.

• Image URLs in Rich Text fields used inside Partial Designs now render correctly on the page.

• Multiline text fields inside collapsible sections are now fully editable in Page builder.

• Grouped droplist fields now use the correct item name instead of the display name for consistent values.

• Editing a phone link in the Rich Text Editor now updates correctly on the page.

• When using Page Branches with insert option rules, unchecking and rechecking the "Page" checkbox in the Page settings caused duplicate entries to appear in the "Select a page template" dialog. This has now been fixed.

Key benefits of the SitecoreAI DAM:

• AI-powered efficiency -Automatic metadata enrichment on upload, where AI generates image tags and descriptive alt text to improve accessibility and SEO.

• Smart discovery - Quickly find exactly what you need with advanced search and filtering tools designed for high-speed navigation.

• Seamless integration - Effortlessly tag and organize assets within a simplified interface that serves as the foundation for a unified media picking experience.

• Simplified sharing – You can now generate public links to share your media assets instantly or use them directly within the SitecoreAI Page Builder.

Feature availability is part of a phased rollout.

You can now show different component variants to different visitors without personalizing the entire page. This gives you the flexibility to personalize multiple components on the same page, such as banners, messages, promotions, or calls to action, based on visitor profile data, conditions, or custom values.

Component personalization uses a decision table to evaluate each visitor against your configured rules. You can:

• Define the inputs used for visitor evaluation.

• Create personalization rules based on profile data, conditions, or custom values.

• Map each rule to a corresponding component variant.

Rules are evaluated from top to bottom, and the first matching rule determines which variant is shown. If no rules match, the original component is displayed.

This gives marketers a flexible way to personalize specific areas of a page while keeping the rest of the experience unchanged.

You can also preview and test personalized components before starting the personalization. Analytics data becomes available as visitors begin seeing the live personalization.

• Fixed a defect in the Content Editor where adding a new version to an item that had a clone in a delegated area could cause an exception when the delegated area root had a broken link to the source item.

• Resolved an issue where an error appeared after uncloning an item in the Content Editor and trying to add a new version to its source item.

• Added caching and recursion detection to prevent repeated calls and eliminate intermittent Standard Values recursion errors.

• Deprecated the DB Browser and Serialization admin pages as a security enhancement.

• Added URL string normalization to NameValue classes in both kernel and SXA. This allows comparison operations between encoded and decoded string values that are added to the NameValue collection field in the Content Editor.

• Resolved a defect where language fallback field values were cached without considering live mode context, causing stale or incorrect fallback values to be served across live and non-live publishing contexts.

• Fixed broken links that were appearing after adding a personalized variant in the Page Builder.

• Other security enhancements.