Troubleshooting

This section describes the troubleshooting tips that can help resolve common issues encountered when integrating your VBCS application with Oracle Fusion Field Service.

1. HTTP 403 Error (Forbidden): If you encounter a "403 Forbidden" error, it might indicate that your user account in Fusion does not have the necessary permissions. Ensure that the ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_INTEGRATION_SPECIALIST_JOB role is assigned to your Fusion user. You can check and assign this role in Fusion through Tools -> Security Console -> Users.
2. CORS Error: If you see a CORS (Cross-Origin Resource Sharing) error, the browser is preventing the VBCS application from making requests to the REST API due to security restrictions. Contact your Oracle Fusion Field Service administrator to verify the ORA_CORS_ORIGINS profile option code in Fusion: My Enterprise -> Setup and Maintenance → Tasks (visible in the Right Side of the screen) -> Search -> Manage Administrator Profile Values task -> Add full URL (including "https" prefix and without trailing slash) to Profile Value field. The value is a domain from which the plugin is loaded. For more information, see https://docs.oracle.com/en/cloud/saas/fusion-service/facoe/c_chat_configure_for_cors.html

   The domains that should be listed in the CORS policy field:

   1. for VBCS plugins - domain of VBCS application
   2. for standard plugins - plugins-1-{FS domain}, use environment name in the domain, for example, ofsc-******.test instead of alias for hosted plugins - plugins-0-{FS domain}, use environment name in the domain, for example, ofsc-******.test instead of alias
   3. for requests from browser's console - name of the domain where request is called