Overview
End-users will have the ability to edit office documents from an Appian interface and store a new version of the document in Appian after saving the document.
Key Features & Functionality
You can use the Web Application Open Platform Interface (WOPI) protocol to integrate Office for the web with your application. The WOPI protocol enables Office for the web to access and change files that are stored in your Appian instance.
To integrate your Appian application with Office for the web, you need to have the following:
The sample application included in the download package showcases how this plug-in can be used. The function getembeddedofficeurl() can be used to generate a url which can be used in the Web Content Field.
The sample application also includes the following API's which are needed to embed office into an Appian application:
Hello,
I'm interested by your plugin. We have an Office online installed on prim. Actually the sample cannot work. Word Online start but the document cannot be opened. Have you an idea of what is wrong ?
URL is something like this:
https://office.xxxx.xx/wv/wordviewerframe.aspx?title=OOI_WOPICLIENT&WOPISrc=https://appian-int-td01.tst:8443/suite/webapi/wopi/files/5224&access_token=....
Regards
Did you added the API service account access to the folder where the documents are stored?
You can find more information on the error in the ULS logs of OOS2019 which are located here if you used the default install location: C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS
There is a nice utility called ulsviewer which you can use to monitor the logging of OOS2019 and where you can filter on the sessionId which the browser is showing. It could be that on the OOS side you need to allow incoming and outgoing traffic.
No errors with the appian API, the response is:{"BaseFileName":"DOCX_EXAMPLE.docx","OwnerId":"momen.salameh","Size":0,"Version":"1","UserCanWrite":true,"IsAnonymousUser":true,"LicenseCheckForEditIsEnabled":true,"UserId":"Anonymous","UserFriendlyName":"Anonymous","LastModifiedTime":"2021-11-03T11:06:57Z"}
I'm using Office Online Server 2019 on-premises.
What is the error you get when you call the Appian API(https://<appianinstance>.appiancloud.com/suite/webapi/wopi/files/<docIDd>/contents) from postman or something similar? And which Office are you using?
Hello Mr. Mark Ansink,
I'm facing the same issue above, also when I call the API using the my API key I receive the response,
Can you please help me with this issue!
Thanks in advanced.
The the access token is how Office is able to access Appian to get the document. Office is doing a callback to Appian. So you need to have either the Appian API key in your Appian credentials store. You can also mail me directly on mark.ansink@appian.com so I can help you get this up and running.
yes. When I call https://appian-int-td01.tst:8443/suite/webapi/wopi/files/5224&access_token=.... I well receive the response. But I do not understand the role od access_token