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 clients 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 clients support both Standard and Web Sign-In authentication. When creating an account the mobile client automatically detects the server authentication method and presents the appropriate screen(s) to the user.

See also: Authentication

Standard Authentication

Standard authentication is the default authentication method provided by Appian and is supported by all Appian for Mobile clients.

The Appian for Mobile client will prompt users for their Appian username and password during account creation. Users will not be prompted for credentials again, unless their password changes.

When using Standard authentication any third-party authentication systems must be integrated with Appian's authentication layer and cannot act as a broker in between the server and the client. For example, instead of using an SSO solution like CA Siteminder between the Appian Server and mobile devices, we recommend using LDAP integration with Appian's authentication layer.

Web Sign-In Authentication

Web Sign-In authentication allows Appian for Mobile clients to connect to Appian servers that use custom or third-party authentication, provided that the authentication layer uses a login mechanism based on HTML forms and cookies. This type of forms login is a common feature of SSO platforms, SAML identity providers, and other authentication systems.

The Appian for Mobile client will open the Sign-In screen to render the login form(s) during account creation. The Sign-In screen will also be shown any time the user's session expires. Session expiration is controlled by the server's authentication layer.

In order to enable Web Sign-In, the server's authentication layer must adhere to the following requirements:

  1. The response to an unauthenticated HTTP request must contain a 200 OK status code and a Content-Type: text/html header.
  2. After successful authentication, the response must be a client-side HTTP redirect (302 Redirect status code) to the originally requested URL.

Web Sign-In does not support SAML IdP initiated login, Integrated Windows Authentication (IAW, WIA, NTLM, Kerberos, SPNEGO), or client certificate authentication (CAC/PIV, smartcard).

See also: Authentication

Open in Github Built: Fri, Mar 11, 2022 (04:59:07 PM)

On This Page