New To TrueContext

  • 1.  Question about attachment in email body

    Posted 12-13-2024 10:07

    Hi,

    I have a question about one of the forms I created. The user will capture different pictures. When they are done, they will send the form. The pictures will be part of the PDF form as well as separate attachments in the e-mail. My question is, how can I attach the picture(s) in the body of the e-mail itself?

    I will explain the reason for my question. When the receiver replies to the e-mail, the form and pictures will no longer be visible. We need these pictures as a reference.

    Thank you in advance.

    Jeffrey 



    ------------------------------
    Jeffrey
    BU engineer
    DHL
    ------------------------------


  • 2.  RE: Question about attachment in email body

    Staff
    Posted 12-18-2024 10:09

    Hi Jeffery, 

    This is a great question. I built myself a test form to try out a few different things and I also have not been able to get the photos attached to a form to be embedded in the body of the email that gets sent upon submission. I've sent this question over to our product team, to see if they have a way that this can be done that I'm not seeing and I'll update you once I hear back from them.



    ------------------------------
    Pat Cooney
    Community Engineer
    TrueContext
    community@truecontext.com
    ------------------------------



  • 3.  RE: Question about attachment in email body

    Posted 12-19-2024 20:02
    Edited by Erika Lapenat 12-19-2024 20:06

    Hello Jeffrey, 

    This one had a few of us cooking behind the scenes to explore how we could best answer you, thanks for your patience. If picture files are too large, they won't render inside the email itself, that's expected behaviour. As you've explored, the option to have the photos come through as separate attachments is as close as we can get. When the picture file sizes are small, they do actually show up, but it sounds like the submissions you're reviewing have large size photos which can be expected not to load within the email itself. 

    You mention that when the submission comes through, the receiver will be replying to, and referencing, the photos. Is that because the person who submitted the form needs to make changes? Or is it just to have a record of the images being reviewed by the receiver? Will they need to just reference the photos, or have other ways of relaying info about them, like drawing on them, or having specific file names?

    There are a few more ways I can think of to help with your question, and there might be more to your story which could help light the way, but here's what I could come up with so far: 

    _

    (1) If the receiver gets the Email Data Destination, and they don't mind opening up the photo attachments, they could take screenshots and edit the photos, make notes, using their desktop tools (for example, on mac you get tools available when opening a JPEG file to add shapes, text, draw using a marker, etc.): 

    Once they make their edits, they can drag and drop the screenshots into an email, making sure the 'Reply To' is going to the right place. 

    _

    (2) Setting up the form with a Dispatch Destination. This is where the first form actually feeds into a second form, so that instead of using email, the person can review the submission within the mobile app or on their desktop using the app, and then make notes, edits to the earlier entries, edit photos, draw on photos, etc. We cover Dispatch Destinations in the TrueContext University and in our Docs portal

    _

    (3) Setting up the form with the Teamwork feature, where the user sends their submission to be picked up by a second user, and that second user can edit, make comments, draw on photos, etc. The TrueContext Teamwork feature is covered in the TrueContext University and in our Docs portal

    _

    (4) Exploring connections with a host like DropBox, SharePoint, OneDrive, etc. - to deliver photos which can be referenced in the reply email.  You can set up meaningful naming conventions using DREL so that the photos are named in a way that's easy to work with, to help with referencing in a reply email. 

    _

    While large photos appended into the body of the Email Data Destination aren't currently available, we're exploring putting forward a feature request, and we'll check around the team in case there are other avenues or methods worth exploring. Let us know if we're missing anything with this recap, and happy testing!



    ------------------------------
    Erika Lapenat
    Technical Content Developer
    TrueContext University
    ------------------------------



  • 4.  RE: Question about attachment in email body

    Posted 12-20-2024 08:51

    Thank you both for your quick response and clear explanation! 

    No changes need to be made. The pictures contain clear information about the products and are therefore used as a kind of identifier. However, when the receiver responds to the email/form without attaching or sending back pictures, we miss the identifier needed to recognize which items they are referring to.

    Based on this: '' If picture files are too large, they won't render inside the email itself, that's expected behaviour. '' I will go for another solution. I will ask the receiver not to reply on the mail but to forward the mail (with us as receiver). The result of doing this, is that we receive the emails and can see the pictures.

    Have a nice weekend and many thanks for your support.

    Kind regards,

    Jeffrey



    ------------------------------
    Jeffrey van de Pol
    BU engineer
    DHL
    ------------------------------



  • 5.  RE: Question about attachment in email body

    Staff
    Posted 12-20-2024 11:55

    Hi Jeffery, I just wanted to let you know that I've submitted a feature request on your behalf about getting photos embedded into HTML formatted emails. I'm sure your CSM, @Chris Fraser, will be able to keep you up to date on the status of that feature request moving forward.

    Thanks Jeffery, and I hope you have a nice weekend as well :) 



    ------------------------------
    Pat Cooney
    Community Engineer
    TrueContext
    community@truecontext.com
    ------------------------------



Reminder: Content posted to our Community is public content.  Please be careful not to post Intellectual Property that you do not have permission to share.  For more information please refer to our Terms Of Use