Users can now generate and download a PDF report of their event analysis, enabling seamless sharing of key insights with stakeholders.

Key Benefits:

• The PDF format ensures consistency when sharing insights across teams.
• The feature is accessible directly from the Event Analysis interface, simplifying the download process. 
• Users can optionaly choose to add a date range while downloading their pdf

When a user is deleted from DXP, the deletion now happens simultaneously in Analytics Cloud. To enable this, we’ve developed an API that automatically removes the same list of users from both DXP and AC in real time, ensuring data consistency across both systems.

Key Benefits:

• Processing Time: Depending on the number of users deleted, the process may take some time in Analytics Cloud. You can track the progress in Data Control & Privacy > Request Log under “Request Status.”
• Suppression Before Deletion: Each deleted user must first be suppressed before being permanently deleted in Analytics Cloud. As a result, you will see two requests per user—one for suppression and another for deletion.

We’ve introduced a new bulk operations feature that allows you to select multiple changes within a publication and perform actions on them all at once. This feature streamlines the process of managing multiple changes, saving you time and effort when working with large publications.

Key Benefits:

• Efficiency: You can now select multiple changes and perform bulk actions (like moving or discarding them) without needing to handle each change individually. This is particularly helpful in large publications where managing changes one at a time can be cumbersome and time-consuming.
• Improved Workflow: The ability to select and execute multiple operations at once significantly reduces the number of steps needed to manage your content, improving your overall workflow and productivity.

Enhancenment of the review change screen by adding a progress bar to provide clear, visual feedback during the publication process.When you initiate the publication, you’ll now see a progress bar that tracks the status of the publishing process, helping you understand how much time is left before the process is complete.

Key Benefits:

• Better Visual Feedback: The progress bar offers a clear, real-time indication of where you are in the publishing process, so you always know how much time is remaining.

• Enhanced User Experience: With the addition of the progress bar, the publishing process feels more responsive and user-friendly, providing you with a smoother workflow

We have introduced a new publication size classification feature to help users better manage and plan the publishing process, especially for "large" publications where there are many changes involved. This feature categorizes publications into three tiers: Small, Medium, and Large, based on factors such as the number of changes made and the size of the database. This will allow users to better understand the scale of their publication and take the necessary steps to avoid potential conflicts or performance issues during publishing. Publication Owners are also notified whenever a Publication has changed sizes.

Key Benefits:

• Improved Planning: With the new size classification, users can see the current "size" of their publication and allocate the appropriate time and resources for publishing. This helps avoid rushing through a publishing process that might take longer depending on the publication's size.

• Better Visibility of Potential Impact: The classification provides users with a visual indicator that highlights the size of the publication, offering transparency about what to expect during the publishing process. It also helps reduce the chances of errors or performance issues related to publishing "large" publications.

• Clear Communication: When users hover over the size classification, a helpful tooltip explains what the classification means and the potential consequences for the publishing process, ensuring users have all the information they need to make informed decisions.

This release introduces in-context translation for all the form fields 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.

Key Benefits:

• Faster time to publish localized forms: Translating directly in the editor reduces the steps needed to launch forms in multiple languages.

• Reduces reliance on external tools or workflows: Content teams can manage translations within the same interface they use to build pages, simplifying the process.

• Improves accuracy and consistency: Only the form fields marked as translatable are included, so there's less risk of translating the wrong content or missing something important.

• Better experience for global audiences: Visitors can complete forms in their preferred language, which can increase completion rates and engagement.Gives teams more control over localization: Editors can choose exactly what gets translated and when, without needing developer support.

Field visibility can now be configured based on values within the same custom fragment. This enables fields to dynamically show or hide based on user input, supporting more responsive and context-aware interfaces.

This update gives teams more flexibility when building custom fragments, making it easier to support complex use cases without additional custom code.

Customers very commonly deploy fragments through the deploy folder, we identified that we are missing one log once the fragment import finished. Until now Liferay added a message in the application server logs that show that the fragment import has started, but it never indicates when it finishes. Some advantages of logging when the import process finishes is that customers can check when the deployment is still in progress and when it ends, not only being informed in case of failures.