Oprimize flow user experience. #21737
Replies: 1 comment
-
Hello, Overall I agree with this ticket. Adding some quality of life things to the flows would be nice. I have some things I'd like to see as well. Maybe if this request is voted we could consider adding some additional optimizations. Add Links for Triggered From and Triggerd To ItemsI created a separate issue for this, but I think it fits here. #22092. The idea is to add links to any flow that may trigger the current flow, and also links to any flow that might be triggered from this flow. This allows easier multi-step flow management without having to go back to the flow list and select the flow you need to view. Encase the Flow Payload with the Operation NameI consider this one HUGE. When looking at the logs, it would be nice if the operation payload was encased in the operation name - as it would be in the actual results and won't leave me guessing (or referencing) what the operation name is. For example, This simple addition will make understanding flows MUCH easier for a newcomer. We will now understand visually what $trigger means, and for each and every operation, we will get a clear visual as to where the data we are seeking is located in the tree of JSON. Show JSON in Code BlockBy Placing the JSON in a code block we can more easily search it, and we can copy it. This should follow the interface for Code:JSON as in the current field interface functions. Copy JSON LInksI would like to simply copy the entire JSON block so I can view it or use it elsewhere easier. (Alternate/Addition to Code Block) Collapse and Expand JSON Tree in LogsBuilding off the last idea, I would love to see a tree view in the payloads of each flow operation's log. This will allow us to collapse the tree (items and sub-items), to visually inspect the JSON tree and understand it's structure more clearly. Unfortunately, this probably requires a library - which I'm sure is avoided. Here is an example of what I mean Tooltip over each variableI would love to see a tooltip when hovering over a field name in the JSON tree that would show me the location of the variable. For example, when hovering over "id" in this example, you would view {{$trigger.payload.id}}. If you click on the item, it should copy that location to your clipboard.
Limit the count of logs returnedI've noticed when I've ran a view many times, the logs won't load very quickly. They seem to be loading hundreds of logs each time the Log button is pressed. Maybe limit the query to return only the first 10 and then call a "more" to view more. |
Beta Was this translation helpful? Give feedback.
-
Summary
Faced with complex flows, there's a need for simpler shortcuts to reduce operational costs.
#21723
Basic Example
No response
Motivation
Faced with complex flows, there's a need for simpler shortcuts to reduce operational costs.
Detailed Design
3.7.mov
Screen.Recording.2024-03-07.at.15.26.09.mov
Requirements List
Drawbacks
Alternatives
Adoption Strategy
Unresolved Questions
No response
Beta Was this translation helpful? Give feedback.
All reactions