Skip to Content
avatar image
Michal Uhlir

SAPUI5 SuccessFactors extension running on SCP Cloud Foundry

Aug 15, 2018 at 08:48 PM | 210 Views

Dear SAP community,

I was able to create SAPUI5 extension of SuccessFactors and run it in Neo Environment without any problems based on the tutorials available on web. Blogs or help.sap.com documentation.

I would like to run this extension in Cloud Foundry Environment, but unfortunately I was not able to find any proper guide or tutorial. Based on this blog I was able to deploy and run the application, but it is not properly connected to SF oData service. Configuration on SCP Cloud Foundry side is following this documentation.

When I open deployed app, I am getting the error, that oData metadata cannot be loaded.

Thank you for any hints!

Michal

SAP Cloud Platform | SAP SuccessFactors Employee Central | OData | SAP Cloud Platform for the Cloud Foundry environment | SAPUI5 | SAPUI5 | cloud foundry | successfactors odata
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Michal Uhlir
    Jan 13 at 09:40 PM

    This question is solved and described in this blog post: https://blogs.sap.com/2019/01/13/extending-sap-successfactors-using-sapui5-and-scp-cloud-foundry-environment/

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Ivan Mirisola
    Aug 16, 2018 at 03:45 PM

    Hi Michal,

    Have you looked into the network tab on chrome developer tools to inspect which request is failing?

    Pleas post additional information so we can better help. There is a high hance that the OData metadata isn't loading because the OAuth mechanism failed before the odata was called.

    Regards,
    Ivan

    Add comment
    10|10000 characters needed characters exceeded

    • Ivan Mirisola Michal Uhlir
      Aug 22, 2018 at 03:30 PM

      Hi Michal,

      How have you created the access between your UI5 application and the OData service from SSF?

      Are you using the destination service defined on the cockpit or creating your own User Provided Service for this?

      I think the easiest way to accomplish this task is to create a destination with OAuth2SAMLBearerAssertion authentication type - and configure it to retrieve the authentication for you.

      Best Regards,
      Ivan