Here’s an example of what I did with a few changes, hope it helps…Some of the changes I made: Use XML of REST call for Json string, Add Text Accept to Header, use parameter of rest api in routing rule context based conditions, parameter is set in code. Any errors should show up in the application message screen in IFS. Also, Call_Rest_EndPoint2 was the only one I could get to work with the parameters I had available.Create Routing Address: In Additional Header Paramters:Accept= text/html, application/xml;q=0.9, */*;q=0.8The user ID and Password defined here will be used, it is not necessary to code. Create Routing Rule (Outbound) In Destination Address place the Address you created in #1 Above. In Content based conditions use a parameterized rest:https://companyname.com:port/int/ifsapplications/projection/v1/CSalesPart.svc/{parameter1} In code, you will replace parameter1 with the Method Call of the API. Write your PL/SQL Code, you can put your JSON in the field called XML. It’s misl
Sorry I got back so late, been busy. I agree with Luca’s response also you can create a server based API that calls the IFS Rest, instead of the client going directly to the IFS REST call, that’s what we ended up doing. It’s a security issue when a browser directly calls a REST API from IFS I believe. In short, If you create your own API on the same server that calls the IFS API it will also solve the problem.
I think we solved it on our own. It’s not really an IFS question.
On a related question...is it possible for an outside “machine” to enter these analysis data points in IFS rather than manually entering them?
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.