Russell, Thanks for the feedback.
Specifically regarding the Navigate and Operate pallet, those settings are saved to your browsers local storage. That is scoped to a specific URL origin which considers the scheme, host, and port. If you're accessing a NiFi instance as the same origin, it should remember the docked state of each. That docked state will be retained for up to two days so as long as you're accessing your NiFi UI at least once every two days it should remember. If you're seeing differing behavior please file a JIRA so we can further investigate. Thanks Matt On Sat, Sep 21, 2024 at 11:09 AM Russell Bateman <r...@windofkeltia.com> wrote: > As others suggest UI extensions and other improvements, I have just a > few usability concerns. I find the UI tedious to use and would like to > suggest... > > * The ability to configure the two pallets to be collapsed when the UI > comes up, or remember how they were. > * An "undo" ability, perhaps of only the last /n/ accomplishments; for > me, just the very last change would be marvelous. > * The ability to turn off all the confirmation alerts. For example, > when emptying queues, a person who knows he or she was doing it on > purpose should not have to confirm that the queue was emptied, okay > thank you very much, but will just see the queue go to Queued: 0. > > These are primitive suggestions--I don't claim to be a UI or UX guy--I > have accumulated over more than 8 years of writing custom processors > and, somewhat less, as a user of the UI. The real users of the UI are a > "cousin" team and they would like to see these and more besides. > > Thanks for the Registry. Templates were a crucial need from the early > days when they appeared. Not to complain, Apache NiFi is an amazing, > rocking tool. > > Russ
