Before this feature when somebody wanted to activate/deactivate a User they needed to have “Delete” permission. We created two new permissions called “Activate” and “Deactivate”. Users with “Delete” permission still able to activate/deactivate users.

We also created two new Headless-API endpoint:

/headless-admin-user/v1.0/user-accounts/by-status/${status}

Status can be either "active" or "inactive," allowing you to fetch users by their status.

 /headless-admin-user/v1.0/user-accounts/by-email-address/${emailAddress}

This endpoint lets you retrieve a user by their email address, regardless of their current status.

We extended the Audit Log info on IMPERSONATION actions , ASSIGN/UNASSIGN events involving the role assignment of individual users and ASSIGN/UNASSIGN Role Assignment of Organizations/User Groups/Sites.

We have expanded our Headless Admin User API to include POST, PUT, DELETE, and PATCH endpoints for managing postal addresses associated with user accounts. This development aims to provide more comprehensive functionality and greater flexibility for our users. Additionally, we've made crucial changes to the UserAccount schema and related methods to allow users to manage user status efficiently.

It is now possible to set an expiration on the “set new password” link.

Now users can export the Frontend Client Extensions that have been registered through the UI and import them in other instances. The system will generate a JSON file with all the information needed.

In order to use supported JDK versions, we are upgrading to Gradle 7 to use newer JDK.

The integration of ChatGPT with our Web Content editor is now available OOTB.

Now the “Theme SVG Spritemap” frontend client extensions is enabled by default.

Now the “JS Import Maps Entry” frontend client extensions is enabled by default.

Dynamic Data Lists is deprecated and replaced by Objects. DDL has been deprecated as of 7.3, and the Deprecation flag was added to prevent new integrations using DDL (customers that upgrade will still see it).

DDL is planned to be removed in 2024, please migrate your data to Objects before then.

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

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:

1. [%CURRENT_USER_ID%]

2. [%CURRENT_USER_FIRST_NAME%]

3. [%CURRENT_USER_LAST_NAME%]

4. [%CURRENT_USER_EMAIL_ADDRESS%] 

5. [%OBJECT_AUTHOR_ID%]

6. [%OBJECT_AUTHOR_FIRST_NAME%]

7. [%OBJECT_AUTHOR_LAST_NAME%]

8. [%OBJECT_AUTHOR_EMAIL_ADDRESS%]

This feature allows power users to configure the intervals to retry to send the email notifications when the first instant attempt fails.

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.

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.

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.

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.

This feature empowers users to create content use cases on top of objects framework, allowing admins to enable localization for objects' entries text fields.

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.

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.