Symptom
We have an MDF object OnboardingCandidateInfo which is not role based permission secured in object definition level. We have exposed this as a restricted OdataV2 API. Although it is not role based permission secured, when this API is invoked by UI we get “No Permission!” error. Onboarding 1.0 custom card based on start-date solution uses OnboardingCandidateInfo API call.
Environment
SAP SuccessFactors Onboarding 1.0
Cause
Access to Non-Secured permission was missing for onboardees while loading custom cards in Onboarding 1.0 when the OnboardingCandidateInfo API gets invoked.
Resolution
Access to Non-Secured permission is needed if the object is not secured. Kindly provide this permission for onboardees so that the OnboardingCandidateInfo API call gets executed successfully which is required to access the custom cards.
Keywords
Custom cards, No permission, OnboardingCandidateInfo API , KBA , LOD-SF-OBD-API , Webservices & API's , Bug Filed