DanHendriksen Domo Employee

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…

You could try and adapt this: https://developer.domo.com/portal/4w40o03817vij-hitting-a-code-engine-function-from-an-app#calling-a-code-engine-function-code-example I haven't tried it, but this: domo.post(/domo/codeengine/v2/packages/${functionAlias}, inputParameters ) Would become this: codeengine.sendRequest("POST", api,…

It's designed to prevent runaway processes. But if you know that you're going to go through it more than 1,000 times, let us know and we'll raise the limit.

We have a limit of 1,000 passes through a shape. We can raise that limit at the request of the customer. You can reach out to Domo Support to get that limit raised, or in this case you can just message me.

Okay, I see you have your code here. For me when I'm learning, I start super simple. Remove all the required start parameters from the workflow and see that you can successfully start the workflow without the start parameters. Isolate where the issue might be occurring. It would be helpful for me, if you could share the…

Can you show me the workflow start shape showing required parameters, and can you show me the part of your app where you're making the call? Specifically the JS where you're making this call.

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…

I should clarify the solution I proposed (moving to a workflow start form as opposed to a dataset based form and using AppDB to status updates, reporting, etc…) is the that one requires no code, no bricks, etc… Of course your solution doesn't require those things either, but the upsert part will bring a high level of…

@bdetcher - totally get it. I build stuff like that all the time. The good news is it can be done without any writing any code at all, and without using any bricks. If you want to do what you originally outlined, then you'll want to: Enable upsert on the form dataset/define upsert keys (I haven't tried to do this on a form…

If you DO want to update a record in a dataset you can, but you need to enable upsert and upsert on that dataset. It's much more nuanced though. Leveraging an AppDB collection will be more efficient, and give you a lot more control. Saving the responses being written to the dataset and having an alert trigger the workflow…

I would not have the form write to a dataset. I would use a customized workflow start form to have the user fill that out, and then use AppDB for the logging and updating.

I'll put it on my list to get it created, along with a little video.

Ah, I get what you're saying. There is no "CONNECT" option on the little plus tab. I'll bring that up with the product team. I suspect for now you'll need to work around by essentially recreating the "Make Fee a Percentage" shape.

1 - You can have as many paths as you want out, but it sounds like you only want two. If you want, you can multiple multiple and/or rule sets on one conditional. Just add a new rule, and select and/or. Is that what you're after? Multiple conditions that could send it down the same path? 2 - We need to publish global…

@t238 - I'm totally happy to help you with this. It sounds like Mark is aware of someone who just did it - tell me…it's just as simple as taking some of the inputs from the form and using them to create a task in a certain project? If you can share more details, I can be more closely aligned with your exact use case in the…

OK. I can't speak to what our plans are there as I haven't checked with the apps and security team. I'd think the fact that these forms in App Studio will be allowed to be embedded publicly opens up the door for bricks that write to collections to embedded publicly too but my understanding is we blocked that functionality…

This particular thing I'm referring to is the ability to have a Form present in an App Studio app and function in embedded contexts. There may be changes made to the way that these types of Bricks are handled, but I'm not aware of any. Are you trying to get that brick to work in Public Embed?

Hey guys, I know the product team is working to get support for Forms in embedded contexts. It will be included in the November release. It will work with both Public and Private embed. There may be a chance to participate in a beta sooner, but I don't know for sure - reach out to your CSM.

No C! I don’t know who that other guy is 😂 Thanks for being here!

In looking at this again, this was prior to us having templates. Using the loop over dataset template this should not take long to build at all. Probably <20 minutes once you’re familiar with Workflows.

If you look at the “getting started with workflows” training at learndomo.domo.com, one of the examples is essentially just like this. Between this write up and that video you should be good to go. Let me know if you get stuck.

Perfect, thank you!

Sorry about the confusion, @Jbrorby . Yes, we rolled out one of two UI/UX adjustments and only 1 has gone into effect. I hurried and put the training out knowing the changes were coming, with the idea being I could get feedback to incorporate into the recut which will happen soon once the second change drops. In this in…

@sstorm183 - how did you get on? You in good shape?