- Xcode 9.0
- iOS 11 SDK
- Liferay Portal 6.2 (CE or EE), Liferay 7.0 CE, Liferay DXP
- Liferay Screens Compatibility plugin (for Liferay Portal CE or Liferay Portal EE).
- iOS 9 and above
- Visual Studio 7.2
- Mono .NET framework 18.104.22.168
The DDL List Screenlet enables the following features:
- Shows a scrollable collection of DDL records.
- Implements fluent pagination with configurable page size.
- Allows filtering of records 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 Theme uses a standard
UITableViewto show the scrollable list. Other Themes may use a different component, such as
UICollectionViewor others, to show the items.
Dynamic Data Lists (DDL) and Data Types should be configured in the portal. For more details, please refer to the Liferay User Guide sections Defining Data Types and Creating Data Lists.
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. Here are the offline mode policies that you can use with this Screenlet:
|Policy||What happens||When to use|
|The Screenlet loads the list from the portal. If a connection issue occurs, the Screenlet uses the delegate 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 delegate 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 delegate 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 ID of the DDL being called. To find the IDs for your DDLs, click Admin → Content from the Dockbar. Then click Dynamic Data Lists. Each DDL’s ID is in the table’s ID column.|
|The ID of the user to filter records on. Records aren’t filtered if the |
|The comma-separated names of the DDL fields to show. Refer to the list’s data definition to find the field names. To do so, click Admin → Content from the Dockbar. Then click Dynamic Data Lists and click the Manage Data Definitions button. You can view the fields by clicking on any of the data definitions in the table that appears. Note that the appearance of these values depends on the Theme selected by the user.|
|The offline mode setting. The default value is |
|Whether the list loads automatically when the Screenlet appears in the app’s UI. The default value is |
|Whether a standard iOS |
|The number of items retrieved from the server for display on the first page. The default value is |
|The number of items retrieved from the server for display on the second and subsequent pages. The default value is |
|The name of the |
|Starts the request to load the list of records. The list is shown when the response is received. This method returns |
The DDL List Screenlet delegates some events in an object that conforms to the
DDLListScreenletDelegate protocol. This protocol lets you implement the
- screenlet:onDDLListResponseRecords:: Called when a page of contents is received. Note that this method may be called more than once; once for each retrieved page.
- screenlet:onDDLListError:: Called when an error occurs in the process. The
NSErrorobject describes the error.
- screenlet:onDDLSelectedRecord:: Called when an item in the list is selected.