This functionality refers to tracking events related to non-default asset types and visualizing the data on a dashboard. From now on, customers will no longer be able to use this specific method to track views of non-default asset types and visualize this data on a dashboard in Analytics Cloud
Using custom event tracking is the recommended way to track your custom assets from now on.
Release Notes
This improvement allows users to customise the appearance of their Liferay instance more effectively with new properties in the .yaml
file for Theme CSS and CSS Client Extensions.
Key benefits:
Admins can personalise the interface for both the admin panel and the entire platform.
A more cohesive, branded appearance will improve usability and satisfaction for all users.
Allows fine-grained control over where customisations are applied.
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.
The updated Clay chart colour palette improves accessibility and usability by creating more contrast and adding more variations. Now users can easily distinguish charts, icons, and field sets, reducing confusion and improving clarity.
Key benefits:
Now we have more design flexibility for Liferay’s current and future products.
Accessible and distinguishable colours that will improve and unify the platform usability and UI.
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.
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.
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.
With this improvement, the Data Migration Center allows users to export and import Object Entries using CSV files. Not all field types are supported but many of the most used ones are:
Supported field types: dateandtime, date, decimal, integer, longint, longtext, precissiondecimal, richtext, text and picklist.
In order to help users, only supported fields are available for exporting at the UI. As new types are allowed, they will appear available in the UI.
We are excited to introduce enhancements to streamline your cloud management experience! With our updated cloud console view, you will have a detailed breakdown of subscription metrics per environment, empowering you to manage resources more effectively. Additionally, our new storage consumption tracker offers real-time insights into project storage usage, ensuring you're always informed about quota limits.
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 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.
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.
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:
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!
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.
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.
This set of improvements aims to simplify the manual work users must do to resolve conflicts when publishing a publication. Now, instead of raising a conflict to be resolved manually by the user, the system will try to overwrite conflicting changes in production with the modifications done in the publication, meaning that the Modification and Modification deletion conflict types won’t be presented for the user anymore.
In the case of a Deletion modification conflict, the system won’t resolve it automatically, but now it makes it easier to keep the modifications made in the publication. In the Conflicting changes screen, we added a button with the option to "Restore in Production" for conflicts in which the asset was deleted from production and is now in the Recycle bin.
Key benefits:
Reduce the amount of manual work by automatically solving most of the conflicts.
Improve user satisfaction and reliability on publications by ensuring that assets supported by Recycle Bin can be quickly restored, avoiding requiring the user to discard needed changes.
This feature enables users to export a CSV file containing detailed information about segment membership, including a list of all known individuals within a segment and their associated data, providing valuable insights for stakeholders.
Highlights:
Export Capability: Allows users to generate a CSV file containing segment membership data.
Comprehensive Details: Includes a list of all known individuals in a segment, with details such as names and email addresses.
Actionable Insights: Equips stakeholders with valuable data for analysis and decision-making.
Provided an option to turn the “Out-of-date” feature on/off. When turned on (the default behavior before this release), ongoing publications created in previous Liferay versions were labeled as “Out-of-date” after the upgrade and could not be modified or published. This feature is now off by default, and users can publish these publications without Liferay support.
Key benefit:
Increase manageability over publications and the ability to publish any previous modification, including after Liferay upgrades.
This release introduces in-context translation for text-based form fields (Text, Rich Text, and Textarea) directly within the page editor. This empowers content creators to easily create localized form experiences for their users, enabling them to complete forms in their preferred language. Only designated localizable form fields will be translated, ensuring precise control over localized content. |
Previously, when managing complex data models, users must create scripts or code in order to make changes to multiple related objects. Now users are able to configure multiple objects as if they are one object. Related child objects now inherit permissions and account restrictions and more from the top level parent, making object management more convenient.
Key benefits:
Simplifies the management of multiple objects through a configuration on the relationship between objects
Permissions and Account Restrictions for the child objects are inherited from the Top level parent
API endpoints are nested under the same namespace of the top level parent
Allow users to move Object Definitions and Entries between environments
Key benefit:
Addresses a feature gap when moving applications built on Liferay between environments
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.
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.
Users are now able to properly search in the portal using the Search widget (in applications that have data restricted by account).
To reduce the maintenance costs of providing a full document’s preview, the following changes are being introduced:
“No preview available” state when the file size exceeds the preview size limit.
Merge “File Entries” and “PDF Preview” settings under “File Preview Limits”
Rename "File Size Limits" to "File Upload Limits" with a reviewed and more understandable Description copy
The user is being informed that the generated preview may not correspond to the entire document
This development introduces the ability for the user to set the file size at asset library’s level. This settings will override the already existing one at System level when the latter is bigger. As a general rule, when both are set the lowest applies.
When adding validations in Objects, many times it is necessary to validate dates against the current date.
Key Features:
Dynamic Date Comparison - Users can compare a selected date with the current system date. This empowers you to create rules that trigger based on the relationship between a date field and the present date.
Versatile Date Range Checks - Validate whether a date falls within a specified date range relative to the present date.
Users can add read-only fields to object definitions that automatically increment for each new entry.
Key Features:
Customize Starting values - Users can set a starting value. This flexibility allows for better alignment with specific business needs and workflows
Customize labels - Users can set prefixes and suffixes to provide alphanumeric keys appended to the incrementing values
Users can add validations to verify field values that, when used in combination, are unique.
Limitation: numeric fields such as Integer, Long Integer, Decimal, Precision Decimal will be stored as null.
Validate relationships to prevent duplicate names in child objects.
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.
Default View and Download permissions for documents have been adjusted to match the behavior prior to the changes introduced in LPD-16744, restoring the expected user experience.
Highlights:
The View and Download permissions will be linked by default when uploading documents through the single and multiple file uploaders
The Permissions configuration UI is improved so users can more easily recognize that the View and Download permissions are separate permissions
The Download permission is now automatically included when a user shares a document and assigns permissions
We added External Reference Codes for references in widget configurations in Content Management applications. This helps promote data integrity when pages and their widgets are migrated across environments.
Highlights:
References within the following page widgets now use ERC’s instead of internal ID’s:
- Announcements
- Web Content Display
- Category Filters
- Questions
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.
Official release of Liferay Data Sets, moving from Beta to Release! Data Sets are a powerful and flexible way to retrieve, manage, visualize, and interact with structured data in Liferay DXP. Built on top of Objects and leveraging Liferay’s robust ecosystem, Data Sets exemplify the “build Liferay with Liferay” philosophy. With seamless integration with compatible Headless APIs, administrators can easily configure Data Sets and empower end-users with a rich, customizable experience for consuming and interacting with data.
Key benefits:
Retrieve Data: Fetch information from any compatible Headless API to use as a Data Set source.
Manage Flexibility: Administrators can customize what parts of the API response are included, along with filters, sorting options, and available actions.
Visualize Data: Multiple visualization options make it easier than ever for end-users to consume data meaningfully.
Enable Interaction: End-users can interact dynamically with data using the filters, actions, and tools configured by administrators.
To ensure the quality, stability, and modernity of Liferay DXP, we've updated to React 18, bringing significant benefits in security, performance, and compatibility. This update is critical to maintaining DXP's status as a robust and future-proof platform.
Key benefits:
Security Enhancements: Older library versions can expose vulnerabilities. Upgrading to React 18 mitigates these risks by incorporating the latest security patches.
Performance Improvements: React 18 introduces features like concurrent rendering, which enhances responsiveness and load handling for better user experiences.
Enhanced Compatibility: Upgrading ensures DXP aligns with modern tools and frameworks, minimizing integration challenges and future-proofing our development processes.
Continued Support: Staying current with React’s ecosystem ensures ongoing access to community updates, bug fixes, and innovations.