2023 Q3 Quarterly Release
Architecture
Enable customers to manage data from third-party systems through Liferay
Users can now manage data from external systems through Liferay without persisting data on DXP.
With extension support, they can also connect with other systems in a standard way and create experiences in Page builder through Liferay experience management as other objects, and manage permissions through Liferay role management. Users can already, without a single line of code, manage data from Salesforce through DXP.
Features added in this Release:
Objects as a proxy
Proxy Objects allows users to manipulate data directly in external systems, such as Salesforce. This feature provides the ability to always interact with live data, avoiding duplicating and conflicts between the systems.
Now, Liferay includes a connector to Salesforce for proxy objects. With it, you can integrate your proxy object with custom Salesforce objects, using Salesforce as an external storage system
Advanced notification capabilities and extensibility
With enhanced automations capabilities, users can now manage more advanced notifications, not only having more variables and expressions to be used to dynamically compose their email and users notifications. In addition, the support for extensions allows customers to add new notification types, such as: WhatsApp, Line, and Slack for example.
Features added in this Release:
Use relevant user information on notification template settings
New terms available in notification templates related to the current user and entry creator were added, in order to improve the power of dynamically generated templates.
Added terms:
[%CURRENT_USER_ID%]
[%CURRENT_USER_FIRST_NAME%]
[%CURRENT_USER_LAST_NAME%]
[%CURRENT_USER_EMAIL_ADDRESS%]
[%OBJECT_AUTHOR_ID%]
[%OBJECT_AUTHOR_FIRST_NAME%]
[%OBJECT_AUTHOR_LAST_NAME%]
[%OBJECT_AUTHOR_EMAIL_ADDRESS%]
Set notification configurations
This feature allows power users to configure the intervals to retry to send the email notifications when the first instant attempt fails.
Use variables from the entry of the related object (single relationship) on notification template
Evolving the power of notification templates, this feature allows users to use variables not only from the object in context, but also from related objects.
Improving Low-code Data Modeling capabilities
More use cases enabled through low-code, accelerating time to value and the scalability of those solutions. Some of the highlights:
Multi-language support for object entries
New encrypted and date-time field
New rules for making a field read-only at API level
Object Data GDPR compliance
Features added in this Release:
Default Value in Object Fields
This feature allows the user to define a default value for object picklist fields. Default Value can be configured for custom fields from both Custom and System Objects.
Enable configuration to define a field as unique data only
This feature allows the user to require that a field's values be unique inside of that column. When this is configured, the system will not let two records have the same value for that field, behaving similarly to a key to that entry.
Date-time fields for Objects
This feature adds a new field type “Date and Time”. A Datetime value stores a year, month, day, time, and time zone. With this field, users will also be able to create time ranges, manage priorities and order entries well, and to give more context and assertiveness to the data.
Support Translations for Objects
This feature empowers users to create content use cases on top of objects framework, allowing admins to enable localization for objects' entries text fields.
Support Read-only Fields in Objects Framework
This feature adds read-only support for all object fields types, making sure users are not able to update those fields from both the UI or APIs, only the system can: through default values or actions, for example.
Create and update system object entries through Objects Actions
Evolving the extensibility of system objects through objects framework, this feature allows users to create and update System Object entries through Object Actions as they can with Custom Objects.
Retrieve my object log information from my Objects definition headless API
In order to get in context entry history information, this feature introduced the endpoints to retrieve the object entry log information through the object headless API suite. Allowing users to compose experiences with the specific entry update history.
Delete fields from published Objects
This feature allows users to delete fields from published objects that were added before the object got published, giving more flexibility to admin users.
Object framework to support basic column data encryption
This feature allows users to enable the basic encryption support for object fields.
Organizations as system Objects
This feature shows the Organization application as a System Object in Objects Admin, allowing users to extend it and related with other objects available.
Commerce
Automated Order Splitting
OTB workflow that will split a mixed basket of goods a customer places from different suppliers, into individual supplier orders to support marketplaces and webshops where partners are also present.
Used in Conjunction with Supplier Accounts, this object's rule, once configured, splits Commerce Orders automatically by the Catalog that each Product belongs to. The Channel on the Order is updated to be the channel linked to the same supplier that the Catalog is linked to. The order splitting rule effectively allows the supplier to manage orders for their own specific products.
Price on Application
OTB Support for Customers to request quotes for catalog products or baskets and to restrict pricing to be only available on request:
Enable Product Catalog managers to initiate contact with a Sales Agent to process a quote.
Allow customers to request a quote for a catalog product.
Submitted Quote requests will be assigned to the sales agents to review and process.
Allow clients to request a quote for individual products instead of setting a price.
Includes the option to use a Price List or a Promotion to price the Product as "Price on Application".
There is also the ability to activate the "Request a quote" option on a fully priced cart for a particular channel.
Supplier Order & Catalog Management
Make it easier for suppliers to manage products and orders with an OTB account type supplier, and a Generic Supplier role, that grants them the ability to manage their own product catalog(s) and channel. With this, they will have the ability to create product bundles with SKUs from Supplier Catalogs.
New Account Type of Supplier. A Supplier can be linked to a catalog and to a channel to allow the supplier to manage their own products, price lists, promotions, catalogs, discounts, inventory and channel in order to be able to fulfill orders for their own products.
Experience
Enable AI powered content creation features
This integration with OpenAI ChatGPT will allow content creators to get suggestions for their web content from the most trendy AI content generator.
Features added in this Release:
Integration of ChatGPT to contribute content through Web Content editor
We have enabled the integration with ChatGPT so texts can be generated from the Web Content editor.
There is a new button on the CKEditor (web content editor) that triggers a modal where users can write a prompt (instructions for the bot) and add additional parameters such as tone and length.
Allow customers and prospects to understand our Accessibility Strategy
Let our customers understand our Accessibility Strategy and communicate the release of our VPAT (Voluntary Product Accessibility Template) / Accessibility Conformance Report by the end of Q2.
Digital Experience Platform Accessibility Conformance Report
Features added in this Release:
Accessibility Menu to allow users to customize their accessible admin experience
In order to make it easier for users to configure certain accessibility properties to their liking or needs, we have created our Accessibility Menu.
The Accessibility Menu allows each user to customize certain accessibility settings in a specific way, so that DXP has a custom accessibility setup based on the needs of that user. It can be accessed via keyboard navigation using Tabulation, right after the “Skip to Content” option.
Management
Configuration and Definition of Dataset Views for Headless Resources
With this new dataset manager, customers will be able to define in a low-code way, views for displaying and manage data leveraging the headless APIs
Enable users to customize what to be shown in a data view.
Reduce the effort to customize the view as it’s done via UI.
Reduce the amount of work needed to adjust the UI after a platform upgrade.
Features added in this Release:
Configuration and Definition of Dataset Views for Headless Resources
A new application, named Data Set Manager (Data Sets in the Control Panel) allows admins to define through a UI data set views for the different headless resources available. Admins will be able to choose the data source, as well as configure the columns to be available and the pagination options for the different views.
To enable this feature:
Add feature.flag.LPS-167253=true to your
portal-ext.propertiesGo to Instance settings > Feature Flags and enable “Data set manager” in the Beta tab.
In addition to the data set manager, two additional components have been added to provide the full value to the users:
A new fragment, so these views can be integrated in any content page. Content managers will select the data set view to display on each fragment.
A new frontend client extension, Frontend Data Set Cell Renderer, that allows developers to customize how any field of the data set view is rendered, providing total control of the look and feel of any column.
Content Security Policy
Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross-Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft, to site defacement, to malware distribution
Features added in this Release:
Content Security Policy
Feature Description
Additional New Features and Capabilities
Business Process Management and Objects
Features added in this Release:
Object Data GDPR compliance
This feature applies the GDPR rules to the object entries. When the admin chooses to delete User's Personal Data, the object entries related to that user will also be deleted.
Add e-mail notification in the Notifications queue
This feature allows developers to add email notifications directly into the notifications queue. It is useful when the email notification templates do not support a necessary custom logic that the template requires without requiring customers to re-write the entire email engine logic.
Experience Management
Features added in this Release:
Mapping and triggering standalone Object Actions from page builder
Now, users can build forms and content pages configuring them to trigger stand-alone actions with a click from the content page UI through the Page Builder.
We have added a new type of mapping that is available for editable type Action: you can see for example in a button fragment general options. To provide this out-of-the-box, we have evolved the button fragment to contain a configuration to switch between Link and Action buttons.
Configure which custom fragments are automatically mapped in Form Container
Now it is faster to implement experiences that rely on forms to interact with a business process, specifically in scenarios in which our customers decide to create their own custom form fragments according to their own look & feel or behavior.
We have added a configuration for the user to decide which form fragments will be automatically mapped to each Object field type, when a form container is mapped to an object.
Customize your site's 500 error pages
As it was done with 404 feature, now this feature is enabling our customers to fully adapt their users' experience providing an OOTB 500 error page fully customizable and allowing creation of new ones from scratch.
Usability improvements in the navigation menu admin application
Improves the overall usability of the application and also the ability to reorder and add items. Also improve the accessibility of functionality:
Now it is possible to move the items in a navigation menu using the keyboard.
There is more flexibility when adding items to the navigation menu since you can now select the place where you want to add them to.
Mapping Link to Page field to Fragment
Fragments now provide editable types to map Link to Page field types that can be found in structures.
The page creator can map the Link to Page field in a fragment from a content page.
The Link to Page field is still mapped through a fragment on a Content Page even after the site is imported.
Better configuration and UX of Fragments Cacheable property
Before, changing cacheable configuration of a fragment would imply a "save" action and potentially a changes propagation action (no changes indeed if only the cache configuration was changed). This caused problems in performance and other aspects (such as wrong modification date).
From now on, and to avoid that, Fragments Cacheable property is managed in the Fragment options ellipsis menu: Fragment Sub-Elements Reference
This prevents fragment save + propagation when this configuration is modified, making it more efficient and resistant to issues.
In addition to that, we have added a cached label to better indicate which fragments have active cache.
IMPORTANT: BREAKING CHANGE as customers might expect the Cacheable configuration to be inside Fragments Editor, and now it’s placed in a different position.
Page Builder support for displaying Object Relationships
Now, when creating pages and display pages to visualize object entries, users can easily display related object entries. To enable this, we have added:
In a one-to-many or many-to-many object relationships scenario, new related item collection providers access information of the “many” side of a one-to-many and many-to-many relationships. For example: a Countries object, and a related “cities” object for cities in those countries. This new capability allows users to easily list the cities that belong to a country, and other data from each city, via a related item collection provider.
In a one-to-many object relationship, if we are listing or displaying the items of the “many” side, information of the “one” side is available for direct mapping as well. For example: a “Countries” object, and a related object for cities in those countries. When listing the cities, this new capability allows to easily display the country which each city belongs to.
Attachment field attributes (such as download URL and file size) are now available for direct mapping.
New date-time field available in Web Content Structures
Now users can create richer web content with the new Date-Time field available in Web Content Structures. To make it add more value, it is also enabled the possibility to map this new field to the editable of type Date-Time from any fragment, allowing users to customize the date & time values in content pages.
New Date and Time field.
Date-time values can be added to Web Content.
Custom format in Fragment config.
Custom date time display.
New column on Content Dashboard (Review Date)
In order to improve the information we display at the Content Dashboard, we have added a new column with the Review Date value. With this new column, users have an easy way to view all contents where the review is needed. In addition, we have developed a new Filter to give the capability to show only the contents to be reviewed.
Note: This change will require a full reindex to work, so the new field can be propagated.
Filter by Review Date:
- All
- To be reviewed
Configuration to control which users can see the Control Menu
Traditionally, it has been complex and tedious to configure the necessary permissions that would make the Control Menu not visible for logged-in users. As soon as one permission was not configured properly, the Control Menu would be visible for these users.
This was previously managed by a specific logic inside the Theme, but now, we have made it easier to control and configure with a new setting.
Now, customers can easily control visibility of the Control Menu per role, within Site Settings >> Site Configuration >> Menu Access.
Refactored UX of Page Configuration
We have refactored the Page Configuration and Page Design Options to make them homogeneous and consistent. Now, users can access Page Design Options as a section of the Page Configuration (they were two separate views before).
In addition to that, we have made the UX homogeneous and more consistent with new Clay component styles. We have also regrouped items according to what users intend to do, making it more logical and user friendly to configure.
New template added for Message Board notification emails
This feature adds a HTML template that provides more context for the email notifications users get when Message Added Email and Message Updated Email are triggered on Message Boards.
For this, three new terms were added:
Message siblings: message thread of messages at the same level.
Message parents: the message body of the parent message.
Root message body: the message body of the original message.
User agent filter for redirection patterns
Ability to filter the user agent (all, human, bot) for each redirection pattern, in Configuration.
Separate permissions of download and view documents in DAM
Users can set different permissions for download and for viewing documents.
New options while using ratings in D&M
Option of rating added to Folders and the endpoints for Documents rated by me, Folders rated by me have been created.
Manage Knowledge Base folders and Hierarchy
Provide users with a simple and effective way to view, access, and manage the Knowledge Base folder hierarchy. It is included:
Drag and drop experience for moving content.
Search for content in the Knowledge Base management.
Using the action menu to manage folder.
Review and Expiration dates in Knowledge Base articles
Ability to set expiration and review dates for articles, and to view which articles are pending expiration.
Enhanced navigation and interactions in Knowledge Base
Improved navigation through the different tabs and pages in Knowledge Base in the manage toolbar, sidebar search, sidebar primary button, priority and general interactions.
Table view in Knowledge Base
Table View is displayed in the Knowledge Base.
New filters capabilities in Documents & Media
Now Content Editors can easily find the documents they are looking for thanks to the new filters added to Documents & Media.
Three (3) new filters have been added: categories, tags and extensions:
Documents and Media version history page
Page listing the version history of a document to help managing different version.
Avoid MB dependency on font awesome
Priority icons to MB CSS are added to avoid to force enabling font awesome in the whole portal.
Publications
Features added in this Release:
Enable Change Tracking for Contact Info
We have made the organization’s addresses, phone numbers and email addresses changes tracked. These can be added to a Publication from now on.
Show the most important changes while reviewing changes in Publications
The list of working in progress for Publishing features can be found at Publications update 2023/06/13. We have improved performance, while also making the wiki pages change tracked. It has also been implemented a mechanism to remove publications that are more than 6 months old.
Content history across Publications
This new feature allows content editors to view the only publications that included modifications to a particular asset.
Publication templates
With this new feature an admin should be able to help preconfigure a publication to help facilitate their unique workflows.
Publication templates can be leveraged to provide naming patterns to any created publication. Tokens are provided to allow each publication to have unique names.
Admins can also assign roles to users immediately during publication creation.
Using knowledge base with Publications
Users can now create, edit, or delete knowledge base articles within a publication.
Deleting published publications older than 6 months
Publications can take up quite a bit of space in the database. While some users need an extensive history, others do not.
With this new feature we can provide an optional clean up to remove older publications for those who do not need the history.
Preview changes for Wiki pages
Users can preview the changes of a wiki page within a publication.
Improve performance of Publications
We have refactored Ongoing, Scheduled and History tabs to use dataset display, and added a configuration to speed up review changes screen.
Search
Features added in this Release:
Operating Liferay (on-prem) with Elasticsearch 8
Operating Liferay (on-prem!) with Elasticsearch 8 as a search engine leveraging its REST API compatibility mode through the bundled Elasticsearch 7 connector allowing Liferay deployments to upgrade the Elastic Stack to 8.x (opt-in), while also keeping compatibility with 7.x.
Elasticsearch
Search Engine Compatibility Matrix
General Upgrade Instructions:
Please refer to the documentation for more details.
- No action is required for deployments already using and insisting to stay on Elasticsearch
7. - Moving to Elasticsearch
8may require a full reindex depending on the choice of the upgrade path:- Upgrading the current Elasticsearch
7.xcluster to8.xand connect DXP (Upgrade Elasticsearch | Elasticsearch Guide [8.10] | Elastic , recommended) → No reindex required - Setting-up a new Elasticsearch
8.xcluster, connect DXP → Reindex required!
- Upgrading the current Elasticsearch
Updated Elasticsearch Sidecar version to 7.17.10
Liferay Portal 7.4 CE GA78 and Liferay DXP 7.4 Update 78 Tomcat Bundles and Docker Images come with Elasticsearch 7.17.10 for Sidecar.
Improved Support for Objects in the Search Widgets
Support for Object displays pages in the search results, aggregating (via Custom Facet widget), filtering (Custom Filter widget) and sorting (Sort widget) using Object fields that are indexed as Nested Fields in Elasticsearch, similar to Web Content Structure (DDM) fields.
Collections with Search Blueprints
Automatically register a collection provider for each search blueprint. By displaying the blueprint's results in a collection display fragment, you can leverage search to return your assets dynamically, and reap the benefits of the fragments toolbox to lay out the page.
Search Headless API
Search the company index for matching content through a single endpoint and build custom search experiences. Supports facets with translated display terms and also custom searching, filtering, aggregation and sorting through Search Blueprints (DXP ONLY)
Sidecar Elasticsearch Updated to 7.17.12
Liferay Portal 7.4 CE GA88, Liferay DXP 7.4 Update 88 bundled with the latest available version of Elasticsearch 7.x for Sidecar (7.17.12, as of Aug 7, 2023).
Feature title
Front end Infrastructure
Features added in this Release:
JS Import Maps Entry Client Extension
With this new front-end client extension users will be able to add an entry to the global import map.
This can be used to share code between decoupled client extensions that are freed from the need to know the deployment URL of the code at build time. For example, this will allow you to share your library or framework of choice among all your front-end client extensions:
For a script to consume the JavaScript module referred to by the import map entry, it needs to be of type=module.
In order to help developers to understand how to use this client extension, a sample has been provided: https://github.com/liferay/liferay-portal/tree/master/workspaces/liferay-sample-workspace/client-extensions/liferay-sample-etc-frontend-2
Theme SVG SpriteMap client extension
This new frontend client extension allows users to replace the existing theme spritemap without the need to redeploy a theme. The spritemap should include all icons needed for the scope where it is used.
The Control Panel still uses the admin spritemap.
After registering the client extension, in the page template or page you need to use it, configure it from the design options menu:
To enable this client extension, do it from the Feature Flags management UI:
Headless
Features added in this Release:
Allows to set or update data on related Objects
This feature allows developers to create or update an object and its related elements in a single request, optimizing the requests performed to the server, thus improving the overall performance of your solution.
Provided the necessary data for the related elements (ExternalReferenceCode, Id, etc), if the element already exists, it will relate the two objects, if the related element does not exist, it will create the object and it will relate them.
It is also possible to remove related elements by just updating the parent without the elements that are not related anymore.
Allows developers to filter by using data of related elements for custom Objects
Now, developers will be able to filter Custom Object Entries using the field values of the related elements for a given Object entry.
It is possible to filter as many levels as needed. The format of the filter query needs to be: relationshipName1[/relationshipName(i)]*/fieldNameN. Being relationshipName1, relationshipName(i), etc the different relationship names that join Object 1 with Object i, and fieldNameN being the name of the field of the latest Object definition on which the user wants to filter.
In addition to this, our nesting capabilities have been enhanced, so now it is possible to retrieve data for an Object entry and its related elements, supporting several levels of nesting.
The names of the different relationships to retrieve need to be specified in the nestedFields parameter, separated by commas. Additionally, the nestedFieldsDepth parameter with the number of levels to retrieve needs to be specified in order to indicate to Liferay how many levels it is necessary to nest.
Support for External Reference Code is extended to Headless entities
It has extended the support for External Reference Code to other Liferay entities in version 7.4. With this new parameter, users will be able to access, create, update and delete various entities by simply specifying the scopeKey and the external reference code.
This External Reference Code is a custom identifier, which means that at the creation time it can be set, helping to migrate entities from one environment to another while keeping this External Reference Code the same across environments. You can check the available endpoints to be accessed by External Reference Code in the API explorer.
Expose export endpoints to allow developers to use it for data migration operations
The batch engine API allows developers to export/import data, but it requires developers to provide a configuration with multiple parameters. With the new auto-generated endpoints, it is easier to perform export operations in the portal. The export endpoints are asynchronous, so it will provide a taskId in order to retrieve/download the records requested.
The endpoints follow this format:
Manage tags and categories for Object Entries through APIs
Now users can manage the tags and categories associated with the Objects entries from the REST APIs. When an Object has Categorization enabled, properties for tags and categories will be exposed in the Object entries schemas. Users can retrieve the information, set or update the tags and categories associated with the Object entries as well as use the information of these fields to filter information
Manage permissions for Objects entries through APIs
Now it is possible to manage and check the permissions of the object entries directly from the headless APIs.
For each object definition, two new endpoints are available. One to retrieve the permissions that apply to that individual Object entry and another one that allows users to set/update the permissions that apply to that entry.
All query parameters available in the API explorer
Now it is possible to use all query parameters available from the API explorer. Parameters such as fields, nestedFields or flatten are accessible and ready to use in your test queries.
Application Security
Features added in this Release:
Users can differentiate between unknown login and incorrect password based on LOGIN_DNE and LOGIN_FAILURE audit events
With this feature it is possible to differentiate the login failures in the audit messages, which one is caused by incorrect password and which one is caused by incorrect login.
Before this change, audit messages were only returned for cases when the authentication failed with FAILURE status, which happens when the user provides an incorrect password. The event type is LOGIN_FAILURE in this case.
With the new changes, it is provided audit information for cases when the authentication fails with DNE status by adding a LOGIN_DNE event type. DNE stands for user "does not exist", it always means that the login (email / screenName / userID) is incorrect.
So with the newly added LOGIN_DNE event type we cover authentication DNE scenarios when the login fails due to incorrect login (email / screenName / userID) .
Ability to remove password change options in the portal
When the users are authenticated through SSO and IdP, it is possible to remove the ability of the end users to add or edit their passwords.
As an Instance Administrator, you are able to configure if the users have the option to give their password at registration and you can remove the whole password block from editing user data, if the password is not changeable by the password policy of the user.
Instance Administrators are able to include users' first name in the notification templates
The instance administrator can create email templates including the first name.
Export audit framework data
With this new feature, Instance Administrator can export audit data filtered by user as well as filtered by site. They can also store site data for audit events.
Staging
Features added in this Release:
Warn Site and Site template Administrators about Friendly URL collisions
We display some additional messages to Site and Site template Administrators when there is a Friendly URL collision between Site page and Site template page.
Display summary of failed staging process
From now on, users can view the summary of failed staging processes, which can help them to solve the issue(s) which caused the staging process to fail.
Optimize storing LAR files in the Document and Media Library
Using LAR files for export/import in the portal are stored in DM. These LAR files can increase the size of the DM significantly. We have changed this, so the LARs are not kept in the DM after the export/import process.
Improve the customization options of export/import validation
On LPS-136108: URLs using a virtual host are always reformatted on export and import, even in cases where they don't need to be the validation of the Web Content was added for Liferay layout URLs. Before this, there was no validation, so users could create their customizations where they could add different URLs to the Web Content's content. After the validation was added, some custom URLs became unable to be added to the Web Content. From user perspective this was a feature loss, so we decided to deliver a feature to make customers able to add their custom URLs to Web Content's content field. This feature is about adding a configuration for storing the user’s relative URL patterns. So custom URLs containing this pattern would bypass validation.
Improve export/import progress feedback to the End User and avoid unwanted data loss
Before the Import process starts, users are now asked via a confirmation dialog if the user is sure about deleting application data . Also, we have improved the error message for Staging related references.
Propagation process can run in the background
As a Site Template Administrator: template propagations are run completely in the background and background tasks are executed in a sequence. The LAR from the Site Template export is cached, so different Sites can reuse it.
LayoutSetPrototypeMergeBackgroundTaskExecutoralways uses the latest Template version for the propagation.If there is already a queued background task for the Site, we don’t create a new one.
If there is a background task in progress, we only create a new background task if the Template was modified.
Improve Staging customization options
Two new configuration options were added:
The first one gives the users the chance to automate an existing feature, which improves performance.
The other one is about displaying the Advanced Staging configuration screen to the users, improving usability.
Make Staging able to handle LXC Client extensions
This is the Staging related implementation of a bigger change. On the Staging side, the LXC Client extensions (Remote apps) could be handled. To make this feature completely working, LPS-182183: Export/Import of FrontEnd Client Extensions is also needed.
Core Upgrading
Features added in this Release:
Improvements on the Upgrade logging
Deletion of property
upgrade.log.context.name. Now all upgrade related log lines are automatically tagged with the keyupgrade.component, which provides more meaningful information.Upgrade Report is now compatible also with upgrade on startup, and it can be printed as Log Thread Context information.
Upgrades log the result and the type of upgrade that has taken place after all the upgrade processes finish.
New mBean available with upgrade on startup to obtain real time information about the status and the result of the upgrade.
DL size timeout
Creation of a new property called upgrade.report.dl.storage.size.timeout that specifies the number of seconds that the upgrade report generation will wait for calculating the DL size before timing out. This property is set to 10 by default but it can be modified in the portal-ext.properties file.
Dev Tools
Features added in this Release:
Use task to shift between Live Development mode and Production Mode
Adds support for creating custom client extension development profiles in the same project.
For example, when the user creates a file called client-extension.dev.yaml , a new task will be available to the user called deployDev.
Exclude modules from the workspace build
In order to allow developers to exclude directories from the build, a new property has been added: liferay.workspace.dir.excludes.globs=
Feature Status Changes
Feature
Feature Status
Description
Kaleo Forms Module
Kaleo Forms was already in maintenance mode (please click here for more info). It is now being moved to deprecated, so it can be removed at the same time as DDL in about a year. This solution is being replaced by Objects, Workflow, and Form Container Fragments.
Portlets in the Contacts module have been pushed to maintenance mode
The portlets that are in the Contacts module will be deprecated. These are:
In the first step, the modules were pushed to the maintenance mode. |
Staging relationship modules
These modules are obsolete ones and are no longer being used. They have been moved to deprecate and later it will be removed.
Breaking Changes
This section contains information about breaking changes in out-of-the-box DXP features and capabilities. For breaking changes on internal code, please check the link below.
For more information on internal code breaking changes, visit this link.
Cacheable option in fragments is now under the Fragment card’s options menu (it was inside the fragments editor before)
This change was made in order to prevent fragment changes propagation when a user changes the cacheable option and then saves it. This was creating performance issues for some customers.
This change will benefit customers in terms of performance, as unnecessary propagations will no longer occur when the cacheable option is changed.
No changes are expected for customers' implementations. Just the awareness that this option is now somewhere else.
More Info
Analytics Cloud
Click here to view the Liferay Analytics Cloud Announcements and Changelog.
Cloud
Click here to view the Liferay Cloud Announcements and Changelog.
Known Issues
Click here to view the full list of DXP 2023.Q3 known issues.
*Notes
Beta Features are features, functionality or capabilities made available by Liferay within Liferay DXP software that are tagged with a “Beta” flag. These features are not supported, but we welcome validation and feedback. Please refer to this article for more information.
Release flags: officially released and supported features - can be activated with Release Feature Flag. Please refer to this article for more information.
© 2023 Liferay Inc. All Rights Reserved