When is an IPaaS form submission template populated

Please see the following.  I have a form submission template that works as expected, but the ticket ID that is generated by the flow behind, which does get populated on the form after execution, is not populated in the form submission template.

https://app.screencast.com/30ubSTk0KjbLd

When does the template get populated?  It appears it is populated on form submission and not the end of the flow execution.  If this is true, how do you populate the value of the field (the ticket ID in this case) in the form submission template?  Or is there another way to provide this information to the person submitting the form from an external IPaaS link?

Thanks, Tevis

Asked by Tevis Boulware on Thu 7/6/23 8:57 PM
Sign In to leave feedback or contribute an answer

Answer (1)

This answer has been marked as the accepted answer
Michael Ligouri Fri 7/7/23 3:09 PM Last edited Fri 7/7/23 3:09 PM

Hi Tevis,

In the Fill Template step of your flow, the fields "txtTicketID" and "txtRequesterDuckID" don't have values.  Have you tried putting values in those fields to see if they show in the template?

Cheers,

Mike

 

 

No feedback
Hi Mike, that is the issue. The TicketID is set in the txtTicketID field as a result of the flow execution (the requester duck id may be left blank).

That is, the flow generates a ticket, then sets the TicketID in the txtTicketID field as expected. However, the TicketID that is set in the txtTicketID field is not pulled into the flow result template. This tells me that the flow result template is created and populated before the flow is completed.

My question is this the expected behavior? - Tevis Boulware Sat 7/8/23 12:56 PM
Hi Tevis, so I guess what I was suggesting was in the final step of the flow, populate the txtTicketID field with the ID from the response of the Create New Ticket action. Right now it's populating that value in the just the ticketID field of the template. I went ahead and did this in the flow step for you to see...can you run a test? - Michael Ligouri Mon 7/10/23 12:54 PM
Mike, this did not work, and the side effect was the flow was called twice and two tickets were created. The workaround was to change the submit button to an action button, and then return the ticket information and populate a field with the data. - Tevis Boulware Tue 7/18/23 12:24 PM