This means users can explore data in table, list, or card formats, whichever best suits their needs. Enhance user engagement, improve data comprehension, and unlock deeper insights with our powerful new visualization tools – explore them today!

While managing data set views, define actions to be used in the data set fragment. Now you can define a broader range of actions, including opening links, triggering headless actions, launching pop-ups, and even opening dedicated side panels. This empowers richer data interactions and streamlined workflows for your users. Transform your data sets into powerful information hubs.

Aiming to provide a better way to manage Object entries, now Display Pages allow the creation of Object Edit experiences, using Forms Container and Fragments.

When using a Form Container in a Display Page, submitting it will now update the object entry being displayed.

This, combined with the possibility to use multiple display pages at the same time, and the new “Save as Draft” option for objects, enable a whole new set of possibilities for customers, such as creating multi-step processes out of the box.

Now, if an asset type (for example, an Object definition) has several related Display Page Templates, and one of them is marked as Default, we allow to map links to any of the existing Display Page Templates for that Asset Type, in addition to the Default one.

This new possibility allows some interesting use cases for customers, such as:

• Differentiated View Display Page and Edit Display Page for Object entries.
• Multi-step processes (that need different step URLs) can be now created by using one Display Page per step.

Now the users can easily identify components that may cause performance issues in their Pages.

We have added a new tab on the Page Audit to show the users the back-end render times of the different components, as well as warnings to help identify specific components configurations that may lead to performance issues. Those warnings also appear on the Edit mode, so the user is aware of possible issues during the page creation.

Sometimes the changes added to a publication needs to be reviewed by someone who is not a member of the site. The goal here was to make unauthenticated users able to review changes within a publication. For this we implemented a mechanism to generate a code, which can be used to access the Review Changes screen of a certain publication. Also this link could be easily invalidated/generated anytime by authenticated Publication Reviewers.

The goal here is to make the users able to move changes between publications. This is needed because sometimes users do not want to publish an entire publication, but also do not want to revert the changes which will not be published actually. With this feature users can move changes from one publication to another, creating subsets of changes, and publish them separately. For readers with technical knowledge: this is similar to cherry-pick-ing a commit in git from one branch to another.

Now, users are able to visually understand the structure of their objects and how they connect with each other to result in the platform model.