Stateless API Wrapper
- Last UpdatedNov 06, 2025
- 1 minute read
You must use the MES Stateless API wrapper provided in the script function library to access Stateless API functionality in System Platform scripts. The System Platform environment does not support Null data types. Even with a try/catch block, the app engine can still hang.
The API wrapper class names start with 'aa' and their functionality corresponds with the equivalent Client API functions.
|
Stateless API Function |
Stateless API Wrapper Class Name |
|---|---|
|
FactMES.API.Core.[Class] |
aaMES.Core.aa[Class] |
|
FactMES.API.EnProd.[Class] |
aaMES.EnProd.aa[Class] |
|
FactMES.API.Labor.[Class] |
aaMES.Labor.aa[Class] |
|
FactMES.API.Prod.[Class] |
aaMES.Prod.aa[Class] |
| FactMES.API.Quality.[Class] | aaMES.Quality.aa[Class] |
|
FactMES.API.Util.[Class] |
aaMES.Util.aa[Class] |
For example:
The definition of StartSession call found in the FactMES.API.Core namespace is defined as:
Session.StartSession(clientType, sessionId);
To use the wrapped call for StartSession, you add aaMES.Core.aa to the call:
aaMES.Core.aaSession.StartSession(clientType, sessionId);
System Platform scripting can access the Stateless API wrapper from:
-
Scripts tab of any automation object.
-
Any script window within System Platform symbols, such as, the symbol script, the event script, or action scripts for individual elements on the canvas.