Overview
Apryse WebViewer for Appian is renowned document technology that powers mission-critical applications for private companies, large enterprises, and governments alike.
Deep dive blog on configuration options https://apryse.com/blog/appian/view-and-edit-pdf-and-word-documents-with-appian
Key Features & Functionality
Appian Documentation, FAQ, Guides: https://docs.apryse.com/documentation/appian/
Can we please update this to include compare feature (enableSemanticCompareMode)
Hi Mike,
Thanks for your comment and for using our PDFTron WebViewer Component.
From your screenshot below it looks like you are still using version 1.0 and not the latest 1.0.4
I wanted to provide you with additional information so I reached out to the Appian AppMarket Team, please see below:
AppMarket Warning
Upgrading to latest version
Note: the links from my comment will take you to the appropriate section of the release notes in Chrome. You can also search for 'Keep your plugins up to date' on the 22.2 release notes or search for ' Update plug-ins' on the 22.3 release notes.
Feel free to reach out twinter@pdftron.com if you have any other questions.
Thomas Winter
Product Manager, PDFTron Systems Inc
Hello Mike, thanks for the heads up. I will double-check with the AppMarket team. We actually just submitted a new update that will be for Appian version 22.3 and it brings a number of features and improvements. If you have any questions, I would be more than happy to schedule a call: asafonov@pdftron.com.
For reference:
I notice the current version of this plug-in is showing up in my environment with a warning symbol indicating it's "removed from the app market". Does 1.0.4 require the original version (the one from just a couple months ago) to be uninstalled first?
Thanks Mike, I got it now. We are working on a new version of component and I will try to incorporate this change.
The "regular save" button *only* saves over the existing document (as a new version). My point is, there needs to be a way to configure this in the back-end to create a new, separate document in an arbitrary folder.
Imagine a use case where we present a generic template to a basic user, ask them to populate a few things (for example just a name and signature, etc), then save. We are *NOT* talking about "computer experts" here - but rather, about as far to the other end of the spectrum as you can get. The "save as" button (while a nice option in other cases, of course) is not acceptable here, particularly because we won't want to count on the basic user to have to provide a correct / meaningful name (nor would i even assume they'll even do it successfully at all, in some cases). Instead I'd hide the "save as" button and just make them click "save" - but I don't want to save over my generic template, either.
Mike, there should be two buttons one for save and one for save as where it captures the name. Does the regular save does not work for you?