October 2021

Backend architecture improvements to increase performance of APIs.

Rich Text Editor has been extended to include an underline functionality.

SEO metadata attribute lengths have been increased to 400.

Improved error messaging when attempting to create duplicate page types and new page with instructions when encountering a 500 error.

 

Fixes

Issue: When searching for a term containing a parentheses character, the search fails and returns a 500 internal server error.

Solution: Adjusted code to enable special characters. Error message no longer displays.


Issue: Imported menus do not have correct order value.

Solution: Modified logic to correct issue.

 

September 2021

Several minor changes to ensure consistency across all UI elements.

Monitoring and alerting improvements for earlier Fabric support responses.

Page status modifications

  • Added page status indictor for Live, Draft, or Scheduled.
  • Updated to single Publish button for current live content to save and push changes live.
  • Draft status pages will now have both Save and Publish buttons.

 

Fixes

Issue: Internal server error after importing PIM hierarchy to generate a menu.

Solution: Fixed back-end error, menu generates as expected from the imported hierarchy.

 

Issue: Error displayed to users editing pages on Safari.

Solution: Adjust code to work with Safari, error message no longer displays.

 

Issue: Role type does not work with XM Rich Text Editor.

Solution: Update the XM rich text editor to allow for role property when adding an HTML element.

 

November 2020

 

Page Types: You may use Page Type labels to group pages to group pages of the same type/application.We added page types to help XM users classify and organize content. Example: Home, Landing, Blog, PDP, Category, etc.

We recommend creating Page Types first before creating any new pages. To create a page type, you would need to provide the following:

  • Page type name
  • Prefix

Note: Page type prefix can be used on the commerce front-end for dynamic routing (additional configuration is required by the system). To elaborate, currently all XM-driven pages use the same prefix - /content. With page types, every type can enable its own prefix, That is, prefix /p for a PDP page, prefix /c for Category page, prefix /blog for a blog page, and so on. please bold the page names.

Known Bugs:

  • Search doesn’t persist across tabs.
  • To see archived tab count, user has to hard refresh
  • You will get code 409 when editing version details through the editor
  • You will see an empty page when there are no pages created

October 2020

 

Nested Components: The earlier version of XM allowed users to add multiple components to the page. However, these components existed at the same level, that is - page layout. With this release, nesting capabilities are added to the platform. Now, XM users can nest additional components within a single component. In other words, now you can add children (one or many) to a parent component.

Components: Components are elements on the page that enhance the experience and contribute to the visual interface of the website. Every page has different components, such as banner image, content, CTA, etc.

As an example of nesting, let's look at the Hero Carousel with Heading and Slides section. These sections have additional elements as follows:

  • Heading: Title, AutoZoom, etc.
  • Slides: Title, Description, Image, Button copy, Button link, etc.

If nesting is enabled for this component, you will be able to add additional components within the Hero Carousel sections or particular elements of a section. One of the use cases could be adding a Rich Text Editor to the Hero Carousel component.

The updated component structure appears as follows:

Option 1: Adding nested component at section level 

  • Heading
  • Slides
    • Slide1
      • Title
      • Description
      • Image
      • Button copy
      • Button link
    • Slide2
      • Title
      • Description
      • Image
      • Button copy
      • Button link
    • Rich Text Editor

 

Option 2: Adding nested component within a section 

  • Heading
  • Slides
    • Slide1
      • Title
      • Description
      • Image
      • Button copy
      • Button link
      • Rich Text Editor
    • Slide2
      • Title
      • Description
      • Image
      • Button copy
      • Button link

For this to function correctly, nesting should be defined in the descriptors. For example, when a front-end developer builds a React framework and writes a descriptor, they would need to define what components nesting is available and at which level. (That is, within an array or at a section level).

Last update: Oct 21, 2021

Have any questions?
Let's Talk.