Thanks @SAMSAL  it worked for me... ... View more

@SAMSAL This looks like a plausible solution. Let me try it out.  ... View more

@Diga  In a scenario like this, the first thing to ask yourself is "How would I do this outside of NiFi?".  If you were to use curl from command line, how would you handle authentication with the Polarion ALM rest-api endpoints?  The answer there would help with how you would handle it within NiFi and assist in getting a better response in the community.  @SAMSAL provided some great suggestions of possible methods. Matt ... View more

@kanchanDesai Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  Thanks. ... View more

thank you so much! i'm moving forward again! ... View more

hi @Ytch , To use the PutDatabaseRecord you need to have the column names defined in whatever input format you have (CSV, Json....etc.) and the column name should match what is in the DB table ( see also the "Translate Field Option" if not exactly the same). If you know the column order in the CSV file you can add a header using the ReplaceText processor as described here: https://community.cloudera.com/t5/Support-Questions/How-to-add-customer-headers-to-csv-file-in-NIFI/m-p/285457   If you find this is helpful please accept solution. Thanks ... View more

Hi @CommanderLaus , If you do anything manually with the processor you are trying to change its Running State through the API, then yes the revision will be updated. In my case what I do is basically the first API InvokeHttp is to get the latest revision using the following GET API:   https://localhost:8443/nifi-api/processors/${pipeline.start.processor.id}   This will give the following response where you can parse the latest "version" value using something like EvaluateJsonPath processor and store the value in an attribute:   { "revision": { "clientId": "value", "version": 0, "lastModifier": "value" }, "id": "value", "uri": "value", "position": {…}, "permissions": {…}, "bulletins": [{…}], "disconnectedNodeAcknowledged": true, "component": {…}, "inputRequirement": "value", "status": {…}, "operatePermissions": {…} }   Then use extracted version attribute to build the next API post Body , for example in my case I use ReplaceText processor to generate the post body :   { "revision": { "clientId": "${pipeline.start.processor.id}", "version": ${processorVersion} }, "state": "...", "disconnectedNodeAcknowledged": true }   Hope that helps.       ... View more

Thanks @SAMSAL  for recommending @MattWho  ... View more

@saraDdeveloper  If you are still experiencing the issue, can you provide the information @SAMSAL has requested? Thanks. ... View more

@SAMSAL my bad !!! I start to be old i need better glasses 🙂 You are right it works fantastically !!! THANKS!!!!!  ... View more