Thanks Paul. 

Bugs and feature requests can be submitted here [1] which will ensure they are seen by the entire team/community. The most helpful reports include screenshots when applicable, current system description, and potential use cases or unit tests to verify issue resolution. 

Very quickly, you can accomplish a “non-edit mode” by assigning “ROLE_MONITOR” to a user in the authorized-users.xml configuration file, but currently a feature whereby a single user can switch back and forth between those two modes instantaneously does not exist. Can you describe the use case where you see this being valuable? Are you having trouble and accidentally modifying items on the canvas?


Andy LoPresto
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Mar 22, 2016, at 4:55 PM, Paul Nahay <> wrote:

I can tell you a list of things I think need to be improved in NiFi. The most important is having two “modes” that one is always in, an “edit mode”, which is basically what you have 100% of the time now, and a “non-edit mode”, where the user cannot move things (inadvertently) around on the canvas.
Oh, and you desperately need an “undo”.
From: Andy LoPresto [] 
Sent: Tuesday, March 22, 2016 7:51 PM
To:; Paul Nahay
Cc: Jonathan Wood
Subject: Re: Errors in your Documentation
Thanks Paul. We always welcome feedback that helps us improve the product and documentation. I can’t promise those documentation fixes will be released in 0.6.0 but we will try to get them out as soon as possible. 
Andy LoPresto
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
On Mar 22, 2016, at 5:52 AM, Paul Nahay <> wrote:
Description: The isEmpty function returns true if the Subject is null or contains only white-space (new line, carriage return, space, tab), false otherwise.

This logically implies that isEmpty returns FALSE if the Subject contains NO CHARACTERS AT ALL (not even white-space). This makes no sense at all.

Description: Checks to see if any of the given attributes, match the given condition.

Hopefully you actually mean "all", not "any".

What's funny here is that THESE TWO functions were the ones I initially needed, and your documentation has errors for BOTH of them. I'll expect then to find more errors in your documentation, and will report them to you as I find them. 

Feedback confirming the errors will be appreciated.

Paul Nahay