@Justee    First thing I would do is add a new Attribute on my FlowFile that specifies the year I'd be searching for in the lines contained within the content of that FlowFile. (optional) For example adding an attribute "year" with a value of "1995". In the routeText processor, I'd then be able to use NiFi Expression Language (NEL) in my java regular expression as supported by this processor component: ^\|(.*?)\|(.*?)\|${year}\|(.*?)$ The above java regular expression will match on lines that begin with a pipe "|" followed by a non greedy wildcard match of one or more character until the very next pipe "|", then again for field 2, then for field three I used NEL which resolves to "1995", and then finally i match via wildcard the remainder of the line. Of course you could simply put "1995" in place of "${year}" in the above regex. The routeText processor component configuration would look like this: The result would be two FlowFiles.  One FlowFile would be routed to the relationship "1995" (based on property name used) which would have content only containing lines with "1995".  The second FlowFile would route to the "unmatched" relationship and would contain all the non-matching lines ( you may to choose to just auto-terminate this relationship if you don't care about these lines). If you found these responses addressed your query, please take a moment to login and click on "Accept as Solution" below each response that helped you. Thank you, Matt   ... View more

@smartraman  This can also be accomplished through a different and more complex configuration of the ReplaceText processor: Using below input content example: { "TOT_NET_AMT" : "[\"55.00\"]", "H_OBJECT" : "File", "H_GROSS_AMNT" : "[\"55.00,58.00\"]", "TOT_TAX_AMT" : "[9.55]" }   I would set up the replaceText processor as follows: Instead of just searching for those character patterns and replacing them with nothing, I break entire input line-by-line in to a series of capture groups.  That way I can omit the capture groups matching the patterns you want removed ([ or [\" or \"] or ]) and then manipulate the capture group containing a possible comma separated list, so that only the last value in that list is returned. I used below java regular expression which results in 5 capture groups: (.*?)([\Q[\E]\\\"|[\Q[\E])(.*?)(\\\"[\Q]\E]|[\Q]\E])(.*?)$ I then used the following Replacement Value in which I used NiFi expression language against the 3rd capture group.  If that capture group does not contain any commas, the entire string is returned.   With example above and this configuration, you end up with the following new content: { "TOT_NET_AMT" : "55.00", "H_OBJECT" : "File", "H_GROSS_AMNT" : "58.00", "TOT_TAX_AMT" : "9.55" }   If you found this helped with your latest query, please take a moment to login and click on "Accept as Solution" below this response. Thank you, Matt       ... View more

@midee  @janis-ax is correct that this is not possible. "ONLY" sensitive attributes can be encrypted/masked.  Only component properties coded to as a sensitive property field would be able to decrypt an encrypted/masked value.  If setting policies to block specific users from being able to view the data on these components, you may want to look at other options for performing these endpoint authentication/authorization actions.  For example, with the NiFi endpoints you could use mutual TLS via certificates instead of token based authentication for accessing the endpoints.  This does not mean you need to stop using or un-configure the token based authentication methods for access to your secured NiFi. If the endpoint you are trying to reach is not NiFi, you may want to see what other options it may offer for authentication that are not token based. Hope this helped, Matt ... View more