Release Notes
This feature introduces User Views in Frontend Data Sets, allowing end users to personalize how data is displayed by saving and reusing their preferred filters, sorting, and visualization mode across the platform.
Key Benefits:
Users can easily create and switch between custom views tailored to their needs
Personalized views can be saved and reused, improving productivity and consistency
Administrators can control whether Custom Views are available per Data Set
This feature improves how Frontend Data Set view state parameters are represented and managed within URLs, introducing a cleaner, more readable, and user-friendly encoding format. It replaces the previous fully URL-encoded JSON structure with a compact and maintainable serialization strategy while refining how and when view state parameters are persisted. These improvements ensure that URLs remain functional, easier to share, and simpler to debug.
Key Benefits:
Administrators, developers, and end users benefit from significantly shorter and more readable URLs that accurately reflect the current Data Set view state.
View state parameters are only added to URLs when users modify the Data Set view, reducing unnecessary noise and improving clarity.
Data Set states can be reliably shared, bookmarked, and restored across sessions and browsers.
Navigation behavior is improved by establishing push-based history updates as the default, enabling better navigation tracking and user experience.
From now on, most JavaScript files in Liferay DXP have hashed file names generated at build time. For example, a main.js file may appear at runtime with a randomly generated hash value in its name, such as This hash value represents a unique version of the file, so the browser can identify that the file’s contents have not changed. This allows the file to remain in the browser cache indefinitely when the infinite caching strategy is selected. In addition, the frontend caching infrastructure now supports both infinite caching and time/validation-based caching strategies. These strategies can be configured through Instance Settings. For those JavaScript files that cannot be hashed because they are generated at runtime by the server depending on some parameters, a new configuration is available in DXP to define their TTL and the option to add the Also, hashed files have a fallback strategy based on TTL + eTag if they are requested using their canonical name. This acts as a fallback for import map errors or legacy portlets that are not aware of hashed file names. Key Benefits:
The new Liferay DXP caching strategy for JavaScript files improves performance and stability. 1. Faster Page Loads: 2. Elimination of Stale Resources: 3. Reduced Origin Server Load: 4. Cache busting: |
This change promotes the Save Data Set view state to be recoverable when navigating back to it epic from Beta to General Availability, confirming the feature is stable and fully supported.