Expected Application Errors

These errors include all error conditions that are checked for and handled as part of normal application processing. This covers any errors that occur as a result of incorrect data that may be sent to an FTM application.

The pattern is similar in all cases:
  • The logic in an application flow tests for, and detects, an error.
  • The application flow creates an error entity that it associates with the object in error. This error entity is used to record the details of the error, both for logging purposes, and to provide the information that may be used to build an acknowledgment transaction.
  • The application flow raises an event that references the object in error and the error entity.
  • The FSM logic for the object in error, and any appropriate related objects, determines what further action should be taken and whether to move to a new state.
  • Such a new state may be denoted as an alert state if it is appropriate that operations should be made aware of the error.
  • Depending on system and customer setup, further interactions may be defined to react to the event in order to send a Customer Alert message, or to send a Negative Acknowledgment to the originator of the object in error.

This pattern ensures that the error details are recorded, the transactions affected are brought to a conclusion, and that all appropriate parties are notified. Similarly, if the error is detected in an input mapper, the mapper may set the mapping result to failure. The EndMapper subflow then raises E_MpInTxnMapFailure, instead of E_MpInTxnMapped, which can be handled in the FSM logic.