Member since
12-27-2023
2
Posts
0
Kudos Received
0
Solutions
12-27-2023
09:38 PM
Okay, Let me explain the whole scenario. The following are the steps to build job descriptions using the Job Profile Builder. Step 1 => create an idp token and its curl is as below curl --location '----- URL -----' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data 'client_id=----CLIENT_ID----&token_url=----TOKEN_URL----&user_id=----USER_ID----&private_key=----PRIVATE_KEY----=' and its output => kmf0P2sW00eJnHS9gQ1bF9vohjG4N4X9QgJ2rbsZ3H4HlvvSiLV8HmbVxoHFYR8CbYHq92cWFRzam4zJkBYI6CkA0cNtmkUzcGza1I07zT2zwcjBnUDl9nZkaQeUHjhwfaXjKaZnzh0zQnZiYmeP6OcWPCmQWjkG7aFwzsC8N= Step 2 => create an access token curl --location '----- URL -----' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'client_id=----CLIENT_ID----' \ --data-urlencode 'grant_type=urn:----GRANT_TYPE----' \ --data-urlencode 'company_id=----COMPANT_ID----' \ --data-urlencode 'new_token=true' \ --data-urlencode 'assertion=kmf0P2sW00eJnHS9gQ1bF9vohjG4N4X9QgJ2rbsZ3H4HlvvSiLV8HmbVxoHFYR8CbYHq92cWFRzam4zJkBYI6CkA0cNtmkUzcGza1I07zT2zwcjBnUDl9nZkaQeUHjhwfaXjKaZnzh0zQnZiYmeP6OcWPCmQWjkG7aFwzsC8N=' Step 3 => Create a Family and Role (post api) Step 4 => Assign a Job Code to the Role (post api) Step 5 => Create skills (post api) Step 6 => Map Skills to the Role (post api) Step 7 => Create a Job Profile Template (JobDescTemplate) (post api) Step 8 => Map the Job Profile Template with Job Families (JDTemplateFamilyMapping) (post api) Step 9 => Create a Job Code (post api) Step 10 => Create a Position and assign the Job (post api) Step 11 => Create a Job Profile (post api) From step 1 to step 11, those are POST requests and every POST request, I have to request pass body too. So I have to use InvokeHTTP processor.. In simpler terms, sometimes I might use information from the previous step as input for the next step. For example, if I receive data in step 3 that includes a "family_id," I may want to use that specific family_id in step 4. This means that what happens in step 4 depends on what happened in step 3. Now my problem is that I'm not able to add body inside InvokeHTTP processsor for POST request. NOTE : my Apache NiFi version is => nifi-2.0.0-M1
... View more
12-27-2023
05:17 AM
Hi everyone, I'm currently encountering an issue related to passing request bodies in my workflow. Here's a breakdown of the situation: In my workflow, I have a total of 9 processors, all of which are InvokeHTTP Processors utilizing post requests. For each post request, I need to include a request body. The challenge lies in figuring out how to effectively pass the body using the InvokeHTTP processor. Presently, I am unable to accomplish this by utilizing the InvokeHTTP processor directly. We've attempted using GenerateFlowFile to pass the body, but it cannot be seamlessly integrated into the workflow. Specifically, I am unable to insert GenerateFlowFile between Processor 3 and Processor 4, for example. One potential solution we've considered is creating individual GenerateFlowFile instances for each processor outside the workflow. However, this approach introduces complications, especially when one processor is dependent on the output of a previous processor. For instance, if Processor 5 relies on the output of Processor 4, I'd need to introduce yet another processor. I'm reaching out to the community for insights and suggestions on how to efficiently handle passing request bodies in this scenario. Any advice or alternative approaches would be greatly appreciated. Thank you!
... View more
Labels:
- Labels:
-
Apache NiFi