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.

We would love the ability to update details of workflows, specifically the time saving value, from within a workflow.

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

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)

Allow us to create groups that we can assign roles to in Rewst. For example "Forms" group would have the Forms role only. "Engineer" could have read-only, "Manager" could have member etc. This would also help keep the list of users cleaner by nesting users within those groups.

As I dive deeper into the mystical realms of REWST organization structures, I’ve had a revelation—nay, a vision! What if we added a third tier to our hierarchy? Picture this: Parent Organization – The mighty MSP overlord, the all-seeing eye, the supreme ruler of the REWSTiverse. Child Organization – The client, loyal subject of the Parent, but with a rebellious streak and a penchant for independence. Grandchild Organization – The customer sites. These are the wildcards. The rogues. The Han Solos of the REWST galaxy. They follow the rules... unless they don’t. Why a Third Tier? Because reality is messy. Tools like RMM, Auvik, and other site-specific applications don’t always play nice when everything is lumped into one big happy family. Sometimes, you need to say, “Hey, this config is just for Site A, not the whole dang client!” With a Grandchild tier, we can: Assign tools and integrations at the site level. Keep configurations clean and scoped. Avoid the dreaded “Why is this alert firing for every site?” scenario. The Power Dynamic Let’s talk governance, because every good empire needs rules: Parent Org: The Emperor. Sets the laws of the land. All defaults, flows, and variables cascade from here. Child Org: The Governor. Can override the Emperor’s laws with local edicts (a.k.a. variables and flows). Grandchild Org: The Rebel Base. They do what they want. If they define their own variables or flows, they take precedence. If not, they fall back to the Child, and then the Parent. It’s like inheritance, but with more drama. TL;DR: Let’s build a third-tier org structure in REWST: Parent → Child → Grandchild. It’ll make tool integration cleaner, governance more flexible, and give us the power to manage chaos like pros.

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.

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.

We upload our forms to IT Glue with the name and URL. Since some forms are being created by rewst and some by ourselves the naming conventions are all over the place. This makes it hard for our technicians who don't work in rewst to understand which one is meant to be used. I also would not want to present a form to a client without being able to control the title as having [CRATE] in the middle may be confusing to a client.

I would like to see a built in chat system for talking to other people all editing the same workflow.