This blog is primarily targeted to those facing an issue where you have subscribed both SAP Build Process Automation and SAP Build Work Zone, standard edition but can't see / add / enable My Inbox App into your SAP Build Work Zone portal.
This issue happened when users do manual subscription of SAP Build Process Automation service and SAP Build Work Zone service; some extra configuration is required when you want to use SAP Build Work Zone with SAP Build Process Automation.
Unfortunately, if you're evaluating both SAP Build Process Automation and SAP Build Work Zone service on SAP BTP Trial landscape, there's no guided booster available for these services on Trial so you will likely encounter this issue.
When the guided booster is made available in your BTP global account, please use it, as it will make your life much easier.
This step is also documented in official help documentation of SAP Build Process Automation here.
Navigate to Services > Service Marketplace > Create a new service instance for SAP Build Process Automation.
Select `standard` plan.
Once a service instance created successfully, next step is to create a service key. You will see a new entry under `Service Keys` section.
You will see this pop-up, when you click your service key.
Do note down the following field and its value:
Navigate to Connectivity > Destinations > Create a new destination.
Enter following details:
Field | Value |
Name | sap_process_automation_service |
Type | HTTP |
Proxy Type | Internet |
Authentication | OAuth2ClientCredentials |
URL | <”endpoints”.”api”> |
Client ID | <"uaa"."clientid”> |
Client Secret | <"uaa"."clientsecret”> |
Token Service URL | <"uaa"."url">/oauth/token |
Also enter below as additional properties:
Field | Value |
endpoints | endpoints (copy the whole JSON structure including ‘{‘ and ‘}’) Example: |
html5-apps-repo | html5-apps-repo (copy the whole JSON structure including ‘{‘ and ‘}’) Example: {"app_host_id":"xxxxxxxx-e05b-4654-a999-30de519f64b4,ad4b900b-4bf1-4965-a6a6-d71ce7fc5300,9cd6ff5e-f33f-459e-90de-35e17719e6e1,3be0da62-2508-4691-8794-abcdfg"} |
saasregistryenabled | saasregistryenabled copied from the service key |
sap.cloud.service | sap.cloud.service copied from the service key |
sap.cloud.service.alias | sap.cloud.service.alias copied from the service key |
The entry should looked like below:
If you want a quick way, just modify below configuration (update the important fields with the values from your service key) and save it as `spba_destination.txt` and import into Destinations:
#clientSecret=<< Existing password/certificate removed on export >>
#
#Tue Jul 09 02:57:54 UTC 2024
Type=HTTP
clientId=sb-xxxxcxxx-6df1-477c-95f4-abcdefgh2b97\!abc123|xsuaa\!abc123
saasregistryenabled=true
endpoints={"api"\:"https\://spa-api-gateway-bpi-us-prod.cfapps.us10.hana.ondemand.com"}
sap.cloud.service.alias=spa
Authentication=OAuth2ClientCredentials
Name=sap_process_automation_service
html5-apps-repo={"app_host_id"\:"xxxxxxxx-e05b-4654-a999-30de519f64b4,ad4b900b-4bf1-4965-a6a6-d71ce7fc5300,9cd6ff5e-f33f-459e-90de-35e17719e6e1,3be0da62-2508-4691-8794-abcdfg"}
tokenServiceURL=https\://sap-build-demo-xxxxxxxx.authentication.us10.hana.ondemand.com/oauth/token
ProxyType=Internet
URL=https\://spa-api-gateway-bpi-us-prod.cfapps.us10.hana.ondemand.com
tokenServiceURLType=Dedicated
sap.cloud.service=com.sap.spa.processautomation
CEP.EnableCsrfProtection=true
Once you have done all steps above, do a quick a `Check Connection` test, and it should show you `401: Unauthorized` (this is a correct response):
When you launch your SAP Build Work Zone's site manager, you should be able to see My Inbox App and other HTML5 Apps that comes with SAP Build Process Automation in the `Content Explorer`.
If My Inbox App is not visible there yet, navigate to `Content Manager` and do a content refresh first.
SAP Build SAP Build Process Automation SAP Build Work Zone, standard edition