Under all supported formats, users can select the origin and destination site of the data so it is possible to export and import object entries between any site.

We continue to improve the API Builder by adding new endpoints: GET single element. With the GET single element new endpoint, we allow users to create a GET endpoint that only retrieves a single element using a path parameter.

One particular thing is that users can select as a path parameter any unique custom field defined in the object apart from ID and External Reference Code.

New POST endpoint inside API Builder to add the possibility not only of recovering information of the entries but also of creating them.

As in the GET methods, users can define the schema to use for the request and the response. Both can be the same or two different ones. And can even be one already used previously on another endpoint definition.

Company and Site scope is available too.

The POST method only works for creating new entries of the main object . No entries for the related objects can be created yet at the same time.

SCIM provides a unified, RFC compliant way to keep user/group data in sync between different applications. Liferay is a service provider and enables clients to be connected. Through the defined RESTful APIs and schemas, clients can perform CRUD operations to keep resources in sync.

Pages served by Liferay might make use of third party cookies. In order to inform Liferay to manage them as part of the user cookie consent, now Portal developers and Content creators have a way to indicate the portal about them.

In order to make Liferay aware of them, the content creator or portal developer will need to update the markup to the following:

First, indicate the type of cookie following this format:

Second, change the markup depending on the element affected:

For example, embedding a video from a video provider, will see the markup changed in the following way:

• Before: <iframe src="..." />
• After: <iframe data-src="..." `data-third-party-cookie="CONSENT_TYPE_FUNCTIONAL"  />

We have introduced a configuration feature within the Asset Library, enabling users to decide whether a Vocabulary created there is solely required at the Asset Library level or if it extends to the connected Sites as well.

Use the platform's configurable purchasing rules to dictate which product options need to be purchased together when setting up products with options. You can set which product options must be purchased together and/or which product options cannot be combined together to create a valid product bundle. You can also limit the number of products from a particular group of products that can be purchased together.

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 more speedy alterations to be made before proceeding with check out.

Two new permissions were added to View and Edit the channel default tab in the Account Management Pages. Users are now able to activate/inactivate the tab.