In Notification Templates, users will now be able to send emails based on Account, Organization and Regular Roles.
Notification recipients will follow the permission framework that is already in place.
|
Release Notes
Users can now create picklists beginning with capital letters. One key feature is that now users will be able to filter by Active and Inactive values.
This will be a new configuration under System Settings and when enabled, will allow notifications from the workflow to respect the scope of the site. |
Objects is used for a wide range of use cases, some of them more technical than others. This feature will allow users to configure where they want their objects to be listed. Thus, creating unnecessary complexity and reducing cognitive load on other users.
Users can now configure their objects to observe the guest user’s locale and send email notifications based on the guest user’s language preference.
The guest user’s language preference is determined by the language the guest user used when submitting the form. If a locale cannot be determined or a notification template does not exist, then the notification will be sent in the instance’s default language.
For those Objects that have the translation active, users can not get this entry information using GraphQL. In order to improve GraphQL capabilities, we have exposed the _i18n properties, so any user can retrieve it.
Liferay has expanded GraphQL capabilities to match the functionality of REST APIs for managing object entries. Users can now transition object entries from Draft to Approved status using GraphQL, providing more flexibility and control within the development process. |
For making the Sign In portlet related functions easily customizable for the end users we want to simplify the portlet as much as we can. We need to remove all it’s configuration or functionality that can be handled in higher level.
Currently, the customer has to resort to email reports to see their autoscaling. We are making this information much more available and searchable, allowing the user to better understand their autoscaling behaviour.
Liferay DXP provides a variety of developer tools that include a robust build script framework, lightweight CLI utilities, and IDE tools. We have recently released new versions of Liferay Workspace and the IDE tools, which include Liferay Developer Studio, Liferay Eclipse Plugin, and Liferay IntelliJ Plugin. The main benefits include:
Alignment with the platform itself: The tools now support our quarterly releases, giving access to development on Liferay DXP's latest features.
Latest Java version support: Compatibility with JDK 17 and 21 provides developers with enhanced security, improved performance, and the newest capabilities of the Java platform.
- Upgraded development environment: Support for Gradle 8 enables improved build automation features and performance.
Liferay now allows users to sort Custom Objects entries based on data from related objects. This enhanced functionality provides greater flexibility and control when managing complex data structures, enabling users to organize information more effectively.
Feature Status Change
It is now possible to select Date Times as a product option type, configuring purchase options for products based on date, times, time zones, and durations, allowing for the sale of time slots.
Feature Status Change
Users can activate the content creation prompt with a single click by leveraging AI capabilities directly within the CKEditor for seamless and efficient content generation. Requires a valid OpenAI API key.
Feature Status Change
Manage contacts directly related to accounts like phone numbers, emails, websites, addresses.
A new Contact Tab in Account details page with 2 internals tabs was created:
- Addresses
- Contact Information
Users with “Accounts > Account Entry: Manage Addresses” permission should be able to manage their contacts with all these actions:
- Add
- Edit
- Remove
- Mark as primary
Example of managing a phone number:
Users without “Accounts > Account Entry: Manage Addresses” permission should be able to only view the existing phone number entries.
Feature Status Change
Map individual specifications, choose the order, and create clear, informative product pages that drive sales and enhance the customer experience. Simplify product page creation and empower your business with this new feature.
Feature Status Change
Our new Bulk Permission Management empowers administrators to modify access rights for multiple pages effortlessly. This new feature offers a multitude of benefits:
- Effortless Management: Save valuable time by managing permissions for multiple pages simultaneously.
- Enhanced Security: Gain complete visibility into page access, ensuring all intended audiences can access the content they need.
- Optimized Accessibility: Quickly identify pages not accessible to Guests and make adjustments for optimal user experience.
Feature Status Change
Now it is possible to easily identify the content you have created and any recent content you generated. This enhancement streamlines and optimizes this workflow.
Feature Status Change
The goal here is to make the users able to move changes between publications. This is needed because sometimes users do not want to publish an entire publication, but also do not want to revert the changes which will not be published actually. With this feature users can move changes from one publication to another, creating subsets of changes, and publish them separately. For readers with technical knowledge: this is similar to cherry-pick-ing a commit in git from one branch to another.
Feature Status Change
Simply provide a descriptive prompt and let DALL-E generate the perfect image to complement your content strategy, saving you valuable time and resources. Leverage AI to spark new ideas and generate unique concepts that perfectly align with your content needs. Explore a world of visual possibilities!
Feature Status Change
The Custom User Attributes functionality of Asset Publisher is sometimes difficult to understand for the customer, so we recommend the users use Content Sets + Experiences instead. |