Overview
Enables automated server-to-server file management between Appian and Box, individual user-delegated actions, native Box Sign e-signature cycles, and structured document classification through metadata templates.
Please see the Box Connected System Set Up document for more details and instructions.
[Deprecated] Provides Smart Services and custom functions to integrate Appian with Box document management. Please see the Box File Utilities guide included with the download for complete setup and usage instructions.
Connected Systems: BoxConnectedSystem (Client Credentials Grant), OAuthBoxConnectedSystem, JWTBoxConnectedSystemTemplate & DeveloperTokenBoxConnectedSystem
Key Features & Functionality
[Deprecated] Functions
[Deprecated] Smart Services
Box File Utilities
com.appiancs.plugins.boxFileUtilities.upload.BoxFileUpload
Box (boxFileUtilities) references private and deprecated Appian APIs[private] com.appiancorp.services.WebServiceContextFactory.getServiceContext(javax.servlet.http.HttpServletRequest)[deprecated] com.appiancorp.suiteapi.common.ServiceLocator.getContentService(com.appiancorp.services.ServiceContext)
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.
Is there a reason that enterprise level security is required? Would it still work with application-only level security?