December 2017 – released Sitecore Experience Accelerator 1.6 (rev. 180103)
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)
|You can now use a wizard from the context menu to add a feature to a site after it is created.
|You can now use a wizard from the context menu to add a feature to a tenant after it is created.
|You can now use image, link, and text fields for tag attributes in rendering variants.
|Rendering variants now support self-closing tags.
|The Cookie warning meta rendering is now called a Privacy warning.
|The Feature and Foundation nodes now have module scaffolding to facilitate the creation of new SXA modules.
|Tenant and site scaffolding input validation script support has been added to allow features to validate selected configurations in the dialog before scaffolding the site or tenant.
|Tenant and site scaffolding post-setup script support has been added to allow features to perform additional actions after you create the site or tenant.
|The SXA Rendering Copy wizard lets you create customized versions of existing SXA components.
|You can now edit composite renderings directly on the page.
|The Gallery component supports rendering variants.
|Feature authors can now provide theme extensions that extend the themes that are created by scaffolding scripts.
|Feature authors can provide theme extensions that will be included when you edit a site in Wireframe mode.
|You can extend rendering variant tags with custom data attributes.
|Rendering variants let you add an editing frame as part of the variant definition.
|Row and column splitters allow you to add and remove placeholders out of order.
|Row and column splitters let you change the order of their placeholders.
|SXA now has a Google Analytics integration meta-rendering.
|You can configure the search box to show Solr predictions rather than a list of results in its drop-down.
|Rendering variants use a markup that complies with the variant definition to render a field, even when the field is not present.
|The Row Splitter markup allows for better adherence to the Bootstrap and Foundation grid guidelines by adding the appropriate row class.
|The new Splitter components allow you to define pre-fabricated component groups to a page.
|You can now open the specific sections for Tabs, Carousel, and Accordion renderings when a page loads.
|You can configure the range slider to show minimum and maximum values.
|The Page Size drop-down search rendering can show custom texts as values.
|The Page Selector component renders an additional class that allows you to hide the component if page selection is not possible.
|Additional styling facilitates the easier selection of multiple elements in the checklist filter.
|The Checklist filter component now allows you to search by results count.
|A page can be used as a data source for components inside composites to allow for rendering page fields in them.
|You can define URL language embedding on a per-site basis.
|The SEO Sitemaps aggregate all the available sites under a single hostname, and support multiple languages
|Page layout information is cached after merging with partial and composite rendering information.
|Data source items can inherit from an additional template. This allows you to copy data source items from the Global folder to page data sources when the data source is used.
|Site and placeholders now have component caching, configuration triggering, and support donut caching.
The following issues have been fixed:
|Customer ticket ID (or other)
|There is a duplicated JSON tab in the Select a Rendering dialog for JSON devices.
|In the Experience Editor, SXA renders URLs for multisite instances with incorrect host names.
|SXA shows JSON markup instead of HTML markup in the POI details.
|Composites do not work on mobile devices.
|A user cannot add a new SXA site to a tenant that has an existing SXA site.
|The AssetBundler transforms CSS files incorrectly. This causes an error in the IE 9 browser.
|The Select Rendering dialog has duplicate tabs when a user creates a folder that has the same name as a rendering.
|You cannot change the file destination that you upload images to in the standard Sitecore Select Media dialog.
|490622, 493310, 497544
|Personalization does not work for composite renderings.
|Two Location Finder components do not work on the same page.
|Rendering variants do not work for renderings that are placed inside a composite.
|Search filters do not respect the current language setting of the Search Results component.