rfellows commented on a change in pull request #3725: NIFI-6558 Added Parameters to User Guide and Sys Admin Guide URL: https://github.com/apache/nifi/pull/3725#discussion_r324753461
########## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ########## @@ -729,23 +901,30 @@ NiFi properties have resolution precedence of which you should be aware when cre * Processor-specific attributes * FlowFile properties * FlowFile attributes -* From variable registry: +* From Variable Registry: ** User defined properties (custom properties) ** System properties ** Operating System environment variables When you are creating custom properties, ensure that each custom property contains a distinct property value, so that it is not overridden by existing environment properties, system properties, or FlowFile attributes. -There are two ways to use and manage custom properties: +There are two ways to use and manage custom properties with Expression Language: + +- *Variables*: Variables are created and configured within the NiFi UI. They can be used in any field that supports Expression Language. Variables cannot be used for sensitive properties. NiFi automatically picks up new or modified variables. Variables are defined at the Process Group level, as a result, the access policies for viewing and changing variables are derived from the access policies of the Process Group. See <<Variables>> for more information. Review comment: General question: If Variables are one of the 2 ways to do this, and they are going away, does that mean that in the future only Custom Properties File will be the only way? Or are parameters a 3rd way? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
