Extending System Objects
Liferay 7.4 U86+/GA86+
With Liferay Objects, you can extend supported system services. Currently, only these services are integrated with the Objects framework:
- Account
- Commerce Order
- Commerce Product
- Commerce Product Group
- Organization
- Postal Address
- User
The Postal Address object stores account addresses. For this reason, you can only relate it to custom objects that are related to the Accounts object. See Using System Accounts with Custom Objects for more information.
When extending system objects, you can add fields, relationships, actions, and validations to them.
| Feature | System Objects | Custom Objects |
|---|---|---|
| Fields | ✔ | ✔ |
| Relationships | ✔ | ✔ |
| Layouts | ✔ | |
| Actions | ✔ | ✔ |
| Views | ✔ | |
| Validations | ✔ | ✔ |
Adding Fields
You can add fields to system objects. The additional database columns are added to a separate database table that uses the service’s original table name with _x appended to it (e.g., AccountEntry_x). System objects support all available field types. Since system objects do not support custom layouts or views, you can only access these custom fields via Headless APIs. See Adding Fields to Objects for more information.
Liferay’s Custom Fields application is for adding fields to most Liferay system applications using the Expando framework. Objects does not support the Expando-based custom fields, so you cannot use them with Objects features (e.g., relationships, actions, and validations).
Adding Relationships
You can add relationships between system and custom objects to link their entities. System objects support both one-to-many and many-to-many relationships. See Defining Object Relationships for more information.
Relationship APIs
If the system object is in a many-to-many relationship or on the parent side of a one-to-many relationship, Liferay generates REST endpoints for querying and managing the relationship. This includes a GET endpoint for returning related object entries, PUT endpoint for relating entries, and DELETE endpoint for disassociating related entries.
In this example, the User system object is in a one-to-many relationship (userRequests) with a custom object (timeOffRequest). These endpoints appear in the headless-admin-user service.
See Using Relationships REST APIs for an introductory tutorial.
Adding Actions
You can add actions to system objects, triggered on events like adding, updating, or removing entries. The table below shows actions supported by system objects:
| Action Type | Supported in System Objects? |
|---|---|
| Webhook | ✔ |
| Groovy Script | ✔ |
| Notification | ✔ |
| Add Object Entry | ✔ |
| Update Object Entry | ✔ |
See Defining Object Actions for more information.
Adding Validations
You can add Groovy and Expression Builder validations to system objects. When triggered, these validations check for valid field entries and show custom error messages for invalid entries. Currently, Objects only supports validations for a system object’s default fields and does not support validations for its custom fields. See Adding Field Validations for more information.
Additional Configuration Options
When editing a system object, you can also configure the following settings in the Details tab.
| Field | Description | Supported in System Objects? |
|---|---|---|
| Title Field | Determine the field used as the title for object entries. | ✔ |
| Panel Link | Determine where the application appears in the UI. | ✖ |
| Widget in Page Builder | Determine whether the object’s Page widget is available in sites. | ✖ |
| Categorization of Object Entries | Determine whether categorization tools are available for object entries. | ✖ |
| Comments in Page Builder | Determine whether users can add comments on object entries. | ✖ |
| Entry History in Audit Framework | Determine whether object events appear in the audit history. | ✖ |