What's new in Sitecore Experience Platform 10.4
Version:
This topic lists the new features and the changes in the most recent release of Sitecore Experience Platform. We've also added new features for XP in Managed Cloud and in a number of tools and module releases.
Experience Platform and Experience Manager
The following table lists new features and improvements made in Experience Manager and Experience Platform 10.4.
| Area | Change | Description |
|---|---|---|
| Accessibility | Improvement | There's a new range of accessibility features in the Content Editor, in accordance with the W3C ARIA Authoring Practices Guide. You can now use a keyboard to:
In addition:
|
| Digital marketing | New feature | Trigger campaigns or goals based on rules. This is relevant, for example, if you want to display content from a campaign when certain pages are visited. Links to documentation: |
| xConnect integrations | New feature | An xConnect endpoint is now available in Sitecore Connect. This allows you to build your own recipes and send your data to many of the martech solutions available in Sitecore Connect. |
| Content authoring | New feature | You can now add a custom language or regional language such as en-EU directly in the Content Editor. This allows you to extend beyond the language formats that are registered in .NET. Link to documentation: |
| Security roles | Improvement | Added the Sitecore Client Content Reader role which grants read access to the content tree items in the Content Editor and the Media Library. Link to documentation: |
| Solr search | Improvement | You can now configure Solr search to use soft commits. Link to documentation: |
| Webhooks | Improvement | Webhook requests now include the TemplateName property.Link to documentation: |
| Media files | Improvement | You can turn off the feature that blocks SVG files with JavaScript code when you upload media files to the Media Library. Link to documentation: |
| Item API | Improvement | You can now use the Sitecore.Context.Language.CultureInfo property to return culture information related to the current language context.Link to documentation: |
Sitecore Experience Accelerator
The following table lists new features and improvements made in Sitecore Experience Accelerator (SXA) 10.4.
| Area | Change | Description |
|---|---|---|
| Grid systems | New feature | You can now configure your headless sites to use the Tailwind grid system. Link to documentation: |
| Security roles | Improvement | With the new Sitecore Client Site Managing security role, users have the right to create, rename, write to, and delete sites and site collections. Link to documentation: |
| Modules | Improvement | You can install modules at the Project layer. Link to documentation: |
| Sitemap | New feature | You can enable or disable language codes in sitemap URLs. Link to documentation: |
| Renderings | New feature | You can show or hide renderings in the Experience Editor toolbox for specific sites based on the page template. Link to documentation: |
| Experience Edge | Improvement | Mark non-content sites as internal to prevent them from being published. Link to documentation:
|
| Asset Optimizer | Improvement | You can now exclude unsupported CSS or JS files from minification. Link to documentation: |
JavaScript Rendering SDKs (JSS)
The following table lists new features and improvements made in JSS since the release of 21.0.
| Area | Change | Description |
|---|---|---|
| JSS | Improvement | JSS sample applications now use Next.js 14 and Angular 16. The JSS_APP_NAME environment variable was renamed to SITECORE_SITE_NAME. There are also updates for React packages. If you are on version 21.5 or earlier, upgrade to 21.6 then 21.7 to get all the latest features.Links to documentation: |
| JSS | New feature | You can apply retry strategies for Experience Edge requests to prevent build failures on large websites. Link to documentation: |
| JSS | Improvement | Sensitive information in component-level getStaticProps and getServerSideProps functions is included in the client-side bundle in development mode, but not in production mode.Links to documentation: |
| JSS | Improvement | If you use Netlify for hosting your Next.js JSS applications, you can follow our guide for deploying Next.js applications to Netlify. |
| JSS | Improvement | JSS applications have improved .env support.Link to documentation: |
If you have suggestions for improving this article, let us know!