This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Now that it's live, don't forget to accept your certification badge on Credly today! Learn more here.
We are currently experiencing an issue with Email verification at this time and working towards a solution. Should you encounter this issue, please click on the "Send Verification Button" a second time and the request should go through. If the issue still persists for you, please email email@example.com for assistance.
I am currently working on building self-serve Analytics apps for colleagues and I am using the Email tool for this. However, the credentials have to entered directly into the tool and whenever the password changes this needs to be again changed into the workflow by the workflow developer.
This means that:
A) Workflow developer needs to have access to the mailbox used in the From field B) Only the developer's email address can be used in the From field C) The developer needs to connect with mailbox user in person or over video-conference, share control of his own machine and have the user put in their credentials every time the mailbox user's password changes.
These are three major hindrances in using the email tool to its full potential.
Provide an option in the Alteryx server to have a database where users can create a record of their credentials (hashed of course) and with each record a token number is generated. The token number can be shared with the developer who will update that in the email tool. Whenever the password changes, the user can directly retrieve his old credentials and change them using the same token number. This method will eliminate the above mentioned three constraints and allow for use of email tool to create complete self-serve apps.