Create smooth multistep forms directly in the page builder with Liferay’s new fragment—making complex processes simple and intuitive!
Liferay DXP makes it easy to create dynamic, multi-step forms. Simply add a stepper fragment to any existing form to transform it into a multi-step journey. You can then organize your form into different steps, moving inputs between them as needed. Users can easily navigate through the steps using the step menu or form buttons, which you can customize to fit your needs.
Release Notes
Boost Liferay’s platform with drag-and-drop, multi-selection, and cut/copy/paste features for easier field and fragment organization.
Enable JavaScript Client Extensions within SaaS environments to enhance customization and flexibility for administrative tasks, allowing tailored solutions directly within the platform.
This feature ensures that theme CSS client extensions "just work" out of the box when referencing images from the base theme. It reduces friction in the development process, increases reliability, and provides a more seamless and predictable experience when customizing their Liferay environments.
How it works:
Simplified Image Management:
Developers no longer need to manually handle or configure paths for images included in the base theme.
Relative paths (e.g.,
../images
) can now directly reference these images, reducing complexity and errors.
Out-of-the-Box Compatibility:
The feature ensures that theme images are automatically included during the build process via the
assemble
step.This means that after deploying the theme CSS client extension, image references work seamlessly without additional configuration.
Semantic Search now supports the Documents and Media type. Text embedding generation can be enabled via the provider configuration. Please note that the provider configuration is now located under the Global Menu: |
The upcoming Marketplace release of the Liferay Connector to OpenSearch 2.x will provide an alternative to Elasticsearch for Self-Hosted Liferay deployments.
IMPORTANT: Please note that the Liferay Enterprise Search Learning to Rank, Cross-Cluster Replication, and Monitoring applications are not compatible, and thus not supported with OpenSearch.
Synonym Sets now also supports the following languages (locales) out of the box:
Portuguese (Brazil):
pt_BR
Portuguese (Portugal):
pt_PT
Italian:
it_IT
Arabic (Saudi Arabia):
ar_SA
Catalan (Spain):
ca_ES
Catalan (Andorra):
ca_AD
Catalan (Spain, Valencian):
ca_ES_VALENCIA
Chinese (China):
zh_CN
Chinese (Taiwan):
zh_TW
Dutch (Netherlands):
nl_NL
Dutch (Belgium):
nl_BE
Finnish (Finland):
fi_FI
French (France):
fr_FR
French (Canadian):
fr_CA
German (Germany):
de_DE
Hungarian (Hungary):
hu_HU
Japanese (Japan):
ja_JP
Swedish (Sweden):
sv_SE
Administrators are advised to review the Elasticsearch connector configuration and remove any customized field mappings and settings added previously for the above locales from the Override Type Mappings and the Additional Index Settings as now they are provided by the platform out-of-the-box. (Requires a Full or Concurrent Reindex!)
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.