You are viewing limited content. For full access, please sign in.

Question

Question

Forms email with secure attachment

asked on July 2, 2020

Our Exchange is configured to secure an email if we put a specific phrase at the beginning of the subject line. I did this with an email notification in a Forms process but the email is not going through as secured. I don't know if this is an issue with how Forms is passing the email information to our Exchange server or something else? I have also tried sending an email from Workflow as secured and it isn't working either.

 

As  a stopgap I've tried setting up the workflow email activity attachment properties to encrypt the PDF but it only encrypts the attachment from the "Include  images as PDF" part, not the "Include electronic form" part. And the PDF's I'm using are blank if all I select is the "Include images as PDF". Is there something I need to do to prepare the "PDF" so that the encrypt option will work?

 

Neither of these solutions are working and we have to have the attachment secured in some manner. We have RIO on prem with Forms 10.4.2.381.

0 0

Replies

replied on July 2, 2020

The option to encrypt PDFs in Workflow only applies to PDFs generated from a document's image pages. Existing PDFs will not be modified.

0 0
replied on July 6, 2020

If the document is a TIFF will the "include electronic form" work?

0 0
replied on July 6, 2020

"Include electronic document" always applies to the electronic component (ie, not the image pages). The electronic document is sent in its current format and not converted to PDF.

0 0
replied on July 6, 2020

So how would I setup the workflow (or the original form to save to repo) so that I can encrypt the pdf?

0 0
replied on July 22, 2020

Update: I could not get the secure email or the encrypted PDF to work in the time I needed it to. I will continue to work on that as I have free time and will post on here if I do get it working. In the meantime, I updated the processes to do the following:

1. Save the document to the repository

2. Send an email to the user with a "code" (really, just the instance id)

3. On the final form, the user enters the "code" if the previous one was filled out electronically instead of manually.

4. When the final form is submitted a workflow is called to move the file from the "temp" folder in the repository to its "processing" folder.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.