REST API: Exposed Workflow As 'REST API' Does Not Reflect Immediately Without Restarting Task And Receiving An Error: {"ERROR": "Access to Resource xyz of type BUS_PROC is denied(SBL-DAT-00825)"} (Doc ID 3038370.1)

Last updated on JULY 31, 2024

Applies to:

Symptoms

When the workflow (added in 'Business Process Access' view screen) exposed as a Rest API and tested, the results do not appear immediately using the same task session, resulting in the following error:

ERROR:
---------

The issue can be replicated by following the steps outlined below with the inbound Rest API functionality.

• Launch the Siebel tool/Web tool and create a new workspace.
  
  
• Create a custom workflow (CustomWF) or select a vanilla WF to expose as an inbound Rest API, then deliver the changes to the MAIN workspace.
  
  
• Next, login to the Siebel application.
  
  
• Navigate to the 'Site Map' --> 'Administration - Application' --> 'Business Process Access' view.
  
  
• Add the above-mentioned (point #2) 'CustomWF' / vanilla workflow and assign the responsibility.
  
  
• Click the 'Clear Cache' button.
  
  
• Next, use the Postman tool, invoke the workflow via the rest inbound functionality, as described below in the in the URI:

             https://<host name>:port/Siebel/v1.0/workflow/CustomWF

• Then the output displays the following error:

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.