Error Policies (Magic xpi 4.13)
If an error handling flow does not exist, or when an error handling flow handles the error and updates the C.sys.ErrorCode and the C.sys.LastErrorComponentType variables in the last step of the error handling flow, Magic xpi looks for an error policy in the flow that raised the error.
The error code that you update should belong to the component code defined in the C.sys.LastErrorComponentType variable. If the error does not belong to the component, a different error will be thrown - Error 24 of the General error group: Error Code [code number] does not exist for the selected component.
The error policy is defined in the Error Policies repository. You access this by double-clicking Error Policies under the relevant flow.
In this screen, you can select the error policy (Abort, Ignore, Restart Flow, Retry, or Jump) for a specific error number or range of error numbers.
You define the error policy per flow. For example, if you define the error policy for email in Flow 1 to Abort, the error policy for the same error in Flow 2 can be Ignore.
By clicking the 
button in the From or To columns, the Error Repository dialog box is displayed. Here, you can see all of the error codes built in to the Magic xpi components. If you develop your own components, you should add the errors to this list.
You add errors to Magic xpi as follows:
-
From the Solution Explorer's Repositories section, select Errors. The Errors Repository opens.
-
From the Components drop-down list at the top of the repository, select User Error.
-
Click Add.
In addition, for each error line defined, you can specify that an email notification will be sent to the administrator recipient. (The email address is set in the Send Error Email To property in the Project Properties dialog box.)
Error Policy Options
