API operations the request information from, or submit changes to, the Automation Engine are performing using XMLRequest, or subclasses thereof. The typical procedure looks something like this:
In this way, your app can be designed to handle warnings, errors, or other messages returned by the Automation Engine.
We had been operating under the assumption that the getMessageBox method would reliably tell us the overall final result of any XMLRequest operation. However, we had recently seen cases wherein getMessageBox returned null even though errors had occurred.
This morning CA Development informed me that three XMLRequest classes do not return all errors via getMessageBox. Instead, these three classes require additonal case-specific error handling:
We are even seeing getExportException()is returning null when an Export has failed. Have you run into this as well? I'm gathering info to get a case open with CA. We are currently on 12.0.3 HF4.
Yup, ExportObject & ImportObject behave differently than all other similar classes. Each has its own special method for determining whether an error (or multiple errors) occurred. You cannot rely on getMessageBox().
For most other XMLRequest operations, there is the getAllMessageBoxes method. Using this method, one should in principle be able to get a list of all of the errors resulting from the request.