RELATED IDEAS
Set Signatures as Image Variable for Workflows
When a user completes the form and signs the document allow this signature to be used as an image variable within the workflow. Removing the need to store/generate an image file and then call that file into a workflow. This is important for data privacy and can be used for other similar situations (Licences etc) where companies do not want there employees sensitive data being stored other than in their personal secure files.
Hi Andrew,
Thanks for reaching out.
The Signature control's output is a "File" variable, which can be used in any action that supports file variables. This file does not need to be stored in order for it to be used in subsequent actions.
e.g.
My Start form only has a Signature control. I have no actions between the Start event and this Email action where I am referencing the file variable - I am not uploading the image to any EFSS storage like OneDrive or GoogleDrive.
This Send an email action will send the signature image as an attachment.
If the concern is around these image files being stored by NAC, there is this option in the Settings in the designer, which will delete the instance data and any associated files used in the instance:
Or this tenant level setting, which only impacts files uploaded during instance execution.
Hope this helps! Do reach out again if you have any other questions.
Regards,
Kate Huynh