June 2018 – released Sitecore Experience Accelerator 1.7 Update 1 (rev. 180604)
Sitecore Experience Accelerator (SXA) enables parallel work streams (content, creative design, UX, coding) to not only reduce the time required to produce a website, but also improve the quality by allowing all contributors to validate each other's contributions. SXA provides reusable user experience layouts and components that are fully integrated into the Sitecore editing experience.
|Customer ticket ID (or other)
|We have provided a set of sample scripts that allow you to integrate Creative Exchange with your Continuous Integration environments.
|Components that experience an exception in their code are now wrapped with standard markup. This hides them and makes it easier to investigate the problem.
|SXA now uses its own optimized custom search indexes.
|You can now override the default indexes that SXA uses per language and per site to enable provider-specific features that can be language specific, such as, stop words.
|SXA now supports working with Solr in Azure.
|The Rendering variant placeholder renderer now supports an explicitly provided placeholder key and allows you to assign placeholder restrictions.
|The Layout Service has been updated to the latest version.
|The introduction of an additional placeholder cache layer has improved the performance of the Experience Editor.
The following issues have been fixed:
|Customer ticket ID (or other)
|When a user interacts with the Slider Filter, no results are displayed in SXA search results.
|Overlay height is not properly applied on a page.
|Creative Exchange does not distribute an imported layout correctly between the Shared and Final fields based on where the renderings are stored, but always imports them to the final layouts.
|In SXA Data Modelling, JSON is not properly rendered for the Link List component.
|The Container background image is removed when you add a component to its placeholder.
|502135, 502326, 505087
|The SXA Search service throws an error when you click a POI marker on a map.
|Creative Exchange terminates with an error when a user tries to import from an empty folder.
|The Checklist filter does not work correctly when you try to select multiple values.
|Newly created SXA modules are not displayed in the scaffolding dialogs if the UI language is not set to English when they are created.
|A newly added carousel includes content from another carousel that exists on the same page if the user doesn't save the page between deleting the old carousel and adding the new one.
|Pages that are exported with Creative Exchange do not function correctly in offline browsing if the site is configured to include language prefixes.
|The Radius filter does not render its title.
|The Range slider filter doesn't output the initial selection range text until after the first user interaction.
|An invalid lookup Source error appears for the Page Content element for the Page __Standard values.
|The Document Manager dialog is not populated when you install SXA.
|Creative Exchange stops the entire import process when it encounters a page it can't parse. An appropriate error is now logged and the process continues.
|Over 550 default SXA fields are now excluded to provide more room for custom fields before reaching the Azure index limit of 1000 fields.
|SXA processors are executed unnecessarily for non-SXA sites.
|Creative Exchange does not export empty files.
|The dictionary in the GridDefinition class is not thread-safe and this adds an error to the log files when an application restarts.
|When you are editing, an empty Navigation component does not appear when there are no items to display in the current language.
|Publishing a large instance with SXA takes longer than expected.
|HTML is not purged correctly for SXA sites during the publishing process.
|The Is Link field works incorrectly in combination with the Field used as link target field on nested rendering field variants.
|You cannot use rendering variants from shared sites as reusable components in other sites in the same tenant.
|The Page data folder for a rendering that is added to a composite site is created under the page rather than under the composite item.
|When you drag and drop a component, the placeholders slide on the page if a rendering variant with the placeholder exists on the page.
|Nested composite components ignore the datasource of the nested component.
|A Content Editor upgrade warning incorrectly says that an update is required.
|A regular expression is unnecessarily executed when you publish a page and this results in higher CPU usage.
|An unnecessary invisible character - ﻿ - is included in the language selector component.
|In the Experience Editor, in a rendering variant field, the Render if empty option hides the empty field if it is not checked making it impossible to edit that field.
|The Azure search provider is configured incorrectly and causes errors during indexing.
|When you use the Azure Search provider, fields with the same name and different types cannot be stored next to each other in the index.