Comments
-
Tony, this is because you have Filesets enabled in your instance. Filesets are in beta and aren't fully supported in the platform, and one area they're not is being able to be passed into an AI Agent. How comfortable are you with light coding?
-
You don't need to give it any additional tools, you would just need to adjust the prompt. You could ask it if it can generate SQL that would result in the same outputs. I can't say from experience how well it would be that because there's a lot of nuance and it can't see your data (as we configured it) but it's something…
-
Here it is attached, because that formatting got weird. https://us.v-cdn.net/6032830/uploads/4RD07MCNA99C/sendemailfromoffice365.txt
-
@KatieLuce - sorry I missed this over the holiday break. Here is the code that I use. If you have any questions, please let me know. CODE BELOW import codeengine import json import smtplib import requests from email.message import EmailMessage def send_email(account, to_recipients, cc_recipients=None, subjectLine=None,…
-
Your second screenshot shows the way it works now. You edit the accountParam to tell it the account type and then you can map it. In order for an account to be available to use in codeengine you need to go to the account in the Accounts Center and under advanced options you need to check that box.
-
They're pretty amazing!
-
The API constants should have ticks around them, like this ` at the beginning and the end.
-
Here you go: const codeengine = require('codeengine') function createTask(projectId,listId,taskName,taskDescription,owner,tag) { const api = /api/content/v1/projects/${projectId}/lists/${listId}/tasks; const payload =…
-
Super possible and very much supported. Give me just a second, I can write a JS function for you.
-
@nazgul - I don't know of a tutorial or video that addresses the different aspects of this directly, but it's a good for one that we can/should create.
-
Additionally, you can call CodeEngine packages directly as well…so something like appending a row to a dataset can just be done via CodeEngine directly and no workflow required.
-
Yes, you can. Open the brick in the pro code app editor and you can add datasets, workflows and/or appdb collections to the manifest and then adjust your apps code to interact with all of those. I might suggest you start with the "Workflow Form Start Brick" and integrate your existing code in there, or take the bits that…
-
Have the first step in your workflow be to check the connector/dataflow status. Then hit a conditional gateway. If it’s running, abort and do nothing. If it’s not running or hasn’t ran in X time, then run it.
-
The alternate approach you mention is a great one, and one I've helped many clients do. You would essentially build a pro-code app that displayed certain information from an AppDB Document. Your workflow then generates the insights, and writes to AppDB. The app displays those insights on the dashboards/
-
Just keep in mind, CodeEngine runs server side code inside of the Domo infrastructure. If there's not a CodeEngine function for what you want to do, you can literally pop open the network tab while performing the action(s) you want to perform, and see the API calls it makes. You can then point CodeEngine at those same…
-
Did you try telling the AI Agent to make a chart in HTML? There's lots of approaches you could take getting a chart in an email body, but I'd imagine that would be the lowest level of effort.
-
@Sean_Tully - it sounds like you now need to: 1 - Create a new dataset 2 - Copy a bunch of cards 3 - Rename the cards? 4 - Switch the cards to this new dataset All of these things are possible, but will likely require you to make a couple of custom CodeEngine functions (which I can talk you through).
-
https://www.youtube.com/live/ncd1_tVLrVM?si=cP-TP6J36OxjDUKh This webinar walks through these components in good detail.
-
Also, the email that you're using there is a user task. A user task is a very structured email that prompts the user for a response. In this case, you'd want to use the Domo Notifications package and the send email function to just send an email. To streamline this, you can just make that tool available to the agent and…
-
@nazgul - rather than querying the dataset and passing the query response to the agent, add the dataset as knowledge and instruct the agent what data to fetch from the dataset for analysis.
-
This can be accomplished with an AI Agent. https://www.youtube.com/live/ncd1_tVLrVM?si=cP-TP6J36OxjDUKh https://www.youtube.com/live/GlXbWork5fQ?si=LKSOAHmqOmTyI7Zn These are great webinars we did on the topic that I think would be a good place to start. Please share your progress and let me know if you get stuck.
-
@nazgul - you would not feed the dashboard to the agent - you can remove the step. In your AI Agent, you would add the datasets as knowledge and in the instructions for the agent you would tell the agent what information you'd like it to extract from which datasets.
-
Workflows aren't created inside of AppStudio. They are created in the Workflows interface. Workflows are very frequently executed from AppStudio, via a button on an Action (as an example).
-
It sounds like support for this (the File rendering properly in a user task) will be in the code base in early November. So sorry about the delay in that. It's part of the beta part of the filesets beta. Thanks for surfacing.
-
I haven't played around with this functionality since the Fileset beta started. Let me loop in the engineering team on our end.
-
No way that I'm aware of. One thing I'd imagine you can do (I haven't done this yet), is use the DomoStats Dataset for Workflows to get an alert on when that happens.
-
There are API's for getting tasks, completing tasks, etc… but there isn't any code engine functions or anything that are published (that I'm aware of) that will do this. You'd need to create the interface and codeengine functions from the documentation.
-
ArborRose nailed it. I haven't actually tried doing this in a Workflow form, but I'd assume it will work. You're just missing the HTML. AI is amazing, but it isn't always correct. Looks like it led you astray on this one.
-
@JohnXClifton - the best way to handle this is not with a parallel gateway, but rather a non-interrupting timer on the user task. If you go to the user task, in the config pane on the right you'll see a timers tab. Create a recurring timer, that is non-interrupting (interrupting timer voids the user task, non-interrupting…
-
Check this out: https://www.youtube.com/watch?v=B5AA03yUlr4