We have been testing Integrated Office Viewer for several months, but we just encountered a big issue with our largest business unit. They have several files stored as XLS format instead of the more modern XLSX format, and this is causing issues since the XLS file is read-only. Before WOPI was enabled in our lower environments, the users could open the Excel document in Unity and edit directly within the client before using SEND TO to save to a pickup folder for preprocessing job to split the Excel file. After WOPI, user is forced to view XLS file in read-only mode. This would require the users to save the file externally, modify it, and resave to a pickup location with a specific naming convention OnBase already does with the SEND TO. This would cause extra clicks for the user group, and that would not be acceptable in trying to streamline things.
. We were considering writing a Unity Script that can be called via Web Service which takes the XLS file and creates a rendition of the current document already stored in OnBase.
- Would create a revision be the proper approach here?
- From an implementation standpoint, would we have to stream the current document to something like a temporary UNC file share and then stream back via PageData into OnBase as rendition? Or can we leverage the Unity Script to stream from current pagedata directly back into OnBase?
This is the first time I encountered a use case like this, so trying to find the easiest yet most durable/efficient approach here.
