Features

I have been struggling with proper workflow maintenance and testing. My customers are all on Workflow A, but if I want to make a feature update or troubleshoot an odd issue, I would need to update the 'Production' workflow. With that brings the potential to break the live version and any execution that may occur while I'm working on the workflow. The Clone function is recommended by documentation, but does not fit this use-case for a couple of reasons. If I clone to the same Org, it only copies the top-level parent workflow. If I need to make changes to a sub-workflow, I would also need to clone that. This creates multiple versions that then need to be maintained and cleaned-up. For example, I now have 5x of one type of workflow after I cloned back-and-forth one too many times without knowing the consequences. If I clone to a 'Test' Org, that is going to break specific permissions that may be setup where the workflow needs to run from the Parent Org. While these can be individually adjusted as a workaround, it's not clean and creates a lot more overhead to get to a place of testing. There needs to be a way to completely sandbox the workflows, with proper versioning and functionality to promote changes to the Production workflow.

Due to additional security requirements for some organizations, we need the ability to restrict technicians from specific organizations. They should not be able run forms, workflows or see results for the organizations they are excluded from.

The inability to apply Filter Options to Dynamic Options using the built-in integrations forces us to manually re-create the functionality of the built-in feature for every data source, even for a minor tweak to the data presented in the form

When working in the workflow canvas, there is no way to adjust the appearance of action labels. For complex workflows with many actions, being able to customize text size, font, and label colors would help builders visually organize and navigate large workflows more efficiently. This is particularly valuable for workflows that have been built up over time with many branches and steps.

When a partner unpacks or unsyncs a crate, there is currently no way to receive notifications when that crate is later updated by the Rewst team. Partners have to manually check release notes to know whether a crate they're using has changed. Proposed: an option to subscribe to update notifications at two points: (1) when first unpacking a crate, and (2) when choosing to unsync a workflow within a crate. Subscribers would receive a notification when a new version is published, even if the update wouldn't affect their unsynced version. This would help partners stay aware of improvements and bug fixes without requiring manual monitoring.

We understand that Rewst currently does not provide a native backup mechanism for workflows or configurations, aside from manual exports. As an MSP, we rely heavily on Rewst for critical operational and automation processes, the lack of a supported backup process introduces operational risk in cases of accidental deletion, platform issues, or auditing requirements. If you can provide an API or a Rewst Action to export a workflow, that would be very helpful as a start. From there, we could build a workflow to back it up ourselves but since there isn't any automated way to do this, it's put us in quite a spot. I think this was being discussed internally as mentioned by one of the Rewst support when I raised a ticket last time. Could I know if there's any ETA to this being implemented?

Every time a workflow is saved or tested in Rewst, a new version is created in the workflow history. During normal development, when iterating, testing, and making small fixes, this quickly floods the history with minor, incremental versions that do not always represent meaningful changes, making it difficult to read and manage. Introducing the ability to squash workflow history versions would allow users to consolidate multiple versions into a single, clear entry with a meaningful summary. This would let users: Collapse multiple dev and test versions into one Add a clear description of the overall change Keep history focused on meaningful milestones rather than every minor edit This would significantly reduce noise from save and test cycles, make history easier to review and audit, and improve maintainability when troubleshooting.

Show where tags are referenced on the Tags page (or at least a count).

We would like to be able to allow workflow retention greater than 30 days. 120 days is the target.

It will be very helpful to be able to replace actions/tasks in a WF but keep all connectors, transitions, data aliases, etc. A good use care example is when mapping out a workflow with noops and then replacing them with the correct actions as you build it. Or when an action is deprecated and a new version is available.