Using the Stateless API

Using Stateless API scripts in System Platform scripting follows the same rules and conventions as required when creating objects in the System Platform.

Note: It is important to use the Stateless API wrapper (aaMES.aaSLIB) within System Platform IDE instead of the DLLs. Even with the try catch code in System Platform scripting, the direct use of the MES DLLs can still fail with Nullable and DB datatypes.

The topics in this section explain how to use several pre-built API scripts. These scripts illustrate the basic coding required to use the full range of API functions.

The stateless API is designed for use within System Platform object scripting and not System Platform graphics. The API can be used in graphics, but there are often limitations with datatypes in System Platform graphics.

When using MES API scripts, there can be significant time delays between making the call and receiving a response back from the MES Database.  The recommendation is to place MES API calls within an asynchronous script so as not to impact the System Platform engine executing the script.

The MES API wrapper makes use of a result object to capture any error messages from the API call.  All calls should include a check on the aaMES.Result object to determine if the call was successful or not.