- Android SDK 4.1 (API Level 16) or above
- Liferay Portal 6.2 CE/EE, Liferay CE Portal 7.0/7.1, Liferay DXP 7.0+
- Liferay Screens Compatibility app (CE or EE/DXP). This app is preinstalled in Liferay CE Portal 7.0/7.1 and Liferay DXP 7.0+.
- Android SDK 4.1 (API Level 16) or above
- Visual Studio 7.2
- Mono .NET framework 184.108.40.206
The DDL List Screenlet has the following features:
- Shows a scrollable collection of Dynamic Data List (DDL) records.
- Implements fluent pagination with configurable page size.
- Allows record filtering by creator.
- Supports i18n in record values.
JSON Services Used
Screenlets in Liferay Screens call JSON web services in the portal. This Screenlet calls the following services and methods.
The Default View uses a standard
RecyclerView to show the scrollable list.
Other Views may use a different component, such as
ViewPager or others, to
show the items.
DDLs and Data Types should be configured in the portal before using DDL List Screenlet. For more details, see the Liferay User Guide sections Creating Data Definitions and Creating Data Lists .
Also, to allow remote calls without the
userId, the Liferay Screens
Compatibility app must be installed in your Liferay instance. You can find this
This Screenlet supports offline mode so it can function without a network connection. For more information on how offline mode works, see the tutorial on its architecture.
|Policy||What happens||When to use|
|The Screenlet loads the list from the portal. If a connection issue occurs, the Screenlet uses the listener to notify the developer about the error. If the Screenlet successfully loads the list, it stores the data in the local cache for later use.||Use this policy when you always need to show updated data, and show nothing when there’s no connection.|
|The Screenlet loads the list from the local cache. If the list isn’t there, the Screenlet uses the listener to notify the developer about the error.||Use this policy when you always need to show local data, without retrieving remote information under any circumstance.|
|The Screenlet loads the list from the portal. If this succeeds, the Screenlet shows the list to the user and stores it in the local cache for later use. If a connection issue occurs, the Screenlet retrieves the list from the local cache. If the list doesn’t exist there, the Screenlet uses the listener to notify the developer about the error.||Use this policy to show the most recent version of the data when connected, but show an outdated version when there’s no connection.|
|The Screenlet loads the list from the local cache. If the list isn’t there, the Screenlet requests it from the portal and notifies the developer about any errors that occur (including connectivity errors).||Use this policy to save bandwidth and loading time in case you have local (but probably outdated) data.|
|The layout to use to show the View.|
|Defines whether the list should be loaded when it’s presented on the screen. The default value is |
|The ID of the DDL being called. To find your DDLs’ IDs, click Admin → Content from the Dockbar. Then click Dynamic Data Lists on the left. Each DDL’s ID is in the ID column of the table.|
|The ID of the user to filter records on. Records aren’t filtered if the |
|The offline mode setting. See the Offline section for details.|
|The number of items to retrieve from the server for display on the first page. The default value is |
|The number of items to retrieve from the server for display on the second and subsequent pages. The default value is |
|The comma-separated names of the DDL fields to show. Refer to the list’s data definition to find the field names. For more information on this, see Creating Data Definitions. Note that the appearance of these values in your app depends on the |
|The name of the |
|Starts the request to load the specified page of records. The page is shown when the response is received.|
DDL List Screenlet delegates some events to an object or a class that implements
This interface lets you implement the following methods:
onListPageFailed(int startRow, Exception e): Called when the server call to retrieve a page of items fails. This method’s arguments include the
Exceptiongenerated when the server call fails.
onListPageReceived(int startRow, int endRow, List<Record> records, int rowCount): Called when the server call to retrieve a page of items succeeds. Note that this method may be called more than once; once for each page received. Because
endRowchange for each page, a
0corresponds to the first item on the first page.
onListItemSelected(Record records, View view): Called when an item is selected in the list. This method’s arguments include the selected list item (
error(Exception e, String userAction): Called when an error occurs in the process. The
userActionargument distinguishes the specific action in which the error occurred.