Error Management (Magic xpi 3.x)

The error behavior definition is a crucial definition in your integration project. The more you can identify error situations, and define automatic routines to handle them, the more robust and productive your project will be.

Now you need to go back to your business process and consider potential error situations. For example, if the first step is receiving an XML file from the portal, then potential errors can include:

• Unidentified data in the file

• XML file does not match the defined schema

• XML file does not include default data settings

• Mandatory data is missing

Every error situation should go through two-phase definitions:

• Error detection – Define the business rules upon which error situations will be declared.

• Error handling – What to do in case of an error situation.

Magic xpi’s error management mechanism includes:

• Error variables

• Error behavior on step or flow

• Error and Exception flows

• Abort Flow Service – This service can cause a Flow Restart or cause the Error Policy to take place based on the defined error code.

You can find detailed information about the error management mechanism in the Error Handling in Magic xpi concept paper in the Magic xpi Help.