My Oracle Support Banner

Error Callback Is Not Invoked When The AJAX Request Fails For An Asynchronous Business Service Call. (Doc ID 2352080.1)

Last updated on JANUARY 23, 2018

Applies to:

Siebel CRM - Version 16.11 [IP2016] and later
Information in this document applies to any platform.

Symptoms

On : 16.11 [IP2016] version, Siebel VB / eScript / COM

ACTUAL BEHAVIOR
---------------
Error callback is not invoked when the AJAX request fails for an asynchronous business service call.



EXPECTED BEHAVIOR
-----------------------
Error callback should be invoked when the AJAX request fails for an asynchronous business service call.

STEPS
-----------------------
We are invoking business service methods asynchronously using Open UI client-side JavaScript. The Siebel Bookshelf reference indicates that you can define a success callback (cb) and an error callback (errcb).

When we call the business service successfully, the success callback is invoked as expected. However, when the AJAX call fails (i.e., returns a 4xx/5xx status code), the error callback is not invoked. The error status code and message are logged to the console, but our custom error callback is never called.
 
Example:
SiebelApp.S_App.GetService(serviceName).InvokeMethod(methodName, inputPropertySet, {
  async: true,
  cb: () => {
  alert('success!'); // called when the business service returns successfully
  },
  errcb: () => {
  alert('ajax error!'); // is NOT called when the AJAX call fails
  }
});

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


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