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.

A common problem we have heard from our customers revolves around the time required to complete an AB Test. If a customer’s page receives limited traffic, the time to completion could be many weeks if not months.  Amidst the rapid changes in today's business landscape, this delay potentially negates the usefulness of test results. On top of this, if a user were to terminate the test prematurely, the insights they gathered from the test and the variant they created were lost.

In order to remedy this issue, we are now providing test results and the ability to publish a variant when an AB Test is terminated. Although these results cannot determine a winning variant with 100% confidence, they will give marketers a sense of how their variant was performing. Using this information, Marketers can now make educated decisions according to their specific time constraints.

It is important to remark that this feature is DXP-only, as it belongs to Analytics Cloud.

The ability for a buyer or sales agent to edit a product bundle directly from the mini-cart has now been added. Previously, if a change had to be made the bundle had to be deleted from the cart and added again. This allows for more speedy alterations to be made before proceeding with check out.

New extension point allows for external custom rules to be written to determine what SKU's can be linked to a product as Options. This is limited to dynamic pricing scenarios. Discounts can still be created to discount specific product combinations.

Sell and manage SKUs by adding different Units of Measure to the SKU. Configure the Unit of Measure to optionally allow for sales in decimal quantities. Units of Measure have their own pricing and inventory. Once configured, they add to the shopping experience of the buyer who can now purchase SKUs in different Units of measure.

Integrated Logging in Cloud Console for both Client Extension and DXP. Capabilities:

1. Unified Logging View: Enables users to simultaneously view both Client Extension and DXP logs.
2. Log Interactivity: Allows users to filter and sort logs based on parameters like timestamp and severity.

Benefits:

1. Comprehensive Insight: Eliminates the need to toggle between separate log sources, offering a holistic log view.
2. Efficient Troubleshooting: Enhanced filtering and sorting make it easier to pinpoint and address issues.

Capabilities:

1. PSC Connection Support: Allows direct integration of specific Kubernetes services or namespaces via Private Service Connect.
2. Tunneling Solutions: Provides a dedicated channel for GCP services or different GCP VPCs to connect securely within Liferay Cloud.
3. API-Driven Provisioning: Enables users to automate and configure PSC connections programmatically.
4. Combined Utility with Cloud Interconnect: Offers a mechanism to securely link on-premises data/systems with GKE or Google Cloud Storage.

Benefits:

1. Enhanced Security: Bypassing the public internet ensures data protection during transmission.
2. Reduced Latency: Direct connections speed up data transfer and interactions.
3. Predictable Performance: Stable and consistent network performance between on-premises and Liferay Cloud.
4. Flexibility & Automation: API-driven provisioning provides users with a more flexible setup and deployment process.

Capabilities:

1. Azure DevOps Authentication: Supports integration of Azure Git repositories via Azure DevOps with Jenkins, including PAT generation for authentication.
2. Jenkins Build Integration: Configure Jenkins to poll or check the Azure repository based on specific triggers.
3. LCP.json Setup for CI Service: Define Azure DevOps as the SCM provider and specify details for Jenkins interaction.
4. Deployment Configuration: Allows push from GitHub to Azure DevOps and deployment from Jenkins to the designated infra environment.

Benefits:

1. Versatility: Users can leverage Azure DevOps as their Git repository provider while working within Liferay Cloud.
2. Automated Updates: Automatic polling of the Azure repository every 5 minutes, ensuring timely builds upon detected changes.
3. Security: Utilizes Personal Access Tokens for specific and secure authentication, combined with best practices for token management.

Reducing downtime, improving operational and resource utilization efficiency with the new Concurrent and Sync reindex execution modes providing high-availability in search capabilities while the operation is running.

We have created a new application that helps developers to build APIs based on custom Objects in a Low Code/No Code UI. This new feature allows users to define the whole structure of the API, from the endpoint’s name to the data model of the request and response schemas.

And, because the persistence layer of the API Builder is Objects, all capabilities are available at the API layer and every object has its own CRUD API application created by default.

So, from the UI or from the API, now users can create custom API Applications from scratch.

The scope of this beta feature only covers the creation of GET methods to retrieve a collection of elements with the possibility of creating pre filters and sorts.

Now admins can define the default sorting for a dataset view. You can select the field to sort by when users access the page with the data set view as well as the direction (ascending or descending). It is possible to add more than one field. In this case, results will be sorted following the order of the fields, so it will start sorting based on the first field, for elements with the same value for that field, it will continue sorting based on the second field and so on.

Admins now can define views and select fields that are localized, so users will access the corresponding translation when visiting the page. Additionally, the names of the columns and filters are also localizable.

In order to use this feature it is needed to enable “Translation Support for Object Entries” in the Feature Flags menu before enabling “Data Set Manager” in the beta section of the Feature Flags menu.

Admins can define filters to make them available for end users visiting pages with the dataset fragment. There are 3 types of filters available:

• Date filters: compatible with fields of type date. Admins can provide a name to the filter as well as provide a “From” and “To” dates to be pre-applied if needed.
• Selection filters: This filter allows admins to configure a picklist as the source of the options for the filter.
• Client extension: This new client extension enables admins and developers to fully customize the filter experience and add new types of filters depending on their needs.

• In order to use this feature enable “Data Set Manager” in the BETA section of the Feature Flags menu.

Apart from exposing information in tables, with the Data Set Manager now admins will be able to define actions linked to each of the elements of the data set. For each action:

• Admins can provide a localized label
• Choose the icon to be used
• Provide the URL to redirect the user to. In case you need to parametrize it so each row has a different URL, you can do it by adding it between brackets as part of the URL, for example myURL/{id}/editPage will look for “id” in the Headless response and substitute for the corresponding value in the URL.
• With “Headless Action Key” admins can associate an action to a headless endpoint, which takes permissions into account, so the action will only be shown to the user if the corresponding headless action is present in the response. For example, you can link an “edit” action to the “update” Headless Key.
• Provide an optional Confirmation Message if needed.

• In order to use this feature enable “Data Set Manager” in the BETA section of the Feature Flags menu.

With the Data Migration Center, users can export and import, in a very easy way, Objects entries and Objects definitions from one instance to another using JSON files. The actions executed can be consulted later in a list when you can download the files generated every time is needed.

Now we prevent content creators from generating page conflicts and errors by automatically locking pages when they are opened in Edit Mode, not allowing other users edit it at the same time. Beside that, a recurrent process reviews all locked pages to unblock them automatically if no activity is registered. Administrators can also unlock them manually if it’s needed.