![]() Office for the web navigates to the HostEditUrl that's returned in the PutRelativeFile response, which the host controls. The X-WOPI-FileConversion header tells hosts when the operation is being called from the conversion flow, so the host can choose how best to handle those requests.įinally, the host can control where the user is navigated after conversion is complete. Second, the host can choose to handle converted documents in a unique way, by handling the PutRelativeFile operation differently when called from the conversion flow. This can also apply to the in-application Edit button by setting the EditModePostMessage property to true and handling the UI_Edit PostMessage. Because hosts ultimately control when the convert action is invoked, a host could choose to display a notification message when a user attempts to edit a binary document, informing them that the document will be converted. There are three basic customization options that hosts can employ to help manage this.įirst, the host can choose to display some UI to the user prior to beginning the conversion process. Thus, it's important to consider how to manage user confusion around converted documents. This can be confusing for users depending on how the host UI user experience is designed. If the user attempts to edit the file again, Office for the web again converts it and creates a second converted file, for example File1.docx.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |