Comments
-
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.
-
Let me know when you are ready.
-
ZOOM LINK REMOVED I waited about 15 minutes and you didn't join. If/when you're ready let me know and if I'm available I'm happy to help. Otherwise to do it via text I'll need some more detail.
-
I'm not sure I follow, shreeyab. It sounds like someone is looking at a card, based on what they see they fill out a form? Do you want to hop on a Zoom and show me what you're trying to do?
-
If that's the case, I'd write a workflow that had all the required input parameters, and have a singular step to "Send Email" and build the email body using the variables that were input. For the form, I'd grab the "Workflow Form Start Brick" from the AppStore, and modify that brick to have the fields you want to capture…
-
All you want to do is send someone an email that has the details of the submission?
-
That's because your workflow is configured with a required start parameter. If you want the workflow to go get the parameters on it's own, you'll need a version of the workflow that doesn't have a required start parameter, but has an added task to to query a dataset (or something) to get the list of items you want it to…
-
You can have a schedule start (run every morning at 9am, for example) or you can have any external trigger. A button on a dashboard, you going a pressing "start" on the workflow, etc… You can go to your alert driven workflow, and just hit the play button.
-
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.