PDFTron WebViewer Component

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:

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?

Thanks - that appears to be the culprit behind the confusion here.  I was able to use that control to rotate a page in a document and i can confirm it persisted after hitting "save".

Also, a bit of a feature request: if using this in a production system, I'd want an easier way to provide the user a generic template, and when they hit "save", have the component save a new (separate) copy (with either the same name or a pre-determined one), without having to require the user to hit "save as" and type a hand-entered name. 

The current options don't allow us to do this, though they're frustratingly close.  It would simply require a new optional flag called "saveNewCopy", maybe a new field called "newCopyFilename" or similar, and it could utilize the existing "document folder" parameter for the save-to location (which, BTW, if not provided during a "save as", saves new documents to a "null" Folder ID, leaving them in a weird limbo in the appian filesystem - just fyi.  it would be better if it could be "forced" somehow, or hardcoded to /Default Community/Temporary KC/Temporary Documents, if a better value isn't provided).

Hi Mike, View Controls are just for user preference on viewing the document in moment, if you open the page manipulation, rotate it and save the document, it will preserve the orientation.

I can confirm the above behavior, i believe (i just installed the plug-in this afternoon after learning about it in the 22.3 webinar).  I can rotate the document using the "rotate clockwise" control under "page orientation" in the "View Controls" nav button, save (which saves an apparently new version), but upon reloading the interface, the original document loads again but in its original orientation.  Maybe this control isn't meant to indicate the document itself will be rotated?  But if so, it's not very well explained.

Thanks for your response Andrey. When we access the site from office network there's restriction of rendering things if network detects something as Mixed Content. Message that we saw from console was - Page was loaded over https but requested an insecure frame. Request has been blocked; the content must be served over HTTPs. 

When we tried the same thing outside office network, it worked.