Improved Disk Space Utilization for Elasticsearch and OpenSearch Deployments

To reduce disk space usage on the search engine side, we have optimized default field mappings which no longer use stored fields. Instead, the platform uses the fields parameter as the default document field retrieval method.

Important Considerations for Administrators:

• Review Advanced Settings: Administrators should carefully examine the "Additional Type Mappings" and "Override Type Mappings" settings within the search engine connector configuration.

• Compare with Defaults: After reviewing the advanced settings, compare the existing mappings to the new defaults to identify potential adjustments. While stored fields are still supported, they are not recommended.

Potential Impact on Custom OSGi Modules:

While most users should experience seamless transitions, developers of custom OSGi modules that utilize Liferay's Java Search APIs may encounter changes in search response behavior. This could occur if the modules rely on specific fields being included in the search response. In such cases, developers may need to make adjustments to their modules to ensure correct functionality.

OpenAI can now be configured as a Text Embedding Provider for Semantic Search.

OpenAI offers two powerful third-generation embedding models promising lower costs, higher multilingual performance, and stronger overall performance compared to the predecessor models.

If your organization is already utilizing OpenAI's ChatGPT or other OpenAI Platform APIs, now you can take advantage of OpenAI's Vector Embeddings capability to deliver semantically more relevant search results through Liferay's semantic search feature (BETA) without the need to sign up for another service.

The Data Set Manager sorting tab has changed its purpose. From now on, the sorting options created under this section will be added to an Order Drop Down that is added to the Management Bar. This way, users will be able to sort by different criteria, even if those criteria are not visible in the Data Set items.

Admins can now leverage Data Set actions to send targeted requests to a specified endpoint. This enables dynamic updates to persisted objects, such as changing a user's status to "Inactive." While the request body content is currently static, this powerful feature provides a flexible way to manage and modify data within your system.

Data Sets now offer even greater customization power. Admins can directly add manual query parameters to the endpoint URL, enabling fine-grained control over data retrieval.

This flexibility allows you to:

• Filter Data: Apply specific filters to narrow down the results
• Select Fields: Choose the exact fields you want to retrieve
• Flatten Responses: Simplify complex data structures
• Search for Specific Terms: Find relevant information quickly

By tailoring the endpoint response, admins can provide a more curated and user-friendly experience for end-users.

Behind the Scenes:

The platform seamlessly reconciles these manual parameters with those generated by:

• Admin Configuration: Fields and Actions tab settings
• End-User Interactions: Filter and sort options selected in the UI

This ensures a consistent and efficient data retrieval process.

On top of that, admin users can also add or map fields manually to be displayed in the Data Set, so they will be able to bring the information back for those endpoints that don’t have the fields properly typed in the response.

The Database Upgrade Report is now enabled by default and offers expanded information compared to previous releases.

After running a database upgrade, check the reports/ directory for reports about what occurred in the system during the upgrade. The new upgrade_report_diagnostics file includes further details to diagnose any possible issues.

New properties and configurations have been added to allow control over the default user created for new virtual instances.

The instance admin user can be defined by the system admin upon instance creation or be disabled completely. This adds an immediate additional layer of security to a new virtual instance.

This update enhances the transparency and accountability of your Process Builder definitions. By tracking modification dates and user information, you can easily identify changes, troubleshoot issues, and ensure compliance. With this improved version history, you can effectively manage your processes and make informed decisions.

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.