This is the flow I'm working on, I'm using the UpdateAttribute to enter the path of a Windows network directory to get the .PDF files, but it throws the error below.   I must be doing something wrong or missing some other processor.       UpdateAttribute ... View more

@Matt    thank you very much for all the answer.   We are still insisting on getting the Base64 field from Oracle because the PDF is already there. I'm using the Base64EncodeContent process to decode the Base64 field coming from Oracle.   I was able to send a file to the E-mail with PDF format, but it still has an error when opening the PDF file sent in the E-mail.   It seems to me that Nifi cannot say that the code it is decoding from the Base64 field that is coming from Oracle. Sorry for the lack of knowledge on the subject.       ExecuteSQL   UpdateAttribute   Base64EncodeContent   PutEmail    PutEmail    ... View more

@MattWho    Sorry for the lack of clarity in the question. In short, I need to send an attachment by PDF, but I can't select the file that I already have saved in PDF in a directory, because within that directory there are several PDFs from different buyers and the E-mail is sent one to each buyer by the PDF be different for each one.   The PDF is generated at a different time within my ERP system.   Is there a way for Nifi to understand that the Flow of that buyer that is coming is from a certain PDF within the directory by some identification? I do this by which Nifi processor? To bring the buyer I execute a QUERY in Oracle by the ExecuteSQL processor returning the buyer's ID.   A second attempt to send the attachment would be, in this QUERY in ExecuteSQL I can bring together a PDF field that is as CLOB type already saved in the database.   In this second option, can I send the information through the Message property of PutEmail? In this property, can I join the Email body and attachment? Which one would I have to pass in the PutEmail's Content Type property?   If you need any more information, I'm available. ... View more

@steven-matison  thank you so much. ... View more

@steven-matison This is exactly what I needed...   before Nifi version 1.16 this was not possible with Failure Relationships?   ... View more

@MattWho,   Good afternoon.   I changed my flow to make a counter by the processor "RouteOnAttribute 1.12.1" so every time I have a record to be sent to the API and have a return to store in Oracle, I do the LOOP through RouteOnAttribut. Thus sending one FlowFile at a time to the PROCEDURE call in Oracle by "ExecuteSQL 1.12.1"   But what is happening at the moment is that from the second time it goes through the LOOP, it seems to me that the Flow to get the attributes "CODIGO" and "JSON_ORIGINAL" is not passing the values ​​that I requested in the processor "EvaluateJsonPath 1.12.1" passing the parameters as null.   Do you have any idea what may be happening in this second flow passage within the LOOP?     This is the JSON ORIGINAL of the second stream that I must send to Oracle =  This is OK with the CODE attribute as you can check.   This is Split Configure Processor =     This is EvaluateJsonPath 1.12.1 Configure Processor =   This is MergeContent 1.12.1 Configure Processor =     This is ExecuteSQL 1.12.1 Configure Processor =   ... View more