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

Question

Question

Processing Forms attachments for use in Workflow

asked on February 25, 2020

I am working on a process that takes images in as Forms attachments, and using workflow to process the images and put them into a formatted Word Document.  I am using the code here To convert my images into Base 64 and referenced this article on how to put it into the word document. 

The problem I am having is that the file upload field in Forms is creating documents that are the image, not keeping the uploaded file as an attachment.  The Download Electronic Document tool in my find entries/for each entry loop fails because the document does not have an attached electronic document. 

How do setup the file upload in forms so that I can have the attachments in the right format to be able to pull them into the workflow for processing?

 

 

0 0

Replies

replied on February 25, 2020

It looks like your file attachments are being converted to TIF images when they are saved to the repository. To troubleshoot this further, check on the repository connection profile used in the save to repository task. Log in to the repository with that user and check that user's settings. It's likely that user is set to automatically convert images to TIF on import. Change the settings for the repository connection profile user to not convert images and the files should be saved as their original file type. 

6.7.0
1 0
replied on April 13, 2022

Hello!

I'm having a similar issue, where I'd like the files uploaded via Forms to retain their Electronic Document instead of converted to TIF.  We are using the Cloud version of Laserfiche and Forms, and as such I do not believe I can control the settings for repository via a different profile login. Is there a way to control this setting when using the Cloud version? 

0 0
replied on February 25, 2020

Hi Stephen,

As another idea, you may not need to use the Download Electronic Document activity for this Workflow. Looking at the script in the post you linked, it looks like your SDK Script activity itself may be doing the work of taking the document from the repository, exporting it, and converting the exported file to Base64. If this is the case, you may be able to try disabling the Download Electronic Document activity and see if you can work from there.

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

Sign in to reply to this post.