The Business Operations Framework (BOF) has been renamed to the SysOperation Framework. This new name more accurately describes the framework, which includes a number of classes with the prefix “SysOperation.” For more information and a link to example code, see the white paper Introduction to the SysOperation Framework.
You use the SysOperation framework when you want to extend Microsoft Dynamics AX by adding new functionality that may require batch processing. The SysOperation framework replaces the RunBase Framework and provides infrastructure for creating user interaction dialog boxes and integration with the batch server for batch processing.
The SysOperation framework supports a variety of development scenarios. You can use the SysOperation framework to enhance processing performance by explicitly specifying when and how operations are executed. For example, you can run operations that are triggered by user interaction, or schedule them to run via the batch server.
In another example, the FormLetter framework is used to post documents for sales or purchase orders. This framework has been refactored to provide better support for customizations, extensibility, and performance by using the SysOperation framework. For more information, see the white paper Using the Refactored Formletter Framework.
For information about other development patterns and programming models available with Microsoft Dynamics AX 2012, see the white paper Selecting the Best Development Technology for Your Application Development Scenario.
For great additional resources about the SysOperation framework, see:
- Brandon George’s blog posts on the SysOperation framework: http://dynamics-ax.blogspot.com/search?q=sysoperation
- Joris de Gruyter’s blog posts on the SysOperation framework: http://daxmusings.codecrib.com/search?q=sysoperation
