Can a "Response Required Email" step in a workflow be sent to a variable user?

johnrbreedon

Hi All,

I'm sestting up a workflow and need to be able to send a "Response Required Email" to a user, but the user will be defined in the workflow as a variable as it changes on data provided in the form that kicks off the process.

I've tried using the code block to do this, and tests work okay, but the actual emails don't send and also make things more complicated.

Does anyone have experience of this?

Many thanks,

John

DanHendriksen

John, an email user task cannot have a dynamic recipient at this time.

I would encourage you to use the form user task. The form can be very simple and only require a single response, but in my experience (which is vast) is a much better way to go for several reasons:

1 - You can get more than a single predefined response
2 - You can have the recipient be dynamic
3 - They can get push notifications in the Task Center App

I could go on, but in my experience everyone thinks they want the email user task until they've used it once. The user will get an email on their phone, click the button and it will launch Domo in the browser. They won't be logged in, so they'll have to go through the authentication flow, then their response is recorded and they can close the browser. Furthermore, if this is something with any frequency, they're having to go back through a crowded inbox to find the things that are waiting for them.

Task Center, both in the mobile app and Domo web app, provides a much more comprehensive and user friendly experience. If you need help with it, let me know.

Now, if you are hell bent using the email user task, there is some creativity that can accomplish it. You can dynamically add a user to a group, send the task to that group, and then after they complete it remove the user from the group. It can get messy and you could potentially have race conditions where multiple people are in the group, but it's a creative approach I saw someone use (before they realize the Form User Task just works better) that I figured might be worth mentioning.

johnrbreedon

Hi Dan,

Thanks for coming back on this. We are using a comprehensive workflow that kicks off from a form user task. The idea is access to reports. Once a form is submitted, we send an email to the submitters line manager to approve/reject the request. That's the tricky bit, we can't get all users to install the App, so we're directing them to the queue in Domo (desktop), to find an approve/reject.

This is now working okay, but the final issue is we can't assign the task to that line manager in the queue, as we can't extract the line manager as a Person variable in the Domo workflow only as an object, or are we wrong on that point?

Many thanks for your help, really appreciated!

John