Error on REST call from Custom Event Action

Hi @jhooperyan,

Below post might be helpful. Check the parameters/variables you are using with the scenarios described here.

To provide more detail - we are using an event action to make a REST call.  And this error started when I added security to the API being called, which added a header parameter.  The error started when we added a header parameter that includes a security certificate.  When I have no header parameters - this works.  With the Header parameter - I get the error.  Since this is all firing through a custom event, the variable error is happening somewhere in IFS code.  I can save my parameter value in the Event Action, it’s just failing somewhere in the IFS internal code.

Hi @jhooperyan,

I understand now.  You are exceeding the field length allowed for the header based on how the event processes rest calls.  You will need to switch to PLSQL and code it in an anonymous block.  The following is a snippet from the IFS technical documentation that you should take a look at for reference, but it is representative of how something like that would look:

url := PLSQLAP_DOCUMENT_API.New_Document('url_params');
PLSQLAP_DOCUMENT_API.Add_Attribute(url,'parameter1','/myResource');

Query_params := PLSQLAP_DOCUMENT_API.New_Document('QUERY_PARAMETERS');
PLSQLAP_DOCUMENT_API.Add_Attribute(Query_params,'value1', 'abc');
PLSQLAP_DOCUMENT_API.Add_Attribute(Query_params,'value2', 'xyz');

plsql_rest_sender_API.Call_Rest_EndPoint_Empty_Body2(
rest_service_ =>'MY_REST_SERVICE',
url_params_ => url,
callback_func_ =>'callback_fn',
http_method_ => 'GET',
http_req_headers_ =>'Content-Type:application/json',
query_parameters_ => Query_params);

The plsql_reset_sender_api has multiple methods.  The ones that end with Empty_Body are for ‘get’ requests. where you are only submitting things in the URL.  If you have a document, then you will want to use one of the other methods, but the concept is the same.  Also, this snippet only has some of the parameters listed, there are many others for error_callback, header parameters, etc.  You will then setup an address and a routing rule in connect that you configure for your endpoint.  The header parameter you are adding will then be added to the endpoint, but the value for the certificate not be entered there.  Instead you will use a placeholder variable that look like:

The additional header parameters are on the address screen.  The code will then be in your custom event.  In this example you could set header1 to Ocp-Apim-Subscription-Key and the value2 to your certificate (but remove the = in that case).  Or what I would do is just replace that line in the additional header parameters screen with:

Ocp-Apim-Subscription-Key:{cert1}

Or something like that. 

Keep in mind this is to model the solution like you have it, but you may want to look at the other setup options in the connect configuration to see if you can utilize the built in certificate capability.  This way you are not putting your certificate in your code.