Well some documents are converted to native after being uploaded in Forms. In the case they are .jpg documents uploaded to an upload field in Forms.

In this situation, the customer has a Forms Process which has a file upload field. Since he has a document merge rule and Forms does not see merge rules, he calls a workflow to call the rule and the resulting document must then be attached in a workflow email activity instead of a Forms email activity.

Now when workflow goes to attach the attachments, they are considered native, because the format was .jpg.

Chad, we've also run into this "expected behavior" and it seems odd that the cloud system cannot handle what Laserfiche calls its native file format.  I'm not sure how this is not considered a high priority on the development list but we've been talking to them about it for months.

Can this please be put on the development list, Laserfiche?  In our situation, the documents had to be TIFF so the customer could use a stamp (signature) and then the file would email to an external user.  This seems like a pretty basic action, but is not possible. . . in the cloud.  Any advice or a fix would be GREATLY appreciated.

I concur that not being able to attach an image or have an option to convert to pdf at the point of attaching to an email is a miss.

I added this as a use case to the following thread:  https://answers.laserfiche.com/questions/168118/Why-does-Email-Attachment-not-show-option-for-starting-entry-Laserfiche-Cloud

When downloading an image from the repository the default behaviour is to convert to pdf so it sounds feesable to do so before attaching a document to email.  Or, if the download electronic file does not find an electronic file, to have the option of generating one from image.  Or, simply being able to attach the image to email.