Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.6.0
-
None
Description
This may be captured in andrewmlim's UI/UX notes, but I propose that when a component state is changed (i.e. started/stopped), the (local) canvas is refreshed automatically. Basically, when new users start a processor, because the canvas doesn't refresh immediately, they do not always get immediate feedback and realize it is processing flowfiles.
I also understand that on canvases with giant flows, it is not always performant to refresh the entire canvas on every change. Perhaps just the local process group or N processors, or just upstream/downstream connections could be refreshed immediately, with other components being refreshed from the scheduled refresh action.