Supported controls when working offline

When developing a user interface for an offline-enabled application, it is recommended to use an iframe-less dynamic container in a screen layout and use data pages or a local list to source data. You can also use back-to-back assignments in a standard flow for offline mode.

You can use only the following user interface controls and components when working offline:

  • Formatted text (supported only for the following types: none, text, date-time(custom), email, phone, URL, true-false, number)
  • Dropdown (sourced from a data page or a local list, with At Screen Load load behavior mode, cascading)
  • AutoComplete (sourced from a data page or a large data page)
  • Multi-Select lists
  • Text inputs
  • Button labels
  • Check boxes
  • Radio buttons (sourced from a data page or local list)
  • Date/time
  • Icons
  • Menus
  • Attach content
  • Signature captures
  • Address maps
  • View static PDF
  • Search
  • Links
  • Paragraph rules

Only client-side visible when rules and client-side validation are supported. Autopopulated properties are also supported. You can activate when rules for layout groups. You can use client-side JavaScript when working offline. ClientCache JavaScript API can also be used to create and remove pages in offline mode. For more information, see the ClientCache API Javadoc documentation.

If your offline-enabled application is localized, button labels, link captions and radio buttons appear in the selected language.

Note: An offline user 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 supported on the repeating dynamic layout for a worklist in which the opening of an assignment is supported, as well as open by handle, and actions are also supported when adding or removing a row. When using the Add or Remove action on a repeating dynamic layout, you do not need to use a Run script action. You can configure master-detail interaction and views for both online-only and offline-enabled cases.

Keep in mind the following information:

  • The Delete action button must be configured within the repeating dynamic layout row.
  • A 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 active 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, with one exception:
    • When the user's actions are replayed on the server during synchronization.
  • Declaratives, with one exception:
    • Custom client-side JavaScript-based declaratives can be implemented.
  • Refresh section for other sections by name or property reference. Only refresh this section is supported in offline mode.
  • Localization of property references
  • Cascading of controls, with one exception:
    • Cascading drop-down lists that use parameterized data pages sourced from report definitions.
  • When rules