(Optional) Choose an icon to show in your Data Set fragment.
Choose from a list of out-of-the-box icons or type in the name of an icon registered through an SVG sprite map client extension. The custom icon requires configuring the client extension.
Tip
When an item has a single action, its label appears as text inside a button component if no icon is selected. If multiple actions exist, an action menu icon () appears, revealing available actions on click.
Under the Action Behavior section, select the action type. You can find specific configurations for each action you choose. See Configuring Item and Creation Actions to learn more about each action type.
With creation actions, create new items for the data set. You can direct users to a URL where the new entry is created and choose whether to open the link directly or in a modal or side panel.
API Information: Access action keys and endpoint details through the API Explorer.
Confirmation Messages: These are only available for item actions.
Permissions: When an action is associated with a headless endpoint, the user must have the necessary permissions to use the endpoint (e.g. to edit the document). The information returned by the endpoint may vary depending on the user’s permissions.
URL Interpolation: Use interpolated parameters in URLs to send information dynamically to the API. Enclose parameterized values in curly braces {}.
For example, replace static values like (...)externalReferenceCode=9ad3e87f-0a7b-4624(...) with externalReferenceCode={externalReferenceCode} so the value is retrieved dynamically based on the item.
URL Best Practices: Use relative URLs and try to make them as universal as possible.
Avoid including the hostname/port in the action URL.
Avoid specifying site names whenever possible.
Do not use p_p_auth values in URLs, as they are session-specific and are not valid in different contexts.
Asynchronous actions operate behind the scenes, allowing complex or time-consuming operations to be carried out in the background while users continue interacting with the application.
To create an asynchronous action,
Under Action Behavior, select Async as the Type.
Specify the URL for the REST endpoint where the selected method is implemented and select the Method: Delete, Get, Patch, Post, or Put.
Liferay DXP 2024.Q4+/Portal GA129+ Enter the Request Body if it applies to your chosen method. Enter all required values for your chosen endpoint (for a Patch method, only the fields you’re changing).
The request body must be valid JSON. No input is interpreted as {}.
(Optional) Enter a Headless Action Key to link an action to a headless endpoint and verify if users have the required permissions for the chosen action method. Ensure the key matches with the selected method.
Important
If no key is defined, the action still works, but becomes visible to all users, as there are no validations or restrictions in place.
Headless actions are controlled via a Headless Action Key, which determines the specific permissions and functionalities that can be executed through the API. For example, a headless action with the key delete would allow an API to carry out a deletion operation on a specific resource.
To create a headless action,
Under Action Behavior, select Headless as the Type.
Liferay DXP 2024.Q4+/Portal GA129+ Enter the Request Body if it applies to your chosen method. Enter all required values for your chosen endpoint (for a Patch method, only the fields you’re changing).
The request body must be valid JSON. No input is interpreted as {}.
Enter a Headless Action Key to associate the action with a headless endpoint.
Link actions direct users to a specified URL. They can be used both as item actions, which facilitate operations such as deleting, modifying, or viewing details of data set items, and as creation actions to add new items to the data set.
The primary distinction is the specific purpose of the URL and whether you can set a confirmation message, which is only available for item actions.
To create a link action,
Under Action Behavior, select Link as the Type.
Specify the URL.
Note
When you set a URL in a link action, the Data Set component automatically adds redirect and backURL parameters, with the backURL parameter set to the URL of the Data Set’s page. If you can’t navigate back to the Data Set from the destination page, ensure that the destination page handles the parameters correctly.
(Optional) Enter a Headless Action Key. With the action key, administrators can connect an action to a headless endpoint (e.g. GET, POST, and DELETE).
Modal actions send users to a specified URL that is rendered in a modal. You can use modal actions as item or creation actions, but remember that only item actions include confirmation messages.
Important
When using a Modal action, make sure the destination URL works well inside a modal.
To create a modal action,
Under Action Behavior, select Modal as the Type.
Select a Variant for your modal: Full Screen, Large, or Small.
Side Panel actions send users to a specified URL that is rendered in a side panel. You can use side panel actions as item or creation actions, but remember that only item actions include confirmation messages.
Important
When using a Side Panel action, make sure the destination URL works well inside a side panel.
To create a side panel action,
Under the Action Behavior section, select Side Panel as the Type.
You can display confirmation or success/failure messages before executing an action.
Tip
Both fields are optional. If the confirmation message is empty, no message appears, and the action is performed immediately. Similarly, if the status message is left empty, a generic success or error message appears.
You can also activate or deactivate the actions you defined via the buttons in the Status column. When an action is inactive, it no longer appears for users until you reactivate it.
Deactivate data set actions instead of deleting them so you can reactivate them again later if needed.
Side Panel and Modal actions open on top of the current page, so users can interact with the content without navigating away. When you add a Title field to these actions, a bar with the title and a close button appears at the top of the component. Users can close the modal/side panel and return to the original page.
If the Side Panel or Modal action points to a URL that already includes a title, adding one in the action configuration is unnecessary. The existing title from the target URL appears along with a close button. Adding another title in the action configuration results in two overlapping bars.
If neither the action nor the URL includes a title, nothing appears.
This website uses cookies and similar tools, some of which are provided by third parties (together “tools”). These tools enable us and the third parties to access and record certain user-related and activity data and to track your interactions with this website. These tools and the informationcollected are used to operate and secure this website, enhance performance, enable certain website features and functionality, analyze and improve website performance, and personalize user experience.
If you click “Accept All”, you allow the deployment of all these tools and collection of the information by us and the third parties for all these purposes.
If you click “Decline All” your IP address and other information may still be collected but only by tools (including third party tools) that are necessary to operate, secure and enable default website features and functionalities. Review and change your preferences by clicking the “Configurations” at any time.
Visit our Privacy Policy