Features

The new dashboard for tracking workflow failures is awesome, but it would be great if there was a way to put a workflow in a "dev/testing" mode while it is actively being worked on so the success percentage isn't skewed by failures during development.

It can be difficult to know, when looking at the results of a subworkflow (especially when its many workflows deep), what upper workflow it originated from. Of course we can figure this out by loading the contexts and fishing out the originatingExecutionId value, then modifying the URL manually. But this could be better. Loading breadcrumbs in the Workflow canvas would be impossible because any given subworkflow could be a part of dozens of other workflows... but generating breadcrumbs in an execution result should be able to leverage the contextual knowledge of the full run. So like: Parent Workflow Results > Subworkflow A Results > Subworkflow B Results > Name of Subworkflow whose results are presently being viewed With each breadcrumb item being clickable to load the relevant results page in a new window. Could make following the logic of an entire execution easier and, of course, make troubleshooting a bit easier.

Could we get version control / history on Templates like we do for workflows? As far as I can tell, there's currently no way to roll back to a previous version of a Template in the case bad updates / mistakes. Had just lost a fair bit of work today having to re-create a Template after mistakenly submitting partial changes to both the cloned version of a Template and the original.

Example Use Case : We have a bulk update licences form and to give them the option to select users manually, assign based on an existing licence the users have or replace a licence with another, I have 1 Option Gen that can pull back all the licences a company has to cover all of these options, but so all the drop downs are labelled correctly for the users to follow it I need to to make 5- 6 dropdowns calling the same option gen based on the option they pick (Posted on behalf of client)

I would like to be able to have a table input as an option for response gathering. This would allow us to gather multiple part responses to the same question, for example address information of a multi-site company. The field option would allow us to define the field name, as usual, along with the keys for the JSON list generated by the responses.

as a dumb user, I want to put junk in a folder to organize it.

Feature Request: Add support for organization tag-based conditional logic in forms Description: Rewst currently supports organization tagging for workflow triggers, which is helpful for automation. I'd like to see this tagging functionality extended to forms. Specifically, the ability to hide, reveal, or set fields as required on a form based on the organization's tags. Use Case: This would allow for more dynamic and contextual forms, where the visibility or required status of fields could change depending on the tags associated with the submitting organization. This improves form flexibility and user experience, especially for MSPs managing varied customer environments.

I am using custom actions quite frequently and I believe it would make it a much easier process if I could just import raw valid JSON to build the list of JSON objects in the body. This would also reduce time and help mitigate formatting errors. It would also help lower the level of entry for the platform. Bonus points if you are able to have it take raw JSON + jinja templates as demonstrated below instead of it potentially complaining about formatting. example: { "Key": "{{ CTX.Value }}" }

We need the ability to embed/provide forms publicly. We have a lot of forms that are used by outside vendors and/or new clients that are not yet in AAD. For example, we have a Site Survey form that 1099 field techs complete. Another example, a new client that is in the process of onboarding may not have AAD as part of our onboarding is to migrate them from hosted Exchange/etc. We still need to provide them with forms for: Company Details, Billing Details, Sites/Locations, Employee Listings, Letters of Agency and many more.

For workflows like new user onboarding that can have 100+ actions, a search feature would be really helpful when you need to edit the workflow days or weeks later. It can take a lot of time to scroll through a large workflow to find a particular task.