Comments
-
You're assigning the queue to people that you haven't given access to the queue, as it states in the error message. "Assignee does not have update content access to queue". You need to give the assign (Shubham and/or Ajeet in this case) update content permissions on the queue. You haven't shared the queue with them, so…
-
It's the user task right before the conditional gateway. You need to tie that to a form, that provides the response as an output variable back to the workflow.
-
If you're just wanting to understand what cards were manipulated by your workflow, I'd have your workflow include a step to log records to either a dataset or an AppDB collection. I'm not aware of a dataset that is constructed by alerts firing. I'd imagine the 34 rows correlate to your 34 alerts. I may be able to provide…
-
So you're just wanting to have a dataset that shows you all the cards that were manipulated by your workflow?
-
I'm not quite sure I follow. Can you give a little more detail?
-
@GordonCox123 - see above. Forgot to tag you.
-
Feels like this may not be workflows related, but happy to take a stab at helping. If you use the table type "HTML Table" then it will let you highlight text. The issue with the other tables are it's essentially an image….
-
I'm not 100% certain I follow the entirety of your request, but as trafalger mentioned Teams does have an API. I have seen customers who have Workflows writing to Teams.
-
@Jarren - I think, after further research, this is something that should wait for a workbench enhancement. Apparently it would be quite risky to use this end point as you could very easily botch the entire workbench job as it wasn't created for this purpose.
-
When you validate your workflow, do you encounter any validation issues?
-
Yes, you just need to disable them first.
-
Below is your function. Remember that this forum strips out the backticks. You want backticks around the API (as in the screenshot below). Your input is a number. No output const codeengine = require('codeengine'); function disableCardInsights(cardId) { const api =…
-
@Jarren - I'll see what I can turn up. It's not an end point of mine, but I know a guy…
-
Jarren, as it relates to Workbench, there isn't any way for a Workflow to talk to Workbench, because it's running locally behind your firewall in your environment. That said, your idea of having a workflow notify if you data hasn't updated is a good one. I believe there is an end point that can update a workbench jobs…
-
Kathy, I'm sorry about the confusion but in the screenshot it literally says "No Description Provided". Under the function name, there is a description field. Put something in the description field.
-
Kathy, you fixed the backticks, which is awesome. As I mentioned in the email, the community thinks the backticks are a formatting thing and hides them. #annoying I think the reason you're having an issue if you don't have a description. Please put in a description. The requirement for a description is something we are…
-
Kathy, it looks like your function is looking for a parameter called cardId (in your second line, ${cardId} is javascript to insert a variable in to a string, but your function isn't asking for any arguments. As a non-developer also, I've had to figure this out. Let me try to explain. Any values that you want to pass to…
-
Absolutely! You can query a dataset from within a workflow, update a dataset from within a workflow, run a dataset from within a workflow, and have an alert trigger a workflow. We're working on getting some Workflow Templates out in the next month or so. What are you trying to accomplish and maybe I can help? This is Dan…
-
I think what trafalgar said is probably the route to go, but I'd imagine you could create a workflow that ran on the 1st of the month and changed the setting, then ran on the second and changed it back. We'd need to figure out the API call to make that change, and I think what trafalger mentions would be significantly…
-
@DomoDork - it also isn't visible until you have a workflow deployed, so it could have been that you simply hadn't deployed your first workflow yet.