Making an Application Mobile Ready

Making an application mobile-ready enables you to use the application on the Archer IRM mobile app. Advanced Workflow must be enabled in the application you want to make mobile-ready.

The Archer IRM mobile app is available from the Apple Appstore.

Important: Before you can make an application mobile-ready, your Archer instance must be enabled for mobile use. For more information, see "Configuring an Instance for the Archer IRM Mobile App" in the Archer Control Panel Help.

On this page

Supported and unsupported fields

The following field types are supported for updating or read-only use on a mobile device and for placement on the mobile layout.

Editable Fields

Read-Only Fields

Attachments

Cross-Reference/Related Record

Date

Numeric

Record Permissions

Text

User/Groups List

Values List

First Published Date

Last Updated Date

Record Status

Tracking ID
The following fields and field types are unsupported on the mobile device or for placement on the mobile layout. Custom Objects and Placeholders layout elements are ignored on the mobile device.

Unsupported System Fields

Unsupported Field Types

Access History

History Log

CAST (ScoreCard)

CAST (Detail)

External Links

Image

IP Address

Matrix

Multiple Reference Display Controls

Scheduler

Sub-Form

Voting

Data driven events for mobile ready applications

Data driven events (DDEs) are supported for mobile ready applications, but with some limitations:

  • For Apply Conditional Layout actions, only the Required and Read Only options are supported.
  • If a DDE rule or action includes a field type that is unsupported on mobile, the DDE is in the mobile app until the record is saved.
  • When a record is saved in the mobile app, all of the data driven event rules are evaluated, even those that evaluate unsupported field types.

    Important: In this situation, a user may not be able save a record because of a data driven event rule on an unsupported field. To avoid this situation, do not create data driven events that evaluate unsupported fields on any mobile layout or enable mobile use for applications which have DDE rules on unsupported field types.

Task 1: Make an application mobile ready

  1. From the menu bar, click Admin menu > Application Builder > Applications.
  2. Go to the Properties tab of your application.
  3. In the Options section, select the Enable Mobile checkbox.
  4. Click Apply.

Task 2: Configure the mobile layout

After your application has been enabled for mobile use, you can create a mobile layout for your existing web layout. Only data that is defined in the mobile layout of the application are downloaded to the mobile device. If you have more than one layout, you must define a mobile layout for each of your web layouts.

  1. From your application, go to Designer tab > Layout tab.
  2. If you have more than one layout, select the layout from the list.
  3. If not already selected, click the Designer tab.
  4. In the Layout Builder panel, select .
  5. In the Mobile Layout Configuration window, in the panel of available fields and sections, do one of the following:

    6. Note: The mobile layout can only have up to 15 fields.

    The following table describes the actions.

    Action

    Task

    Add individual fields

    Select the checkbox for the individual fields to move to the mobile layout.

    Selecting fields within different sections automatically adds those sections to the layout.

    Remove individual fields

    Do one of the following:

    • In the available fields panel, clear the specified checkboxes for the fields to remove from the mobile layout.

    • In the selected fields panel, click next to the individual field to remove.

    Clear mobile layout

    Click Clear Mobile Layout to remove all fields and sections from the layout.
    The following table describes the icons that might be displayed in the field bar of a field. Required fields are denoted with an asterisk (*).

    Icon

    Name

    Description

    Mobile field

    Denotes the field is included on the mobile layout.

    Key field

    Denotes the field is a key field.

  6. Verify that you do not have any data driven events on this layout that evaluate any unsupported fields.

  7. Save your changes.

  8. If applicable, repeat steps 5 to 8 for each layout in your application.