1
0
-1

If we use the Contact email and confirmation email in a collaboration form, it sends the email on submission at every step as well as the original submission.

Is there any way to manipulate this so it doesn't get triggered after steps?

    CommentAdd your comment...

    2 answers

    1.  
      1
      0
      -1

      Hi Larry,

      I didn't really explain that very well. It's not the task email, but the submission confirmation email that also gets sent to the Contact email (or from the submission success page) after non-collaboration submissions. (The one that uses the Email Form Receipt Message portal property.)

      I cannot find a service that relates to this, so no idea how it works.

      Someone did just suggest a workaround: use a datafield to return the email to only on the first step and make that the Contact Email. Will need to test if this works though.

      Thanks,

      Lin

      1. Larry Bunton

        Hi Lin,

        Thanks for the clarification.

        I understand that you are looking into the reason being part of the delivery...

        Cheers
        Larry


        The confirmation email is configured here on a per form basis.

        If you used the same form for the start submission (email) and for the collaboration tasks (no email) you may need to deploy the form twice to 2 different form codes..

        Start Form (1st With Confirmation)
        Tasks (2nd With None)

      CommentAdd your comment...
    2.  
      1
      0
      -1

      Hi Lin,

      In your Collaboration job: Job Task Assign - Action(s) set the following property to false.


      Task Send Emailspecify whether a notification email should be sent to task assignees [ true | false ]{ "name": "Task Send Email", "value": "true" }

      Cheers

      Larry

        CommentAdd your comment...