Microsoft Document Editor

 This is an Advanced Plug-in available for Advanced and Premium tier customers. To enable this plug-in, submit a support case requesting access to the Microsoft Document Editor component plug-in. Learn more about the Advanced Plug-in Program and read the Microsoft Document Editor Documentation

Overview

The Microsoft Document Editor component offers a seamless experience for viewing and editing Word, Excel, and PowerPoint documents stored within an Appian Knowledge Center. This robust plug-in allows users to directly edit files stored within Appian, eliminating the need for download/re-upload workflows or separate document storage solutions. This component enables viewing, editing, concurrent multi-user editing, among other actions, on Office documents.

Key Features & Functionality

  • Online Office Document Editing: Edit Office documents directly within an Appian environment without needing to download them.
  • Comprehensive Microsoft Office Features: Access a wide array of Microsoft Office features for a versatile document editing experience.
  • Multi-User Editing: Collaborate in real-time with multiple users concurrently editing the same document.
  • Create New Office Documents: Easily create new Office documents through a function plugin, streamlining document creation.
  • Access Control: Manage permissions to ensure secure and controlled access to documents.

Requirements:

  • Microsoft Document Editor Helper Servlets and Functions must be downloaded separately and is required for full functionality of this plug-in.
  • A valid Microsoft 365 license is required for all document editing users functionality. Customers should have the ability to track which users have Microsoft licenses within Appian and should configure document editing only for those users. Use of the Microsoft Office Component plug-in to edit documents without a valid Office license is cause for removal from the program.
  • Available only for Appian Cloud. Appian Government Cloud and Self-Managed sites are not supported.
  • Firefox and Safari are not supported browsers
  • Component is not configured for mobile usage or Portals
  • Public access and Inbound over Dual Access are supported, Inbound over PrivateLink-only and Inbound over VPN-only are not supported
  • Requires Appian version 25.2+
  • If your company has network security restrictions for which domains can be accessed for inbound requests, make sure to add “api.appiancloud.com” to your network allowlist.
Anonymous
  • v1.0.3 Release Notes

    • When editing a document, a banner now appears above the document viewer indicating that changes will sync to Appian approximately every 2 minutes and the user will have to refresh the page to view the latest document.
    • If the document viewer tab is closed while the editor is open, the editor now presents a choice to either keep editing (with a warning that the Appian session will no longer be automatically extended) or close the editor.
    • If the user renames a document, the browser tab will now be updated with the latest document name (requires helper plug-in 1.0.6 or above)
  • This should be fixed in the version 1.0.2

  • v1.0.2 Release Notes
    • Improved session management during document editing: Editing documents in the Editor tab now automatically extends your Appian session, reducing unexpected logouts while working.
    • Enhanced session validation for secure editing: The system now verifies login status every minute and when switching to the Editor tab, helping prevent changes after a session has expired.
  • We are finding that our Microsoft Office documents (stored in the document record type) are only viewable to the user that uploaded the document, and system administrators. Any other user is seeing an error when attempting to preview the document through this plugin, though they are able to download the document using a!documentDownloadLink.

  • v1.0.1 Release Notes

    • Non-functional "Download Button" UI removed. Configure a!documentDownloadLink outside the component to download the file
    • Environments using custom domains are now supported
  • Hi  ,

    Unfortunately, there is not a way around this. Microsoft does not share IP addresses with partners so there is no way to configure access trusted IPs to enable communication with Microsoft's servers. 

    Best,

    Julian

  • Hi Julian,

    We are using our Trusted IP Addresses feature to restrict access to the site. This is also blocking the Microsoft endpoints trying to send requests back to the environment to do the tests. Plugin is currently incompatible with sites using the Trusted IP Addresses feature.

    Are there any workarounds to make this work?

    Thanks.

    Regards,
    Satya B Andra.

  • Hi  ,

    Please submit a support case on MyAppian requesting help addressing this. They will be able to guide you through the appropriate troubleshooting steps.

    Best,

    Julian

  • Hi Julian,

    We are facing similar issue with the plugin.

    Our site meets all the requirements mentioned in the documentation, however only 4 test are passed and rest are skipped in the results of microsoftDocumentValidationField(). 

    Appreciate if you could guide us in the right direction.

    Thank you.

    Regards,

    Satya

  • Hi Shubham, happy to help. Please reach out to techpartners@appian.com with this context and answers to the following questions:

    • Is the excel file an .xlsx document?
    • What is the result of configuring the microsoftDocumentValidationField() with a document with the extension .wopitest? 
    • Does your site meet all of the following requirements?