on 08-28-2019 1:36 PM
Hi All,
Is there anyway to add http headers when calling rest services from workflow service call? I see this scp-workflow-service-task-headers thread for the same question.
Still the status remains same or anything new has beed added ?
I am calling googlesheet api from workflow with open connector to add new row after task has been approved. In order to call open connector url, i need to pass authorization header. Time being i am creating iflow in CPI to call open connector url and calling iflow from worklfow.
Regards,
Muni
Hi Muni,
setting HTTP headers is still not possible. It is on our roadmap, but I cannot tell you a concrete timeline.
In your case, I wonder why you try to use the Authentication header. Isn't the Google Sheets API accessible using OAuth2 Client Credentials?
See
https://developers.google.com/sheets/api/guides/authorizing
You could store the credentials in the destination used at the service task. That keeps the confidentiality of the API credentials and lets the workflow engine manage the authentication.
Regards,
Tobias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
I had a similar question about adding header parameters to the request - our requirement is to call an API which requires an api key value in the header. Is there any way to handle this form the WF service task?
Best regards,
MaryM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Christian,
setting custom header parameters feature is still on the roadmap, currently planned for Q1 2021, however this timeline could change, based on current priorities.
You have another option to trigger iRPA APIs though - you can add the trigger token as part of the payload, when you trigger the API:
{
“irpaTriggerToken” : <your token>,
…
}
Hope this helps?
Best regards,
Krassimir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A sample context could be something like this. Note the input and invocationContext properties. The input should match the iRPA bot's input (if any), and the invocation context is relevant when you want to pass the control back to workflow after the bot execution (achieved via intermediate message event in the workflow)
{
"irpaTriggerToken": "kabiudqiweuyqwe9734",
"invocationContext":{
"key": "1000010",
"workflowDefID": "capexapproval",
"messageDefID": "imtermediatemessageevent1"
},
"input": {
"requestID": "1000010",
"Title": "Build mobile apps",
"TotalCost": 10000,
"Type": "Software",
"Objective": "Buildling new mobile apps",
"CAPEX": 10000,
"OPEX": 2000,
"ROI": 5,
"IRR": 5,
"Country": "Germany",
"Currency": "EUR",
"Division": "BPM"
}
}
In fact, this feature was delivered today. Please refer to the "What's New".
and the feature documentation
at
according to the documentation, in the properties of the service task there should be a tab header, but that tab does not appear, an image of the properties follows
Hi Christian,
You can also call the API trigger of SAP intelligent RPA by providing the token in the irpaTriggerToken property of the trigger payload. This property should be defined on the top level of the payload, next to the invocationContext and input properties.
Best Regards,
Anja
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello tobias.breyer,
is there any update on this feature? I'd like to connect my workflow service task with SAP iRPA API Trigger. This trigger requires a the property "irpa-trigger-token" to be set in the header of the request. Unfortunately I cannot set it. Or is there another way to connect to SAP iRPA via API Business Hub?
Regards,
Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
75 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.