I have 2 actions. Action A, when submit, created a bunch of Field objects. Action B, takes an array of Field objects as input and created a Ticket and links it to the Fields.
Is there a way in Workshop to kick off these two actions in order. Action A, get output, and use it as input to Action B, but without the user having to click submit twice (for the two actions in serial order).
I thought maybe I could use the “On successful action submit” for Action A to trigger the submission of action B (passing the output from Action A into Action B). But I don’t see that options in the “On successful action submit” section. Only to reset variables and/or move to new views.
I’m using the “Inline Action Form” in Table view. Any advice is much appreciated.
Just confirming that this is not currently a way to trigger two or more actions sequentially, but you can often construct a single, complex function-backed action to handle this kind of multi-step edit. That’s likely an option worth exploring here.
That is our backup plan. Since we’re shipping this workflow via Marketplace, we wanted to reduce the burden on the installer. We wanted to remove the work of them having to write a function themselves that does the two steps. And instead just get our workshop app and functions for free.
Another alternative we’re considering is embedding a slate widget in our workshop. Cus in slate I think I can do something like this.
Another option to consider is potentially using an Automation that triggers to run another action. This would also provide you flexibility if you only need to trigger it in certain conditions.
That was our other thought. But after the second action is complete, we’d show the full Ticket view, with all the Ticket details AND linked Field objects. So we’d want it to happen right away vs. waiting for an automate to run a couple minutes later.
In that case, I think your best option is a function-backed Action that makes multiple edits. What’s blocking the function from being packaged up using DevOps and deployed via Marketplace?
Since the Field object (inline action A) needs to be created and linked to the Ticket object (created in Action B), the order is important. Essentially, we want the following:
A form that includes some basic fields and an unlimited number of custom fields. Given that the number of custom fields can be arbitrary, we believe the only way to support this is to have the Custom Fields object type linked to the Ticket object type (which includes the basic ticket fields).
For the workflow admins when this is installed, we want them to define as many custom fields as they need. Then, when their users visit the form, we want the users to only have to click submit once after filling in both the basic and custom fields. The problem is that we don’t know the number of custom fields in the installed version of this workflow, so we dynamically display them in an inline table widget.
At the moment, this means users input the custom fields and click submit (which creates the Fields), and then they fill in the basic fields and click submit again (action B, which creates the Ticket and links it to the custom field object).
The problem lies in the dynamic nature of the form we want, given the potential number of custom fields.
We can package a function-backed action with multiple edits, but then the front-end form doesn’t work (how do we allow them to create multiple Custom Field objects in one Ticket action form)?