Portal History

Intro

With the UX Engine, we can control the user experience of our beloved customers. We can do very powerful things, and sometimes it can happen to create something that is not as good as expected. Fair enough, we can take a step back: from UX Engine 8.2, it is possible to check what has been changed and by who, restore previous objects, and go back to the funny part of delivering a great user experience!

What Is It?

Portal History is the new feature that allows editorial teams to understand the latest modifications in the UI, saving past configurations in an editable timeline. It allows users to monitor changes in:

• Page Real Estate, 
• Number and Disposals of Carousels, 
• Business Rules Applied, 
• Search Criteria and Autocomplete
• Layouts and Layout Groups
• Continue Watching
• Item Detail
• Open Connector
• Editorial Lists
• Target
• UxReferences and UxReference Groups

Why It Is Useful?

Portal History gives visibility to editorial teams of the latest changes executed by a logged UX Engine Portal user over the UX Design and Business Rules sections. It is useful to the Content Chief to understand which teammates did recent modifications, and to the content team to track the latest actions. It also allows to refresh previous UI settings and with it, all the configurations that it carries. Portal History grants editorial teams to check the recurrent objects edited from a version to another and who did it.

Since each carousel can be highly customizable, mixing business rules, hierarchies, editorial lists, and other configurations, it becomes relevant to track all the changes and provide editors with the history of these changes.

Are you worried about restoring inconsistent configurations? Don’t worry, UX Engine has a pre-alarm embedded that notifies conflicts when replacing precedent settings: for example, it warns if, in the version about to upload, a specific carousel was dismissed.