DanHendriksen Domo Employee

No matter what, responses will be tracked at the individual level, by the way. The metadata will always show which user actioned/completed the task.

Nate - I’ve had customers take the approach of dynamically creating the group, adding the users, sharing the queue, then deleting the group and so on. I have a function I can share with you, that will allow you to programmatically share a queue. Here’s another thought. Could you make a dynamic group with a rule that…

The approach that I personally would likely take, is writing this new data (application decision) to AppDB and joining it back to your source data in a VIEW (no processing time and no credits used in the join), and then materialize it back to the source data on infrequent schedule.

I know the product team is working hard on some of these data update features…maybe we will see something at Domopalooza? I do lots of these things with AppDB. The way that update a row works, is by defining an UPSERT key (which is a unique identifier for each row, and typically a combination of columns) and then sending a…

I agree with you that documentation could be improved, and we could have more videos. Please keep the feedback coming - the videos which I created were a result of things I recognized and feedback I heard from customers, and I'm happy to make more. I'm also happy to pass feedback along to the product and education teams.

There's a global package that you'll want to add as a first step in your workflow that will return the person that started the workflow. It's the "Get Executor" function in the "Domo Workflow Executions" package. FYI - currently this package is showing up under the "Custom Packages" section.

You can copy and paste in a workflow. Hold down the shift key to drag and select numerous shapes, then press "Control-C" to copy and "Control-V' to paste.

Well, Workflows are certainly capable of adding users in Domo. That's really simple. As far as the trigger - what tells the Workflow to add the user, you've got a couple of options: 1 - Use the SFDC connector to pull in a user list and create an alert when a new record is added, and have that alert trigger the Workflow to…

You are wanting a Salesforce app, to kickoff a workflow in Domo that creates new Domo users? Did I understand that correctly?

@NateBI , is the task assigned to a group? Or do an individual? You do need to make sure that you go into Queues, and share the queue with the appropriate people. That isn't something that we've done dynamically in the workflow, but suppose I could help you write a function to do that. The current guidance would be to go…

Nate, thank you! Can you clarify the video you think would be helpful? Happy to get it made. And yes - when you version workflows that start workflows it has a cascading effect. You always start with the last one, get it deployed and then work your way back. We have plans to make this easier down the road.

There's a typo in the Products mapping file. template_suffix is now templateSuffix The doc shows template_suffix on both sides.

@NateBI - glad you got this up and running. If you have any thoughts/notes to share with the community that would be awesome.

Recluz, I would encourage you to replace the "Query Dataset" step in the template (new updated template should be out soon) with the new Query Dataset shape (click on the 3 dots on the upper right of the shape, and you should see that option). Alternatively, you can edit the "currentRow" object variable to add the children…

You have a list of objects and you need a list of persons. Send me a DM and we can setup a call where I can show you.

@Ashim - this functionality released today. If you go to Workflows, you'll see you now have the ability to set a default value. You should also see a popup letting you know how to use the functionality. If you get stuck or have any questions please let me know.

Sudheer, I would encourage you to take the Getting Started with Workflows training found at LearnDomo.Domo.com. Specifically the part where we help you build a workflow that finds inactive datasets and tags them. The logic will be IDENTICAL, expect instead of tagging a dataset you will delete a user. There is a global…

It looks like this is a bug. Stand by for resolution/additional details.

Not that I'm aware of, but I can't speak for the product team. Everyone THINKS they want the email user task, until they actually use it. Having to login on the browser after you click the button, having the predefined responses…it really isn't a great user experience. I'd encourage you to try forms and either the…

Sorry I missed this. You can define a userId as a person and pull it from an object to make a dynamic assignment.

Do you have two paths from a conditional gateway that are connected to the same next step? Have you moved the different shapes around to make sure the lines are all actually connected and don't just LOOK connected? Are any of the shapes outlined in red?

You would map the output from the "New Users" step a variable, and you would then pass that variable in here. So go to the "New Users" step, on the output select "Create Variable and Map". If you setup your step correctly, it should create a list of variables that is a person. You can then pass that in as an input to this…

@NateBI - sorry you're having an. issue. In the query field, on the right hand side, define your output as persons. FYI - a person is a user ID. So if your query were something like "SELECT USER_ID FROM DATA", then the output will be a list of strings. Change the output type to a list of persons using the menu on the…

That hasn’t been available, but is actually being released to you next week. As of now you cannot, but next week you will. I’ll be releasing a video highlighting the new functionality.

Lines 145 and 146 are where the "isEditable" can be configured to be dynamic, or set to true/false. Please let me know if you get stuck or have any further questions.

I just pulled up the code that I think is what I used in the webinar? In the app.js file, line 54 has the filter. If you comment out line 54 and line 57, and uncomment line 56, that should get rid of the filter.

My first thought, is why not adjust the query so it only returns rows that you know you need to action? You can add a WHERE clause to the query. SELECT * FROM DATA WHERE ` Number_Column ` = 1 Then you don't need to process through everyone and check to see what the value is - you already know the value. You can also remove…

So it sounds like what you want to do is send an email if a numerical value meets certain criteria? Is that correct? And no worries at all! If this is your first workflow you're doing great! There's a definite learning curve.

Yeah, totally. If I recall, in the example we set it up with a filter. It filters out the ones that have had the action taken on them. You could remove that filter from the query. There's also a section in the code that handles whether a row "isEditable". I believe in the example we set that to true, so they are all…

You could do things concurrently…so have one workflow that identifies all the rows, this kicks off a second workflow that does the sending of the email. If the first workflow identifies 100 emails to send, it will start 100 iterations of the step 2 workflow that all run concurrently. That said, none of this should take…