Features

We have the option to enable a trigger for all current a future orgs, but if we want to exclude a few orgs, we have to use manual selection and future orgs are not automatically added. It would be great to have an exclude option by selecting the org or by tags.

As per title, the majority of the time I click "View Results" is just to then load the Context in the Jinja2 Live Editor... would be a nice QoL improvement to have a link to take you straight there from test.

Currently, when attempting to onboard a new client that was previously managed by another MSP that also uses Rewst the client's tenant will not display in the Microsoft Bundle integration. These migrations require a ticket to be opened with the ROC and my understanding is that the developers have to update a table to manually move the tenant ID from the old MSP to the new MSP. For those unaware of this limitation, it can seem like there are issues with the integration or Microsoft not showing a new GDAP relationship. Given the growth of the platform and overall industry trend towards both acquisition and turnover of MSPs, I would like to see something developed that allows a more seamless transition that doesn't require manual intervention.

When re-running a workflow, currently you only get the option of re-running the entire thing (and any sub-workflows individually). If you run a hefty workflow and find out you did not adequately prepare a prerequisite (such as org variables), it is sometimes detrimental to re-run the whole flow if it does not have checks for pre-existence of certain items. A solution (that's not just changing how your flows are written) would be to allow selective re-running of tasks in the workflow. The one thing I haven't quite figured out in my head is how to properly deal with context. In the situation I outlined above, you would technically want all context to persist besides the missing pre-requisite so that the workflow functions as intended with the new value. IIRC, the current functionality of re-running does not allow that. This may need to be paired with some sort of context editor before the confirmation of the re-run, but folks smarter than me can probably come up with a cleaner solution.

When using the "Test" button in a workflow, allow multiple Rewst organizations to be selected to run multiple test executions for each selected organization

I would like an export that would allow us to more easily perform code reviews. Right now, we export as JSON bundle files, which contains a lot of workflow fluff to sift through. Ideally, we export a workflow which would have an easily readable json file, that shows: Names of tasks Transitions and settings Variable assignments Jinja This would allow us to more easily perform code reviews internally. A bonus would be allowing us to programmatically pull/push imports. This would allow us to have a no touch solution to export, review, and push changes to workflows.

Currently, Jinja expressions in inputs are automatically rendered when the workflow loads. This creates a risk of unintended Jinja injection, especially when handling data from external sources or URL parameters. To improve security and control, it would be helpful to have an option that prevents inputted Jinja from being evaluated immediately upon workflow execution.

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

Adding the ability to generate a PDF in Rewst.

It would be very helpful if a workflow had a button that showed a list of other workflows that call this workflow. There are occasions where a call-breaking change might be made to a small component who is reused frequently and currently it's necessary to wait for failures and process through those to remediate in the absence of manual documentation.