When Fault Code Does Not Match onFault Code
In a business process, a fault can occur in a complex activity that is not handled by an onFault element at that level of the process. When the fault code does not match the onFault element at a level, Sterling B2B Integrator begins to search for the correct onFault element.
When no code attribute exists and no match to a defined attribute exists for an onFault element at a level, Sterling B2B Integrator moves to a general onFault (no code attribute) element. If Sterling B2B Integrator does not find a fault code, Sterling B2B Integrator halts the process.
In the credit card example, the Verify Credit Card activity results in a NetworkDown fault because Sterling B2B Integrator first looked at the onFault elements associated with that activity. Sterling B2B Integrator found only one onFault element in this activity and the code specified was not NetworkDown. Sterling B2B Integrator then looked for the correct onFault element in the next activity up in the process. Eventually, Sterling B2B Integrator found a general onFault element for which no code attribute exists at the highest level of the process. When the fault handling activities finish, Sterling B2B Integrator runs the next activity in the process until no other activities exist in the process.