4.2 Release Notes¶
Mobile Development Kit Client 4.2¶
Notable new or changed features for the Mobile Development Kit Client 4.2
New UI Controls¶
Bottom Navigation & Tabs¶
In 4.2, we have introduced tabs controls namely 'Bottom Navigation' and 'Tabs'.
- Bottom Navigation
It renders a list of tab items along with content for each tab. It is mainly used for top level navigation, treated as navigation menu, where the separate tabs don't have shared context.
It renders a list of tab items along with content for each tab. It is mainly used for organizing or allowing navigation between group of content that are related and at the same level of hierarchy. Each tab page should contain content that is distinct from other tab pages in a set. Tabs is used to create sort of pager to browse between items that have the same context.
For more information, see Bottom Navigation and Tabs Page.
In 4.2, we have introduced a set of analytics controls that can be used in different context.
Analytic Card Collection
Analytic Card Collection is a container that manages and displays a set of Chart Cards. Chart Cards display a thumbnail view of a chart, with key information shown.
Chart Content is a container that provides a visual representation of one or more data sets in a Section Page. It should be used when displaying chart in a non-full-screen context.
KPI Header is a container that manages and displays the different Key Performance Indicators (KPI)
For more information, see Analytics Control.
List Picker in Filter Page¶
List Picker control can now be used in Filter Page. Now, the List Picker control comes with
FilterProperty that can be set as the target property to be filtered on. For more information, see List Picker API Reference .
Object Collection Search¶
Object Collection now supports search functionality. It functions the same way as Object Table search functionality. For more information, see Object Collection API Reference .
Detail Image Text for Object Cell¶
A new property
DetailImageText allows you to put a placeholder text that gets rendered in place of the Detail Image.
This can be useful for displaying initials of a person name if they do not have a profile image.
Support In-App Onboarding QR Code Scanning¶
App user can now use the built-in scan functionality at the initial onboarding to scan the onboarding URL in QR code format.
The scan button becomes available only if
EnableOverride is set to true in the client's
BrandedSettings.json at the welcome screen. In iOS, user can see Scan button. In Android, user can see the Scan QR button after pressing the
Getting Started button.
Note: Once user has scanned and onboarded using the onboarding URL, it will be remembered and next time user logged out and onboard again, they will reuse the same onboarding URLs settings without the need to scan. User need to use device Camera in iOS or 3rd party QR scanner app in Android, if they would like to scan a different onboarding URL.
All Action & UI Controls Properties Now Support Binding¶
All properties in Actions & UI Controls now supports property bindings:
- Object Binding e.g.
- Target Path e.g.
- Dynamic Target Path e.g.
Support HTTPS URL Images for Action Bar and Tool Bar¶
In continuation of loading image over HTTPS URL support, items of
Icon', andTool Bar` now support image over HTTPS URL.
Server Side Paging Support¶
List controls such as Object Table, Object Collection, and Grid Table now support server side pagination. App can set the
ServerSidePaging property in
Target binding to specify that the server support server side pagination.
OData Service Path Suffix¶
OData Service now support
PathSuffix to append to destination path. It allows app to append relative path to destination.
In Offline OData Service, if
PathSuffix if set, you must also set the Offline Store Name.
OData Service Offline Store Name¶
App can now define Offline store's name via
StoreParams in the OData Service definition.
Customizing Transition in Navigation¶
Navigation action now has
Transition property that allows app to set
Name (transition's name).
Support Creating Extension as
In order to allow better control of the extension sizing, it is now possible to implement extension for iOS platform as
UITableViewCell. For more information, see
UITableView Based Extension for iOS.