Supported controls when working offline

When developing a mobile app user interface that is available offline, you must use a frameless dynamic container.

Frameless dynamic containers must be in a screen layout to function. You can use only the following user interface controls when working offline:

• Dropdown (sourced from a local list or a data page, with At Screen Load load behavior mode)
• Autocomplete (sourced from a data page or a large data page)
• Text inputs
• Check boxes
• Radio buttons (sourced from a local list)
• Date/time
• Icons
• Formatted text (supported only for the following types: none, text, date-time(custom), email, phone, URL, true-false, number)
• Attach Content - see the Offline support section in Adding an Attach Content control.
• Signature Capture - see the Offline support section in Adding a Signature Capture control.
• Address Map - see the Offline support section in Using an Address Map control.

Only client-side visible whens and client-side validation are supported. Auto-populated properties are also supported. You can activate when for layout groups. You can use client-side JavaScript when working offline. ClientCache JavaScript API can also be leveraged to create and remove pages in offline mode - see its API for further details.

Note: A user that is offline can attach content and signatures to work objects that have been created offline.

Repeating dynamic layout for lists

You must use a repeating dynamic layout for lists instead of grids when using the offline capability in your application. Actions are not supported on the repeating dynamic layout except for a worklist in which the opening of an assignment is supported. You can configure master-detail interaction and view for both online-only and offline-enabled cases. Only Add or Remove action is supported on a repeating dynamic layout which can be configured by using a Run Script action. Keep in mind the following information:

• The Delete action button must be configured within the repeating dynamic layout row.
• The developer should take care of creating and deleting the row context page.
• The local action used to populate the row page should be configured with the Use data page option.
• The Add and Remove APIs are actioned even if there are errors on the row page.
• The source of the repeating dynamic layout should be a Page List.

Items not supported in offline mode

The following items are not supported when you work with user interface controls in offline mode:

• Server-side conditions
• Server-side validation
• Declaratives with one exception:
  • Custom client-side JavaScript-based declaratives can be implemented.
• Refresh section
• Localization of property references
• Cascading of controls with one exception:
  • Cascading dropdowns that use parameterized data pages sourced from report definitions.
• Parameterized data pages (no cascading between controls)
• When rules
• Non auto-generated controls

Open topic with navigation