DanHendriksen Domo Employee

@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.

OK. How many of these are there roughly every week, and are these tasks to be performed by certain individuals or by anyone of a list of people? If by certain folks, are there attributes of the task that assign it to them? As I mentioned…it could be done two ways that I can think of. What you outlined, or alternatively…

Considering the source of the data and what to do with the response are important considerations.

Workflows and a form should work well, yes. How many of these is someone to process? And what do you do with the response? It may be easier using a Brick, that allows people to change the value and syncing the AppDB data to a dataset that can be a dataflow input to overwrite old values. Multiple ways to skin the cat. As…

The forum software eliminated the backticks, but I'm guessing you follow.

Kyle, sounds like a great use case! As far as the SQL query goes, it follows the same syntax as beast mode. Encapsulate your columns in backticks, strings in single quotes, etc… I'm going to try and write a sample query below, but sometimes this platform does strange encoding things. SELECT ID, First Name as FirstName from…

P, I retract my previous statement. We have temporarily removed that Forms button as part of a migration. You'll now see/build forms in either the Workflow or App Studio.

P, please make sure you've got the appropriate grants on your user account. We have not moved the location of Forms.