on 10-11-2023 9:16 AM
Hi,
We're using SAP Build Process Automation for setting up a new workflow.
We created also Custom UI's as described here:
- https://help.sap.com/docs/workflow-capability/workflow-cloud-foundry/creating-custom-task-ui
- https://help.sap.com/docs/build-process-automation/sap-build-process-automation/technical-informatio...
Now, we want to use odata services from the backend system in these custom UI's.
I already followed the blog (https://blogs.sap.com/2020/09/08/calling-external-api-in-custom-task-ui-of-workflow-in-cloud-foundry/) but still, we're facing issues when using the odata services (http 500 - Internal server error)
- Destination created in BTP Cockpit
- xs-app.json updated
{
"source": "^/S4HANA_Dev_Dest(.*)$",
"target": "$1",
"destination": "S4HANA_Development",
"authenticationType": "none",
"csrfProtection": false
},
- The steps for the mta file are a little bit confusing, as we're using the SAP Managed appRouter and so, we don't have the approuter as a module here...
- Manifest
"dataSources": {
"productDropdown": {
"uri": "S4HANA_Dev_Dest/sap/opu/odata/sap/ZAPI_SRV",
"type": "OData",
"settings": {
"annotations": [],
"localUri": "localService/metadata.xml",
"odataVersion": "2.0"
}
}
}
Our URL's of the odata calls are like (wich returns http 500): https://company.sap-process-automation.cfapps.eu10.hana.ondemand.com/appRouter.customui-0.0.1/S4HANA...
When using the app as a "standalone app" within the Launchpad Module, the destination is reachable and OKAY
Any thoughts?
Thx!
Apparently, the SBPA managed appRouter doesn't use the Connectivity Service.
So, no Destinations can be used in customUI apps currently.
issue addressed to SAP!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
77 | |
9 | |
8 | |
6 | |
6 | |
6 | |
6 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.