UX / Design

When reviewing an execution summary, I should be able to view a transition's data alias values (at the time of execution) just as I am able to see a task's response data. This is incredibly useful when troubleshooting more complex workflows.

Useful for troubleshooting if i run a "with items" and get 100 results and notice in a spot check that some are not working there is not an easy way to track which execution was the result I want to troubleshoot. Example screenshot, I have device name available but can only see Process_Device unless i click into each one. Would like to be able to select a value to add in as a column

Allow transitions to rotate (or enable multiple connection points) so arrows do not cross over each other.

The latest version of the canvas/builder now allows transition arrows to exit either the bottom or to the right. If I have a transition that is exiting a task on the bottom, I would like to move it to the right. I can't do this without deleting the transition and pulling a new one from the right exit point. There should be a way to move this back and forth between the two (bottom or right exit points), especially as we reorganize workflows that are built with the previous editor.

I have a task that stretches vertically and its annoying when the streams cross. Being able to stack task transitions vertically would be cool

Would be cool to control the color of arrows connecting actions in a workflow based on custom controls for organization, ie on success being green, on fail being red, and a custom color selector for any other custom transition.

Currently, in the new Canvas, both workflow start triggers and on-completion triggers (such as Failed or Timeout) are displayed together under a single “Trigger Configuration” section. This makes it less clear at a glance which triggers actually start the workflow and which ones run after execution. Although labels like “Outbound” provide some context, visually they appear as the same type of trigger. Suggested Improvement: Split triggers into two clearly defined sections within the UI: Run Workflow Triggers These are triggers that initiate the workflow, such as Cron, Webhooks, or Integration-based events. On Completion Triggers These are triggers that run after the workflow completes, such as Failed, Timeout, or Success alerts. This could be implemented either as two sections within the existing Triggers tab or as clearly separated containers with headings. Why this helps: Improves clarity and reduces confusion Makes workflows easier to understand at a glance Aligns with how users think about workflows, separating start actions from outcomes Speeds up navigation, especially for more complex workflows

We would like to be able to upload files into forms that are not CSV/Excel format. Could we have the option to upload any file and perhaps have it encoded in base64 and stored as a variable in a workflow?

I don't think I've ever seen pagination implemented where it doesn't show you how many items or how many pages. You have no idea how many times you have to click > until you are at the end! Please add proper pagination that shows how many total records and some mechanism to show how many pages or to also jump to beginning/end. Thanks.

When viewing workflow execution history, users can currently filter by date but not by time of day. This makes it difficult to isolate executions within a specific time window (e.g., 10 PM to 11 PM) without manually paging through a high volume of results. Request: add datetime filtering so users can specify both a date and a time range to narrow down executions quickly.