DanHendriksen Moderator

Vaco, if I wanted to do this, I would probably quickly create a dataset view that had the aggregated view you wanted, then create a dataset alert with filter rules. THen you could get an alert that says something like: Product 3 has dropped below 10%, and is currently at 8%. Something far more descriptive. If you want to…

To answer the last part of this, for some silly reason the product doesn't let you define an object to include a list. You were doing everything right…in your first attempt to define the object if we allowed you to say it was a LIST of persons then you would have been golden, but for some reason the product doesn't allow…

@Jarren - I think you're being too hard on yourself, and I apologize that I didn't explain it better. Did you see my other comment? If you create a new package in Javascript, paste that code, set the inputs up as I show in my screenshot and set the outputs up as a boolean you're in business. It will work, will work…

Workflows isn't the right sub-forum for such a question, but I'd just do a calculated field where you multiply your value by 100 and display that (with the box unchecked on the visual). That will ensure the underlying data is 73.45 and not .7345 (for example).

To answer your question though, the "fetchGroup" function will return a list of all the people in that group, including their ID's. Then you can define the objects and set ID as a person. The code above to email the group directly is far simpler though.

@Jarren - I have good news for you! The code below will do what you're after. This will be added to the global packages soon. See the screenshot for how the inputs should look. async function sendDomoEmailToGroup( recipients = [], subject, body, attachments, ) { const parameters = { subject, text: ` <div style="display:…

We're going to enhance the function to include group support soon. For now, you would need to run the fetchGroup function in the Domo Groups package, then create a list of persons from the list of ID's returned and email to that list of persons. Does that make any sense? LOL

@claudio_sp - there is a much simpler way. You can just define the open object by editing the variable, and then everything inside the object can be referenced directly. There is no need to write any javascript/python code - no need to author a custom function. See this instructional video: CC: @GrantSmith

Pravin, nobody can see your codeEngine package without having access to your Domo instance. You can paste your code here and I'd be happy to take a look. Is there a reason you're not using the existing Domo published function for appending a row to a dataset?

If I were tasked with this, I'd look at the "Workflow Form Start Brick" to create my form, and have the data fed to a workflow that took care of your data logging, your 48 hour wait and the additional actions you need to take.

Sounds simple and straightforward. I'd encourage you to take the free "Getting Started with Workflows" course at learndomo.domo.com. Feel free to reach out to me directly if you get stuck. Dan.Hendriksen@Domo.com

Yes, we did. It was very simple. What are you trying to accomplish?

We are releasing DomoStats for Queues in July, and that will include all that metadata that you need. If you want to do it now, you'll need to add a step to your workflow right after the task is completed that logs the information you want to track to a dataset, and do that for each user task. If it isn't urgent, it will…

That's odd. I'd encourage you to reach out to support. We can get it escalated.

You need to map the output to a variable. On the output from your function, in the drop down hit create variable and map.

I’m here to help. I don’t know why my name is Zoolander, either. Ha ha. This is Dan Hendriksen. I think we’ve met before.

You don’t need a variable for card ID, either. Variables are used if you want data fed in from somewhere and stored to be used later in the workflow. I think you can flip your workflow to a message start, have the only function be to send the scheduled report and then end. Then create your alert and have the action be to…

If that’s the case, then there’s a few things. 1 - you don’t want a timer start. You want a message start. 2 - you shouldn’t need your conditional gateway, but if you wanted to you could setup your workflow with a required start parameter and have the alert pass the number value to that required start parameter. Then it…

Any function that provides an output. You want a function that determines if it’s the 5th of the month or not, right? You could do this a couple of ways. You could set an alert that fires on the 5th of every month and have that alert start your workflow. You could write a function that returns true or false based on if…

The message is because you don’t have a step prior to that which casts a value to the variable. You need a step that sets an output to the variable you’re wanting to evaluate. Does that make sense? I’m sorry you’re having a difficult time. We’ve got some step by step training content that is being edited now.

There isn’t…yet! I’ll make one…maybe I can do it tomorrow. I can use what you’re trying to do as my example.

This can 100% be done via Workflow. We don’t have a global package for at the moment, but the API could be sniffed and called from CodeEngine. Is that something you feel comfortable doing? I am happy to help.

What you have there using requests will work to make external API calls.

So help me understand your question, please. Are you looking for how to use codeEngine to make internal API calls? I'm not sure what your question is.

Are you referring to external API calls? I know with JS I use Axios…I'm not much of a Python person, but have you tried using requests? requests.post, requests.put, requests.get, etc… are all supported if you import requests. That's what I've used successfully in the few times I've used Python.

I'm just trying to share ways to achieve what you're after. My first suggestion would accomplish it.

Atieh, because today, you can't have an App Studio form submission start a workflow. Ideally, either the form submission could start a workflow OR the form submission dataset would support dataset alerts. Neither of those things are possible right now, unfortunately. The form submission starting a workflow should be…

The dataset created by the Form won't allow you to create a dataset alert on it to pass the values. A workflow can very easily post to a Buzz channel. If it were me, and I were in this position, I would use the "Workflow Form Start Brick" to have the form, and I'd have that go to a Workflow. Once it's in the workflow I'd…

Is this a form in AppStudio?

It is. I'd check your permissions.