April 2018 – released Sitecore Experience Accelerator 1.7 (rev. 180410)
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)
|The new Generic HTML meta component allows you to add arbitrary HTML to a page.
|Dynamic Placeholder enabled components now have a default placeholder settings item to fall back on if a specific item was not created.
|Generic links to media items can now be used to render images on the page using the new Responsive Image rendering variant field renderer.
|You can now use model properties to render HTML as the content of rendering variant tags.
|Verbose logging has been added for path replacements in the Set-NewLinkReference PowerShell command.
|You can now dynamically boost search results per page based on the rules in the Sitecore rules engine.
|You can now show previews of rendering variants in the Experience Editor experience toolbar drop-down.
|A container with a specified data source renders the components in its placeholder as if they were placed on the data source item.
|A new Responsive Image rendering variant field renderer has been added to enable all the components that support rendering variants to serve images of different dimensions based on the device size.
|You can now use out-of-the-box functionality to create a site that is hidden behind a custom login page.
|You can now search for media in the search box component based on the media name and content.
|The user experience of the dialog for creating and selecting data sources has been improved.
|A calculated field processor that stores a value in the index depending on whether an item field is empty has been added.
|A cloned site will now appear in the content tree automatically without having to refresh the view.
|Pages that contain search components will no longer add any hash parameters until a user interacts with the search component.
|The Composite theme now inherits from the Basic theme.
|You can now define multiple link providers and switch to a custom provider on a site by site basis.
|The Creative Exchange Gulp watcher now recognizes changes in variant styles and compiles the CSS accordingly.
|We have changed the nomenclature from Feature to Module for SXA functionalities enabled in sites and tenants to align with Helix.
|We have added the Randomize sorting option to enable search results to return a set number of randomized results.
|Filters now display values based on the language settings of the associated search results component.
|Content is now tagged with the language specific tag name rather than the generic item name.
|The default rendering variants are now cloned along with the cloned component.
|Search query tokens functionality has been introduced together with tokens to allow authors to define context-related searches.
|You can now defer the first search operation until the page visitor interacts with a search component.
|The Variant Query rendering is now able to use content search queries on top of previous Sitecore queries.
|The Placeholder Renderer rendering variant now has a checkbox that allows the designer to change the context so that the components in the placeholder are rendered as if they were part of the item that contains the rendering variant.
The following issues have been fixed:
|Customer ticket ID (or other)
|Deleting an original item from the delegated area source does not delete the delegated area clone.
|An SXA item that uses a data source query displays an error in the Content Editor when it is moved outside of the designated context.
|500631, 503479, 504259
|The Metadata renderings do not appear after being dropped on a filled placeholder.
|The Overlay size setting does not affect the overlay page display.
|SXA can break the robots.txt functionality for non-SXA sites on the same Sitecore instance.
|Resolving tokens in Standard Values can cause SXA scoped fields to show errors in the Content Editor.
|Redirect item does not work on Sitecore 9.0.
|SXA interferes with the deployment of marketing definitions.
|When importing the Creative Exchange package, any existing SXA style that contains a space is regarded as a new style.
|Sitecore.XA.Foundation.Search.Azure.config breaks the Content Editor and front-end search.
|There are possible conflicts between the type of an incoming field and the EDM type in the Azure search index.
|Some text is incorrectly translated in the Japanese UI.
|The Load More button can sometimes be displayed, even when the search results do not have any more content to show.
|The JSON placeholder name is not unique and this causes the JSON component to disappear.
|The Experience Toolbar gets stuck on the first selected field when you apply a page design to the page but do not select a rendering on the page itself.
|The active-facet style is removed from the Filter(Checklist) SXA Facet when an additional SXA facet is added on the page.
|Creative Exchange export to folder does not work in Sitecore XP 9.0 if it is defined as a relative path.
|Control characters are not escaped correctly in the JSON output.
|A Check List Filter working with the Number/Integer field type, does not display values correctly.
|You cannot personalize the Carousel component.
|The AssetLinksGenerator can leak database connections.
|The Query String parameter is not rendered in the Link field.
|Content search throws an exception when there is an item that has no version in the default language.
|A global snippet is used instead of a local copy if the snippet is configured to prompt the user to make a choice.
|The Page and Partial Designs from a shared site might not show up if the shared site and the local sites are in different languages.
|Components that contain dynamic placeholders may not work if the display language of the client is Japanese.
|499869, 500779, 501710
|A snippet in a component that contains a dynamic placeholder from a partial design renders incorrectly.
|The workflow state of a datasource item is not updated when a page is moved through the workflow.
|Navigation renders items that have no versions in the current language even if it is configured to skip empty values.
|Creative Exchange can fail to export and import the SXA Storefront theme.
|The SXA components require additional configuration to function correctly when you use the Presentation Details dialog to add them.
|Search Filters (Facets) do not take the search scope into consideration when displaying the content count.
|Specifying sorting in the search scope causes an error to occur.
|Date filters should use the UTC date format.
|The placeholder in some rendering variants is not rendered.
|The Unterminated identifier error occurs when you use the Link component in a shared site.
|In the Experience Editor, the Associated Content button does not open the expected dialog.
|The NVelocity templates are not releasing memory.
|To prevent Sitecore from exceeding the maximum number of fields allowed in the Azure search indexes, unnecessary SXA fields should be excluded.