We have received multiple requests about users having difficulties resolving conflicts during a Publication process. We listened for these requests, and decided to improve the quality of feedback provided to users about conflicts. Making the resolution of these conflicts easier.

Some applications do not support Publications. That situation can be really confusing when users try to use one of these applications, while inside a publication, and expect it to work together with Publications. We are aiming to make the user experience of the portal during publication as smooth as possible, so we decided to add a mechanism which provides the users with information if they start using one of these apps.

Improving performance is one of the main elements in our product strategy. Here we worked on improving the performance of the Review Changes screen. We have already improved the performance of other screens, and in the future we keep improving the performance of the screens.

Although Analytics Cloud provides valuable insights into the performance of content and pages, sharing this information within an organization has proven difficult for some users. To solve this problem, we are introducing a new feature that aims to enhance your sharing and reporting capabilities. With this feature, you can now effortlessly download PDFs of your dashboards and CSVs of lists (eg. segment membership), making it easier than ever to share critical insights with your stakeholders.

Key Benefits:

1. Time and Effort Savings: Exporting your dashboards to PDF and lists to CSV is a breeze. Say goodbye to the time-consuming task of manually extracting this information and formatting. Our platform streamlines the process for you.

2. Professional Reports: The PDF export feature ensures that your insights are presented in a polished and professional format, perfect for sharing with executives, clients, and colleagues.

To use this feature, simply click on the new Download button in the top right navigation bar. From there you can select the date range for the dashboards as well as the specific cards you wish to include in your report.

Although Analytics Cloud provides valuable insights into the performance of content and pages, sharing this information within an organization has proven difficult for some users. To solve this problem, we are introducing a new feature that aims to enhance your sharing and reporting capabilities. With this feature, you can now effortlessly download PDFs of your dashboards and CSVs of lists (eg. segment membership), making it easier than ever to share critical insights with your stakeholders.

Key Benefits:

1. Time and Effort Savings: Exporting your dashboards to PDF and lists to CSV is a breeze. Say goodbye to the time-consuming task of manually extracting this information and formatting. Our platform streamlines the process for you.

2. Professional Reports: The PDF export feature ensures that your insights are presented in a polished and professional format, perfect for sharing with executives, clients, and colleagues.

To use this feature, simply click on the new Download button in the top right navigation bar. From there you can select the date range for the dashboards as well as the specific cards you wish to include in your report.

Now users can select any image from the Liferay repository directly from the Web Content edition page, creating a better experience and allowing creating a structure of featured images if it’s necessary.

To help content creators raise the quality of their content, now they have integrated in our rich-text editors a spell checker that will help them solve spelling and grammar errors. It supports multiple languages, including: Spanish, English, French, and German.

Liferay AB Testing capabilities now helps customers save time by reassigning the traffic split based on the running test results. The dynamic traffic allocation ensures that the estimated winner variation gets more traffic, optimizing conversion in highly time-sensitive situations. 

To help users enrich their content, Liferay provides a new LXC service to serve videos to a wide audience out of the box. Content creators will be able to upload videos directly to Liferay and the new service will take care of generating different versions with several resolutions to adapt to user’s connection capabilities, together with automatic subtitles and AI powered auto-tagging based on the video content. Content creators will also be able to add manual subtitles to the videos in case the automatic ones don't fit the need.

Blueprints are referenced by their ERCs under-the-hood in the Blueprints Options widget and the Low-Level Search Options widget also supports a new attribute called search.experiences.blueprint.external.reference.code as the recommended way to configure a blueprint (preferred over the old attribute search.experiences.blueprint.id). In addition to that, when moving blueprints or elements between different environments using for example the Batch Client Extensions, entries will preserve their ERCs making portability easier. This way, when for example a search page is imported from a LAR, the Blueprints Options and Low-Level Search Options widget configurations can continue working thanks to the association being achieved via the ERC of the blueprint and not via its ID or other identifier that may be different on the new environment.

Lastly, users can now access and edit the ERC of blueprints and elements directly from the editors.

Because WebDAV appears to be the only viable solution for remote documents access/editing for the moment and there is customer demand. WebDAV supports HTTP Basic and Digest auth. The latter requires us to store insecure hashes, because of protocol specifics.

Because we cannot change that nor remove WebDAV support, we will reduce the impact of a successful attack instead.

This is achieved by creating a separate strong password for Digest auth.

We achieve the “strong” characteristic through only allowing generation of passwords, based on UUIDs. This means when the hash is produced, it will also be stronger also, though not perfect.

This feature adds read-only support for all object fields types, making sure users are not able to update those fields from both the UI or APIs, only the system can through default values or actions for example.

Users can configure their fields between 3 options, read-only true, false, or conditional.

• Read-only false: normal fields that support input from users through the UI or API.
• Read-only true: fields that do not support inputs from users through the UI or API, only can be updated through the system, as actions and default value for example.

  • Read-only fields must be supported in views and layouts, in the layouts those read-only fields must be not editable.

• Read-only conditional: fields that by definition are read-only false, but that will throw exceptions in case the condition is true and the user can’t update that field. In this case, in the UI, the logic should run before the field is loaded, in the headless API, this validation is only made when the user sends the request.
  • The condition is built using expression builder.

When users access a site in a language different from their user profile language, the following Information message is shown:

Now administrators can configure if this message will show up or not from System or Instance. Go to Instance Settings > Pages > Friendly URL Redirection and check/uncheck the “Show Alternative Layout Friendly URL Message” option for the appropriate value.

This feature empowers users to create content use cases on top of objects framework, allowing admins to enable localization for objects' entries text fields.

This feature allows customers, who need more capabilities than what the out of the box Expression Builder provides, to add their custom validations in Objects framework without running their data through an external microservice.

Evolving the user experience when object validations fail specifying which information field end-users need to update.

This feature allows admin users to configure whether to send one email with everyone in copy or many emails individually to each email address.

Enabling this feature will allow users to dynamically populate fields using expressions with information created from data filled and provided by other fields.

Traditionally in Liferay, it has been hard to manage features deprecation because customers kept using the old features even if we announced deprecation and eventual replacements.

Now, we are able to better manage deprecation processes with the following changes:

• Features deprecation notice is increased from 6 months to 12 months. It applies to the Intended Functionality, as described in our Support Policy.
• Now, deprecated features might be kept inside a Deprecation Feature Flag during the deprecation period. These feature flags work as follows:
  • For upgrades, Deprecation Flags are active by default, therefore customers still see the deprecated feature. No disruption is perceived.
  • For new instances created, Deprecation Flag is inactive by default, therefore, the deprecated feature is hidden and it requires activation to be used. It prevents users from unconsciously using a deprecated feature.

• Deprecated features are identified in DXP with a new deprecation badge.

When “Manage Users” permission is added to an Account Admin, the Admin can invite, assign and create Users. We separated the “Invite User” permission so it can be used without providing the other permissions to the User.

Before this feature when somebody wanted to activate/deactivate a User they needed to have “Delete” permission. We created two new permissions called “Activate” and “Deactivate”. Users with “Delete” permission still able to activate/deactivate users.

We also created two new Headless-API endpoint:

/headless-admin-user/v1.0/user-accounts/by-status/${status}

Status can be either "active" or "inactive," allowing you to fetch users by their status.

 /headless-admin-user/v1.0/user-accounts/by-email-address/${emailAddress}

This endpoint lets you retrieve a user by their email address, regardless of their current status.

We extended the Audit Log info on IMPERSONATION actions , ASSIGN/UNASSIGN events involving the role assignment of individual users and ASSIGN/UNASSIGN Role Assignment of Organizations/User Groups/Sites.

We have expanded our Headless Admin User API to include POST, PUT, DELETE, and PATCH endpoints for managing postal addresses associated with user accounts. This development aims to provide more comprehensive functionality and greater flexibility for our users. Additionally, we've made crucial changes to the UserAccount schema and related methods to allow users to manage user status efficiently.

It is now possible to set an expiration on the “set new password” link.

Now users can export the Frontend Client Extensions that have been registered through the UI and import them in other instances. The system will generate a JSON file with all the information needed.

In order to use supported JDK versions, we are upgrading to Gradle 7 to use newer JDK.

The integration of ChatGPT with our Web Content editor is now available OOTB.

Now the “Theme SVG Spritemap” frontend client extensions is enabled by default.

Now the “JS Import Maps Entry” frontend client extensions is enabled by default.

Dynamic Data Lists is deprecated and replaced by Objects. DDL has been deprecated as of 7.3, and the Deprecation flag was added to prevent new integrations using DDL (customers that upgrade will still see it).

DDL is planned to be removed in 2024, please migrate your data to Objects before then.

Proxy Objects allows users to manipulate data directly in external systems, such as Salesforce. This feature provides the ability to always interact with live data, avoiding duplicating and conflicts between the systems.

Now, Liferay includes a connector to Salesforce for proxy objects. With it, you can integrate your proxy object with custom Salesforce objects, using Salesforce as an external storage system

New terms available in notification templates related to the current user and entry creator were added, in order to improve the power of dynamically generated templates.

Added terms:

1. [%CURRENT_USER_ID%]

2. [%CURRENT_USER_FIRST_NAME%]

3. [%CURRENT_USER_LAST_NAME%]

4. [%CURRENT_USER_EMAIL_ADDRESS%] 

5. [%OBJECT_AUTHOR_ID%]

6. [%OBJECT_AUTHOR_FIRST_NAME%]

7. [%OBJECT_AUTHOR_LAST_NAME%]

8. [%OBJECT_AUTHOR_EMAIL_ADDRESS%]

This feature allows power users to configure the intervals to retry to send the email notifications when the first instant attempt fails.

Evolving the power of notification templates, this feature allows users to use variables not only from the object in context, but also from related objects.

This feature allows the user to define a default value for object picklist fields. Default Value can be configured for custom fields from both Custom and System Objects.

This feature allows the user to require that a field's values be unique inside of that column. When this is configured, the system will not let two records have the same value for that field, behaving similarly to a key to that entry.

This feature adds a new field type “Date and Time”. A Datetime value stores a year, month, day, time, and time zone. With this field, users will also be able to create time ranges, manage priorities and order entries well, and to give more context and assertiveness to the data.

This feature empowers users to create content use cases on top of objects framework, allowing admins to enable localization for objects' entries text fields.

Evolving the extensibility of system objects through objects framework, this feature allows users to create and update System Object entries through Object Actions as they can with Custom Objects.

In order to get in context entry history information, this feature introduced the endpoints to retrieve the object entry log information through the object headless API suite. Allowing users to compose experiences with the specific entry update history.

This feature allows users to enable the basic encryption support for object fields.

This feature shows the Organization application as a System Object in Objects Admin, allowing users to extend it and related with other objects available.

OTB workflow that will split a mixed basket of goods a customer places from different suppliers, into individual supplier orders to support marketplaces and webshops where partners are also present.

Used in Conjunction with Supplier Accounts, this object's rule, once configured, splits Commerce Orders automatically by the Catalog that each Product belongs to. The Channel on the Order is updated to be the channel linked to the same supplier that the Catalog is linked to. The order splitting rule effectively allows the supplier to manage orders for their own specific products.

OTB Support for Customers to request quotes for catalog products or baskets and to restrict pricing to be only available on request:

• Enable Product Catalog managers to initiate contact with a Sales Agent to process a quote.
• Allow customers to request a quote for a catalog product.
• Submitted Quote requests will be assigned to the sales agents to review and process.
• Allow clients to request a quote for individual products instead of setting a price. 
• Includes the option to use a Price List or a Promotion to price the Product as "Price on Application". 
• There is also the ability to activate the "Request a quote" option on a fully priced cart for a particular channel.

In order to make it easier for users to configure certain accessibility properties to their liking or needs, we have created our Accessibility Menu.

The Accessibility Menu allows each user to customize certain accessibility settings in a specific way, so that DXP has a custom accessibility setup based on the needs of that user. It can be accessed via keyboard navigation using Tabulation, right after the “Skip to Content” option.

Pleae check the Content Security Policy by clicking here.

This feature applies the GDPR rules to the object entries. When the admin chooses to delete User's Personal Data, the object entries related to that user will also be deleted.

This feature allows developers to add email notifications directly into the notifications queue. It is useful when the email notification templates do not support a necessary custom logic that the template requires without requiring customers to re-write the entire email engine logic.

Now, users can build forms and content pages configuring them to trigger stand-alone actions with a click from the content page UI through the Page Builder.

We have added a new type of mapping that is available for editable type Action: you can see for example in a button fragment general options. To provide this out-of-the-box, we have evolved the button fragment to contain a configuration to switch between Link and Action buttons.

Now it is faster to implement experiences that rely on forms to interact with a business process, specifically in scenarios in which our customers decide to create their own custom form fragments according to their own look & feel or behavior.  

We have added a configuration for the user to decide which form fragments will be automatically mapped to each Object field type, when a form container is mapped to an object.

As it was done with 404 feature, now this feature is enabling our customers to fully adapt their users' experience providing an OOTB 500 error page fully customizable and allowing creation of new ones from scratch.

Fragments now provide editable types to map Link to Page field types that can be found in structures.

• The page creator can map the Link to Page field in a fragment from a content page.
• The Link to Page field is still mapped through a fragment on a Content Page even after the site is imported.

Before, changing cacheable configuration of a fragment would imply a "save" action and potentially a changes propagation action (no changes indeed if only the cache configuration was changed). This caused problems in performance and other aspects (such as wrong modification date).

From now on, and to avoid that, Fragments Cacheable property is managed in the Fragment options ellipsis menu: Fragment Sub-Elements Reference

This prevents fragment save + propagation when this configuration is modified, making it more efficient and resistant to issues.

In addition to that, we have added a cached label to better indicate which fragments have active cache.

IMPORTANT: BREAKING CHANGE as customers might expect the Cacheable configuration to be inside Fragments Editor, and now it’s placed in a different position.

Now users can create richer web content with the new Date-Time field available in Web Content Structures. To make it add more value, it is also enabled the possibility to map this new field to the editable of type Date-Time from any fragment, allowing users to customize the date & time values in content pages.

• New Date and Time field.
• Date-time values can be added to Web Content.
• Custom format in Fragment config.
• Custom date time display.

In order to improve the information we display at the Content Dashboard, we have added a new column with the Review Date value. With this new column, users have an easy way to view all contents where the review is needed. In addition, we have developed a new Filter to give the capability to show only the contents to be reviewed.

Note: This change will require a full reindex to work, so the new field can be propagated.

Filter by Review Date:

• All 
• To be reviewed

Traditionally, it has been complex and tedious to configure the necessary permissions that would make the Control Menu not visible for logged-in users. As soon as one permission was not configured properly, the Control Menu would be visible for these users.

This was previously managed by a specific logic inside the Theme, but now, we have made it easier to control and configure with a new setting.

Now, customers can easily control visibility of the Control Menu per role, within Site Settings >> Site Configuration >> Menu Access.

We have refactored the Page Configuration and Page Design Options to make them homogeneous and consistent. Now, users can access Page Design Options as a section of the Page Configuration (they were two separate views before).

In addition to that, we have made the UX homogeneous and more consistent with new Clay component styles. We have also regrouped items according to what users intend to do, making it more logical and user friendly to configure.

This feature adds a HTML template that provides more context for the email notifications users get when Message Added Email and Message Updated Email are triggered on Message Boards.
For this, three new terms were added:

• Message siblings: message thread of messages at the same level.
• Message parents: the message body of the parent message.
• Root message body: the message body of the original message.

Ability to filter the user agent (all, human, bot) for each redirection pattern, in Configuration.

Users can set different permissions for download and for viewing documents.