Appian for Mobile Devices


The Appian for Mobile Devices application allows Appian users to view and interact with the Tempo Interface using a mobile device. The supported mobile device types include iPhone, iPad, and Android.

See also: Mobile System Requirements

This mobile application enables Appian users to monitor general or targeted events, collaborate on goals, take direct action on tasks, and stay abreast of key activities. You gain mobile access to task and event notifications, mobile-enabled forms, one-click mobile approvals, up-to-date business information, and ad-hoc collaboration. The Tempo interface also allows you to discuss your core business activities, systems, and events.

Appian for Enterprise Mobility Management (EMM)

Appian mobile can now be configured through any of the participating EMM vendors that comply with AppConfig standards and guidelines.

AppConfig is a standard approach to mobile application configuration and management introduced by a group of leading Enterprise Mobility Management (EMM) providers and application developers who have come together to make it easier to drive mobile adoption in business. Deployments of mobile enterprise applications are streamlined in AppConfig by leveraging the extensive security, and configuration frameworks provided natively by the mobile operating systems.

See also: Appian for Enterprise Mobility Management (EMM)

Account Setup

If your company set up an Appian for Mobile application, all you need to do to begin working is download the app and create your account.

See also: Creating and Managing Mobile Accounts

Custom Mobile Applications

Administrators and developers can customize different aspects of Appian for Mobile Devices to create a different look and feel that mirrors your organization's style in end-user interfaces.

See also: Custom Mobile Applications

Network Communication Requirements

Appian for Mobile Devices application must have access to the Appian server. Servers running on internal networks or behind application firewalls will require mobile VPN clients or other third-party network access solutions.

Client Authentication Requirements

Appian for Mobile Devices supports Appian, LDAP, and SAML authentication mechanisms. When creating an account the mobile client automatically detects the server authentication method and presents the appropriate screen to the user in an in-app browser. After users have successfully authenticated from the in-app browser, they are automatically redirected back to the mobile application.

/Mobile In App Browser Auth

On the Appian for Mobile Devices iOS application, users are prompted by the operating system to grant explicit consent, allowing the application access to the site’s data in Safari.

Users are required to go through this login workflow every time their session expires. Session expiration is controlled by Appian server’s authentication layer.

Appian for Mobile Devices application does not support SAML IdP initiated login, or client certificate authentication (CAC/PIV, smartcard).

See also: Authentication

Client Certificate Access

With Client Certificate Access, users can import a certificate into the mobile app. The certificate is used to ensure that access to the Appian server on the organization's internal network is restricted to clients that can provide a valid certificate when presented with a certificate-challenge.

The validity of the digital certificate is typically ascertained by a Network Security Service (gateway), that is responsible for keeping out unauthorized traffic from the organization's network.

The feature can be enabled in the Appian for Mobile Devices applications deployed through an Enterprise Mobility Management provider using a custom configuration. When enabled, the option to import a certificate into the mobile app is made available on the 'Accounts' screen.

/mobile client certificate access

For the Appian for Mobile Devices iOS application, the certificate can be imported from any application that acts as a Document Provider.
For the Appian Mobile Devices Android application, the certificate can only be imported from the device's trusted credential store.

The imported certificate is automatically presented by the mobile app any time it receives a certificate-challenge. After validating the certificate, the gateway forwards mobile app requests to the Appian server.

Derived Credentials

This feature can also be used to access Derived Credentials (certificates derived from user's smart card credentials) deployed by providers like Purebred, used by the Department of Defense (DoD).

Purebred is a managed registration service to deploy and configure user certificates on mobile devices. Similar to using a Common Access Card (CAC), mobile devices enrolled using the Purebred registration process can be used to perform security functions on DoD information systems such as authentication, authorization, and generation of digital signatures.

See also: Appian for Enterprise Mobility Management (EMM)

Open in Github Built: Thu, Feb 23, 2023 (02:59:22 PM)

On This Page