Appian for SharePoint 2013

Web Parts

Appian for SharePoint 2013 provides the following web parts:

  • Appian News
  • Appian Tasks
  • Appian Actions

When these web parts are placed on a page, they can be configured to read News, Tasks, and Actions from an Appian server. Each SharePoint user will be prompted to enter their Appian credentials in order to view their personal Appian content.

In order for the web parts to authenticate with Appian, Appian must be configured with standard out-of-the-box authentication or custom authentication that does not modify the HTTP Basic authentication configurations. The web parts do not yet support authenticating against an Appian system that has been configured to use pre-authenticated SSO.

See also: Authentication

In order to deploy the Appian web parts to SharePoint 2013, follow the instructions below.

Configuring the Secure Store Service

The Appian for SharePoint 2013 web parts use SharePoint's Secure Store Service to securely store each user's Appian credentials. There is a one-time setup required to enable the Secure Store Service to persist the credentials securely.

  1. Using a web browser, navigate to the central administration site in SharePoint. By default this is located at http://localhost:40000 on the SharePoint server, but your configuration may vary.
  2. Under "Application Management," click on "Manage service applications"
  3. On the "Manage service applications" page, click on "Secure Store Service" (the parent link, not the proxy)
  4. Click on "Generate New Key" in the Edit ribbon
  5. Enter and confirm a pass phrase. Store this pass phrase somewhere safe for your records.
  6. After creating a pass phrase, click on the "New" button in the Edit ribbon
  7. Fill out the form with the following values and then click Next
    • Target Application ID: AppianTargetApplicationId
    • Display Name: Appian Target Application Id
    • Contact E-mail:
    • Target Application Type: Individual
    • Target Application Page URL: None
  8. On the "Create New Secure Store Target Application" form, add the following fields and then click Next
    • name: AppianUserName; type: User Name; unmasked
    • name: AppianPassword; type: Password; masked
  9. On the following screen, appoint an administrator for this application and click Finish.

Installing the Web Part Solution File

  1. Unzip the appian-sharepoint2013-X.y.z.zip file to a directory on the SharePoint server
  2. Run the SharePoint 2013 Management Shell as Administrator and navigate to the directory that you unzipped into
  3. Add the Appian.wsp file to SharePoint using the following command: Add-SPSolution -LiteralPath <path_to_unzipped_file>\Appian.wsp
  4. Using a web browser, navigate to the central administration site in SharePoint. Navigate to the Solutions Management page at http://localhost:40000/_admin/Solutions.aspx
  5. Locate the Appian.wsp and choose to deploy it to the desired site
  6. Next, visit the site you deployed to and login as the site collection administrator
  7. As the site collection administrator, visit the site settings page and click on the "Site collection features" link
  8. Activate the "Appian Web Parts" feature
  9. Users with permissions to add web parts to pages will now have the ability to add Appian News, Appian Tasks, and Appian Actions web parts to pages

Configuring the Web Parts

  1. After placing an Appian web part on a page, set the web part to edit mode and configure the AppianURL property to point to the Appian server. E.g., https://myappian.appiancloud.com
    • When placing multiple web parts on site, all must point to the same Appian server
  2. By default, the web part will expand vertically to fill the required space for the entries. You can limit the vertical height using the standard web part height controls available in edit mode.
  3. When you save and leave edit mode, the web part will prompt you for your Appian credentials. These credentials will be stored in the Secure Store Service. Each SharePoint user that views an Appian web part will be prompted for their individual credentials if they have not previously provided them.
FEEDBACK