Skip to main content
Solved

IFS Connect (Apps10 Upd13) - REST sender - response code 404 not processed

  • April 29, 2022
  • 1 reply
  • 345 views

DrJeffreyWhite
Do Gooder (Partner)
Forum|alt.badge.img+4

When calling:

 

Plsql_Rest_Sender_API.Call_Rest_EndPoint_Empty_Body(
                                                             rest_service_ =>'search',
                                                             url_params_ => url_params_,
                                                             callback_func_ => 'my_util_api.my_callback_proc’
                                                             http_method_ => 'GET',
                                                             sender_           => 'CONNECT',
                                                             receiver_         => 'MY_RECEIVER’',
                                                             fail_notify_         => TRUE,
                                                             failed_callback_fun_ => 'my_util_api.rest_error',
                                                             accepted_res_codes_  => '200,404');

 

I get ‘No output from address line in previous chain link; cannot proceed.’

 

I originally tried this call without accepted_res_codes as I wanted it to callback rest_error on 404, but then attempted with the accepted_res_codes to see if that would work.  It works perfectly when the response code is 200 just not 404.

 

Any ideas on what I am doing wrong?

Best answer by DrJeffreyWhite

I figured this out:

 

The failed callback creates a background job with argument type ‘Normal Parameter’. As such, the callback procedure must contain the correct parameter names, which does not seem to be anywhere in the documentation.

 

The correct format for the fail callback procedure is:

 

PROCEDURE my_fail_callback(error_text_ IN VARCHAR2, app_message_id_ IN VARCHAR2)

View original
Did this topic help you find an answer to your question?

1 reply

DrJeffreyWhite
Do Gooder (Partner)
Forum|alt.badge.img+4
  • Author
  • Do Gooder (Partner)
  • 10 replies
  • Answer
  • May 1, 2022

I figured this out:

 

The failed callback creates a background job with argument type ‘Normal Parameter’. As such, the callback procedure must contain the correct parameter names, which does not seem to be anywhere in the documentation.

 

The correct format for the fail callback procedure is:

 

PROCEDURE my_fail_callback(error_text_ IN VARCHAR2, app_message_id_ IN VARCHAR2)


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings