An error in Event Processing can result for a number of reasons:
- Unable to Parse Event - this will result in a Parser Exception
- Object Selector Failure - this will result in a Database Exception
- Action - this will result in either a Parser Exception or a Database
Exception.
All of these exceptions will be caught and reported as an UnexpectedError
event - E_UnexpectedError. This event will contain key Environment
data (FSM transition info) and ExceptionList data. The Unexpected
Error events are stored in the database and can be searched for and
viewed in the FTM OAC. The data associated with the event is in XML
format and contains all the available data and context associated
with the error.
Figure 1. XML for an Event
