Box

Overview

Provides Smart Services and custom functions to integrate Appian with Box document management

Key Features & Functionality

Custom Functions

  • Create JSON Web Token (JWT) - createtoken() provides the user with a JWT that can be used for up to 60 seconds as authentication with the Box “token” API
  • Construct URL Custom Function - constructboxurl() expression function facilitates the creation of a servlet download link
  • Generate Box URL - generateboxurl() calls box url and intercepts the redirect url. It requires a valid Client Credentials Grant authorization token.

Smart Services

  • File Upload - after obtaining a JWT, this smart service uses the access token and calls the file upload API passing in the contents of a provided Appian Document
  • File Download to Appian - this smart service can download a file from Box and store it in a provided Appian Knowledge Center or Folder
    Servlet
  • File Download - downloads a file directly to the browser for the user to view/save to their computer. For security reasons most of the parameters passed to the servlet are obfuscated. Use the "constuctboxurl" function to create a URL to access the servlet securely.

Please see the Box File Utilities guide included with the download for complete setup and usage instructions.

Anonymous
Parents
  • Hello, we are using this plug in to upload the files to Box. Files are uploading to Box folder with SSO login ID/internal User login. But files are not uploading to Box with external user (not an employee) logged into Appian. We are also not able to find any logs related to this plug in at  integration_trace.csv file. 

    Is there a way to identify was the request been sent to Box, we are not able to trace the issue.

Comment
  • Hello, we are using this plug in to upload the files to Box. Files are uploading to Box folder with SSO login ID/internal User login. But files are not uploading to Box with external user (not an employee) logged into Appian. We are also not able to find any logs related to this plug in at  integration_trace.csv file. 

    Is there a way to identify was the request been sent to Box, we are not able to trace the issue.

Children
No Data