Currently, in Liferay Forms, users can customize field labels for ease of reference in the page’s HTML.

Now, users are able to fully customize and reference in the HTML the remainder of the Form.

We added the permissions assigned to Custom and Modifiable Object Entries to the Objects Entries APIs' nested fields. This will be useful when we export/import Object Entries with permissions through Batch.

When the access token is near the expiration date, the portal sends notifications to the System Administrator about it.

Liferay Cloud currently supports Java JDK 8 and 11, but the industry is moving towards newer Java versions like JDK 17 and JDK 21. To ensure that Liferay Cloud remains modern, allows our customers to leverage the newest security patches, and boosts overall performance.

A pack of improvements to the usability of the logs page. Clients now can troubleshoot more effectively, be it by better handling multiple filters or by selecting/copying logs without the use of the log inspector.

Feature Status change:

Tracking events related to non-default asset types and visualizing this data on a dashboard

Feature Status Change

Segments that are just static groups of users

Feature Status Change

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. Though the defined RESTful APIs and schemas, clients can perform CRUD operations to keep resources in sync.

Feature Status Change

The vendor has deprecated OpenSSO/OpenAM, so there is no reason for us to keep it. The alternative, which is PingAM can be integrated using our existing OpenID connector or SAML Authentication.

Feature Status Change

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

Feature Status Change

The Forms feature is going into maintenance.

Feature Status Change

Object Layouts are going into maintenance.

Feature Status Change

Object Views are going into maintenance.

Feature Status Change

This feature introduces the ability to create and manage custom picklists for product specifications. Users can now define specific values for product attributes, improving data consistency and efficiency. The feature includes the option to create new picklists or add existing ones directly on the specification page.

Feature Status Change

A new out-of-the-box (OOTB) email notification template based on Objects. This template will be automatically sent to the order creator when an order status changes to 'pending'.

The notification includes:

• Order number

• Order date

• Account name

• Shipping address

• Order item summary

• Order total

We will move away from Commerce notifications and deprecate them and we will use Objects for the new ones.

We added several API endpoints for Documents & Media to improve programmatic management of these entities.

Highlights:

• Users can now add, delete, and retrieve document types via headless API (DocumentDataDefinitionType)

• Users can now add, delete, and retrieve document metadata sets via headless API (DocumentMetadataSet)

It is now possible to subscribe to documents and folders, allowing users to receive notifications when they are updated.

Highlights:

• Users can now subscribe to documents and folders through the “Subscribe” action and through the Subscribe icon in the Info Panel

• If a user subscribes to a folder, all documents and subfolders within it will be automatically subscribed to as well

During the publishing process, users can both define and manage permissions, as well as schedule publication dates for their web content. When creating content for the first time, users will have the opportunity to conveniently review and manage permissions. Furthermore, when editing previously created content, users can also adjust permissions directly from the editor view. Additionally, users can easily select the desired publication date for their content during the publishing process.

• Users can select and reorder categories for a blog’s friendly URL, so they can preview the order of the categories in the friendly URL and determine how the categories will be presented in the friendly URL along with the title.

• Users are able to set different values for the asset types separators in the friendly URLs. Also, they are able to reset to default value, so for those asset types that they have clicked on this option, the separator will be the value defined by default for those specific asset types.

Until now, there was no way in batch engine to export and import object entries and their permissions simultaneously. This new capability allows users to do that, streamlining workflows and reducing manual effort.

Key benefits:

• Execution in only one call.

• Possibility for users to choose to take into account (or not) permissions with object entries.

Data imports, using batch engine, now allows users to preserve content creator information (if required). Previously, imported content with batch was always assigned the user performing the import, resulting in loss of original authorship data when moving content. This update ensures accurate attribution of content ownership (if required).

Key benefits:

• Able to keep critical user information during data promotion between environments

• Can be configured separately per import process

Implemented proactive access token management with automated email notifications. Users will now receive alerts 1 month, 10 days, and 1 day prior to token expiration, allowing for timely renewal and preventing service disruptions. Notifications are automatically cancelled if a new token is generated.

Key benefits:

• Users are notified before token expiration, allowing for timely renewal and uninterrupted access.

• Reducing administrative overhead, as automated notifications eliminate the need for manual monitoring and intervention.

• By prompting timely renewals, the risk of using expired and potentially compromised tokens is minimized.

The vendor has deprecated OpenSSO/OpenAM, so there's no reason for us to keep it. The alternative, which is PingAM can be integrated using our existing OpenID connector or SAML Authentication.

The SSL Certificate Management view now provides expiration alerts for certificates nearing expiration (e.g., within 30 days) and those that have already expired. Certificates must now be defined exclusively through the LCP.json file, simplifying management and ensuring consistency across deployments. This update reduces manual errors and ensures secure and uninterrupted deployments.

Highlights:

• Expiration Alerts: Notifications for certificates nearing expiration and those already expired, with clear visual indicators.

• Exclusive LCP.json Configuration: Certificates can only be defined through the LCP.json file.

• Improved Visibility: Organized list view showing certificate names, types, associated domains, and expiration dates.

• Proactive Management: Tools and alerts to help users maintain secure SSL/TLS configurations.

The Marketplace release of the Liferay Connector to OpenSearch 2 provides an alternative to Elasticsearch for Self-Hosted Liferay deployments.

This connector integrates Liferay DXP with OpenSearch 2.12+, the open source and enterprise grade search engine. OpenSearch offers lexical search for text data, robust scalability and extensibility, and vector search for applications using embeddings, such as Liferay's Semantic Search.

The installation of this app requires specific configurations covered in the official documentation. For detailed compatibility information, see the Search Engine Compatibility Matrix.

The OpenSearch integration is currently a Beta feature with the intention to make it GA in the future.

Liferay Cloud now provides CI/CD support for Client Extensions on Liferay PaaS. Developers can integrate Client Extensions into their Git-based CI/CD pipelines, ensuring automatic builds and deployments alongside core Liferay services. This update enables automated validation, independent deployments, and faster release cycles for Client Extensions.

Highlights:

• Dedicated CI/CD Pipeline: Separate build pipeline for Client Extensions to prevent conflicts with core Liferay services.

• Automated Builds: Every commit triggers a new Client Extensions build, packaged as a LUFFA archive.

• Independent Deployments: Client Extensions builds deploy separately, improving release flexibility.

• Seamless Integration: Works with existing Git-based workflows on Liferay PaaS.

• Zero Downtime Deployments: Deploy client extensions without affecting the main Liferay service.

Liferay 7.4 introduces the ability to manage language translations directly within client extensions. This enhancement allows developers to provide multilingual support for custom labels and properties without relying solely on OSGi bundles.

Key benefits: 

• Developers can now define and manage language keys and translations within the client extension itself, ensuring that all labels and custom properties are displayed correctly across different languages.

• This feature eliminates the issue of untranslated labels with dashes, providing a consistent and professional appearance on multilingual sites.

• Simplifies the process of adding translations, reducing the need for manual intervention and external OSGi bundles, thus accelerating the development and deployment of multilingual features.

• Empowers developers to create more flexible and fully localized custom elements and themes, enhancing the overall versatility of the Liferay platform.

Now user are able to:

• Configuration of document size for copying in D&M

• Bulk copying of documents and folders

• Currently the copy action for documents and folders is able to be performed in Portal without fully respecting the site-asset library relationship. The expected behavior is:

  • An asset library must be connected to a site in order to copy a document over to the site

  • A document cannot be copied from a site to an asset library (only the other way around)

  We can enforce a stricter check when performing the copy action between asset libraries and sites. Instead of the end user receiving a success message when copying a document to a disconnected site, an error message should appear telling the user to set the connection first.

• Document Types contained in a document are being copied in Documents and Media so that they can be easily reused.

• Categories and Tags in Documents and Media are being automatically copied so they can be easily reused on a new site.

With this development, the publication of Knowledge Base articles will be schedulable, in particular, the feature is so designed:

• The primary Publish button will have an arrow down with the “Publish” option, that will immediately publish the article, and the “Schedule” one.

• Clicking the Schedule option, will make a modal appear so the user can set a date and time for the article to be published.

• The Scheduled article will have the SCHEDULED status that will change to APPROVED on the scheduled date

• A tooltip with the scheduled date information will appear when hovering the question-circle-full icon placed next to the SCHEDULED state.

• Editing a scheduled article will provide the user the ability, by clicking the primary button that has turned into “Scheduled”, to:

  • Cancel the operation

  • Publish Now

  • Schedule: this option will save the article, date & time changes and the user will return to the previous screen before entering edit mode

• Additional feature: A Knowledge Base article deletion action will move it to the Recycle Bin so that it can be restored.

This feature allows you to leverage the functions of Liferay’s caching framework. Our current measurements indicate about 10%/30% performance increase in database writing operations, also 10 times faster reading performance!

The user experience of the Management Toolbar present in multiple applications (Web Content, Blogs, Documents & Media) has been improved:

• Separate sections for filter and order.
• Changed “+” with “New” for clarity.
• Moved info icon to the right.

Now, admins can customize the configuration of the Rich Text Editors with this new client extension, allowing them to set the toolbars that are available on different applications. In the form, you will have to define the instances in which the configuration will be taken into account as well as the JS that contains the configuration:

We refactored the way Liferay scripts were managed, so admins can define stricter policies like:

script-src '[$NONCE$]'; script-src-attr 'unsafe-inline';

Limitations: If a policy like the one above is configured, the parts of the product that uses a rich-text editor will not work correctly. Analyze your scenario to identify how strict your policy can be in order to make the solution work.

Now users can configure the values for the following properties from settings (system, instance or site settings):

• session.timeout.auto.extend
• session.timeout.auto.extend.offset

When the Upgrade Report is enabled, the output directory of the report can be configured with the new portal property upgrade.report.dir

If this property is not set, the upgrade report can be found in the default directory:

• portal-tools-db-upgrade-client/reports for the upgrade tool.
• {liferay-home}/reports if upgrade was executed on startup.

With this feature we extending the SCIM implementation with User Group un/provisioning as well with the User Group membership un/provisioning.

Previously customers would add captchas using a TagLib. But this is no longer useful since customers are not deploying JSPs. The Captcha API enables this functionality to be used in arbitrary contexts.