Features

It would be useful to be able to see which training's staff have completed in the Rewst University inside of Rewst. Right now, we need to reach out to our AM to get this information. Would also like to be included on the emails that are sent when they submit the test so we can potentially automate that into our HR platform.

For auditing purposes we would like detailed audit logs of all actions users take across the platform.

I understand that the log retention has a max of 30 days as the CTX is sometimes huge and it was taking up too much space It would be nice though to retain the run log with just the inputs (and maybe outputs). This should be significantly smaller and should serve the purpose of knowing what ran what and with what inputs which is enough in 99% cases and for most compliance needs. Adding the first CTX object would be a plus as that includes the triger info and user info. Thanks

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?

When a workflow fails, I think it would be beneficial to everyone if we could have a "Resume from Here" option in the workflow. It would use the existing CTX data up to that point, without having to re-run. This would allow us to fix potential issues outside the workflows control that had a problem without having to re-run the whole workflow for things that a re-run would not be compatible with due it already previously making changes.

Please give us the ability to backup workflows / push workflows through github or azure devops. We need this so we can handle better version control and collaboration. It would also make it easier to build with AI tools. Please and thank you.

When you have many tasks transitioning into the next task, and you want to disconnet or move one of them, you cannot specify witch connector your trying to move. You end up needed to move all of them until you magically find the one you want out of the pile. There needs to be a way to select or disconnect the one you want.

Currently, when using a form in REWST to upload files, there is no built-in mechanism to restrict the file types that users can select. When requesting specific file formats from users, this limitation forces administrators to handle validation inside a subworkflow after the form has already been submitted. This creates a poor user experience: if a user uploads an invalid file, they only find out after submission, forcing them to repeat the entire process from scratch. Proposed Solution: Add functionality to define allowed file types directly at the form field level. Technical Details: Configuration Option: Allow administrators to specify permitted file extensions (e.g., .csv, .html, .pdf) or MIME types (e.g., text/csv, text/html, application/pdf) directly in the form field configuration. Frontend Validation & Error Handling: Prevent the upload or provide immediate, clear error messages on the form before submission when a user attempts to select a disallowed file type. Benefits: Improves User Experience (UX): Prevents user frustration by catching invalid file types instantly on the form, rather than failing later in a subworkflow and forcing the user to restart the process. Improves Data Integrity: Ensures only expected file formats are processed. Security: Reduces the risk of invalid or malicious file submissions reaching downstream workflows. [=🤖=]

When a workflow fails and that triggers a listener, being able to pull that failure reason into the listener could be useful.

I need to be able to uncompress Zip files as Microsoft is pushing out some reports as Zip files with json files in which we need to automate