Email Tool - 'Test' Email SMTP Settings

[TheOC]

Hello there!

Currently the email tool has the following configuration:

It is a fairly easy tool to use - however one part that I would like to be improved is testing the SMTP settings - similar to how it is done on the Alteryx Server. It would be awesome to have a button as part of this page, that would send a test email, and return true/display to the user that the email sent correctly. This would stop the need to setup dummy data and a dummy output to test a connection before rolling the email tool out into a live environment/use-case.

I imagine something along these lines for this functionality:

Clicking test (and passing):

Clicking test (and failing):

Thanks,
TheOC

[rohit782192]

It is like you are doing a Database Connection

[marcusblackhill]

That would be a nice thing to have. People often run into problems because they don't know if the workflow isn't working because of a mistake in the development or because of a problem with the SMTP configuration. This could help avoid configuration problems even before the development is done.

[ddiesel]

This would be a much appreciated feature!

[DavidP]

This is so much needed!!

[Jean-Balteryx]

And @TheOC strikes again, trying to make users life easier ! 🦸‍

[DanielG]

@TheOC - Thanks for getting this out on the Ideas board.  

I'd actually like to see the Email Tool be tweaked where it will only function as normal when on the Server.  When open in desktop it auto-defaults to test functionality.  Maybe it would have to be a seperate tool from the current email tool, but it would allow you to enter the real information in AND the test information in one time and depending where it is run from, it will flow accordingly.

I know there are instances of manually running emails from desktop, but the pain in this process when it lives on the server is rough:

1) bringing workflow/app down from server to test

2) repointing/disabling tools for testing purposes

3) making changes to workflow

4) running the testing

5) repeat as many times as needed

6) repointing/enabling tools for production purposes

7) reload to server

There are ALOT of opportunities for mistakes in there.  Like accidentally emailing yourself 500 emails because you didn't re-point the process to real recipients OR maybe worse email 500 people a test email and create pandemonium.  :)