I'm doing something like this for an ICIMS interface using the WebRun node to execute my API calls. Processing the data you receive back depends on the format of that data. I'm getting JSON formatted data but you might get XML. If you're getting XML then you'll need to get examples and build a schema (if the vendor doesn't provide it) for parsing the XML data.

We attempted a REST API using the Webrun node to connect with the Nuvia API. We encountered an issue with how they handle the secure connection within the API that Lawson nor our experts could resolve. We had to switch to a flat file trigger of the flow instead. The ION API connections will allow it but we do not have the enterprise product from Lawson yet.

Ethan,

We use REST API with a couple of our vendors. We are currently hosted and using IPD version 11.0.10. Some things I ran into during my trials and tribulations on making our interfaces work that may be helpful:

• It shouldn’t be an issue now as most everyone is using the correct TLS version, but make sure your version is allowed with the vendor

• Make sure the IP of your Landmark or other related servers are allowed through the vendors’ firewall. I know it might sound like a basic item, but you would be surprised how many times it is not set up.

• Like David mentioned, if your return is XML make sure to use the correct/good schema (very important). If your return is JSON, you can use the JSON parser nodes in IPD. Once that is done, you can use the notation on the output from the node to find the information you need pretty easily (examples are in the good old PDF IPD user guide).

• Check to see if there is a limit of how many calls per day or hour are allowed by your vendor. Most of the time, these limits are pretty high and you shouldn’t need to worry, but if you are doing some initial large updates you might need to put in a Wait node within a read loop so you don’t hit a limit.

• Depending on the vendor and/or application you are working with, if you are using JSON sometimes you will not get back a “blank” field if there isn’t any data. This can be frustrating while you are testing and building because you will think something is wrong. If you are lucky enough to have a test/dev copy of the vendor’s data, the best way is to put something in every field so you can see what comes through the API.

• Really check or get the specs from the vendor on the data fields you will be importing or pushing in to the PA52. Most of your development time will be spent on formatting. I ran into issues where the vendor’s fields allowed for more data then the fields I had to put into Infor Lawson. You will need to encounter for that and come up with a plan on what to do with the extra data.

• Another one I found out the hard way is there were some fields on the online forms with the vendor application that did not have any data validation checks (i.e. only allow numerical digits in a number field, phone number formatting, etc.). This is an unfortunately reality, but will make for more overhead on your development design for sure.

Best of luck to you and I hope you have a great tech resource with your vendor. That will make a huge difference when you are troubleshooting issues.