BO Algorithm Execution Summary
This table highlights the processing steps that occur when adding or changing a record that is governed by a business object.
| Invoke BO | |
| Event | Comments | 
| 
 BO Pre-processing algorithms executed  | 
 These algorithms are only executed when Invoke BO is used. The business object in the Invoke BO is the one whose rules are executed.  | 
| MO Processing | |
| Event | Comments | 
| 
 Determine if status has changed.  | 
 The system keeps a note of the new status value but initially proceeds with the old value.  | 
| 
 MO Processing.  | 
 Standard MO processing, including MO validation is executed.  | 
| 
 Determine BO algorithm executed.  | 
 The MO level algorithm is executed to determine the identifying BO.  | 
| 
 BO Validation algorithms executed.  | 
|
| 
 State transition rules are performed if the status has changed.  | 
 BO Status Exit algorithms for the “old” status executed.  | 
| 
 Status updated to the new value.  | 
|
| 
 BO Status Enter algorithms for the “new” status executed.  | 
|
| 
 If no error — MO Transition algorithms are executed. Fastpath:  
Refer to State Transitions are Audited for more information.  | 
|
| 
 If error and there are “save points” the MO Transition Error algorithms are executed. Fastpath:  
Refer to Keeping An Entity In Its Last Successful State for more information. Otherwise, the error is reported.  | 
|
| 
 BO Status Monitor algorithms are executed.  | 
 If the record transitions again, the prior step (State transition rule step) is repeated for the new transition.  | 
| 
 BO Post-processing algorithms are executed.  | 
|
| 
 BO Audit algorithms are executed.  | 
 These algorithms are only executed if the system detects a change in elements that are not marked with “no audit”.  | 
