Searching NEWS ROOM

Export Page

These release notes cover enhancements to the Virtual Staging Environment(VSE) service to support Content Authoring, together with several Content Authoring enhancements. The changes are explained in detail below.

VSE for Content Authoring

The Virtual Staging Environment (VSE) was introduced to provide customers with an easy to set up, flexible and secure way of working with content before it goes live. The VSE service is being released in stages, with the initial release supporting Dynamic Imaging, and it has now been enhanced with support for Content Authoring, together with some other improvements.

As explained in the January release note, when a VSE is created, a unique domain is generated that points to a staging environment to which access is controlled. You can use this domain in the place of the production domain to build a URL to consume assets, and content created with the Content Authoring app, within the staging environment.  Access to the staging environment is controlled, using security rules that you set up, so that only authorised users will be able to view and work with the content. For more information about VSE, including how to set up an environment and security rules, see the Virtual Staging Environments pages.

Adding support for Content Authoring provides several opportunities to improve your workflow:

  • It's now easier for several content creation teams to work in parallel, with one team working on content for a new collection or product launch and another team maintaining content on the live site. Each team can work independently without disturbing the other's work.
  • Content can consist of a mixture of unpublished assets and live content from your website, so it's easy to preview how your entire site will look with the new content added. This also makes it easy to preview "hot fixes" of content before it goes live.
  • Content served from a VSE is consumed in the same way as production content. It can be requested from a browser, ecommerce integration or native application and alll that you need to is replace the production domain in the URL used to retrieve content with the VSE domain. You could even have several staging environments and allow the user to switch between each one.

Using a VSE with Content Authoring is explained in detail, including examples, on the Using Content Authoring with a Virtual Staging Environment page.

Support for text assets

Text assets stored in the Dynamic Asset Management system (DAM) can now be consumed within a VSE. Like images, text assets are uploaded to asset stores included in the VSE content retrieval rules and do not need to be published. Text meta data can also be retrieved. 

Content Authoring Enhancements

A number of user interface enhancements have been included in latest of release of Content Authoring. It's now easier to refresh the publish status of an item of content and to identify an item's content type, and improvements have also been made to the display of long content titles and the feedback provided when searching.

Refreshing an item's publish status

In order to make it easier for users to see when new or updated content is published, a publishing refresh button has been added to the top right of the status bar in the content library. When a user chooses to publish an item of content, the refresh button is shown and clicking it will update the publish icon in the content item's library card. 

 Click here to see the publishing refresh button in action...

Publish an item of content in the content library by choosing "Publish Content" from the item's contextual menu.

The publishing refresh button is shown, together with a status text box showing that the publish is is in progress. Clicking the refresh button will update the publish status icon on the library card. As you can see, the item is now published.




Improved support for long content titles

If the title of some content is too long to be displayed, then hovering over the title will now show the full title. This is shown in the example below.

Identifying an item's content type

A status bar has been added to the ‘Edit Content’ window that shows the content type used to create a piece of content. In the example below, content named "New Collection Banner" has been created from the "Tutorial Banner" content type.

Search improvements

In the Content Authoring app, the search feature has been improved. The new functionality means that the search functionality is now:

  • not case sensitive
  • not restricted to the title

This change applies to searching both in the Content Library and within the media browser opened from the content editing window.

 Click here to see the search changes...

In this example, we are looking for some content in the Content Library that we know contains the text "spring styles". We enter the text in the search box and as we type the popup menu is populated with the title of each piece of content that contains this text. In this case two items are returned, one that contains the search text in its title and the other that contains within the content itself.

Type return to see all the search results. Alternatively, you can just choose the content you want from the list by selecting its title.


Improved feedback when searching

The visual feedback provided when you start a search in the Content Library or media browser has also been improved. A spinner will be shown when you enter some text in the search box and press return and will be displayed until the search is completed. In the example below, the user is searching for "collection" and while the search is in progress, the spinner is shown.

Related Pages

Virtual Staging Environments

Using Content Authoring with a Virtual Staging Environment

Release Note: Virtual Staging Environments, DAM workflow and CA enhancements- January 2017


  • No labels