[ConfiForms] Form is submitted even though a Jira rest - API error is produced.

[Shakir Islam]

Hi all,

I am building a ConfirForm survey that takes in values to:

1) Send out emails with the relevant information to certain individuals. (Via the IFTTT rules)

2) Produces a jira issue with the inputs of the user. (Via the IFTTT rules)

However, when a first time user submits the form, a error is produced as they first have to authorize the connection to Jira (something along the lines of access token). This consists of them logging in and then ticking a box to authorize the connection. The issue is that even though the error is produced, the form is submitted because the relevant emails are sent out. 

This is a issue because the email recipients will believe an issue is created when in reality a Jira issue has not been produced yet. 

I was hoping there was a way to prevent the form submitting (emails being sent out) if an error such as the one described is produced. 

Also, after the user logs in and authorizes the connection, they can submit the form and everything works fine. 

[Alex Medved _ConfiForms_]

ConfiForms IFTTT Rules are not transactional. And are executed as post-functions after the actual operation on the record is completed.

I suggest you to change the order of the IFTTTs and send email only after Jira ticket creation has been successfully completed

You can change the order of the IFTTTs execution by changing the order of the macros in the form's configuration in Confluence editor