SysOperation framework part 1:

In Dynamics 2012, the runbase and RunbaseBatch has been replaced sysoperation framework. The main difference between the old and new framework is as following,

Runbase and RunbaseBatch	Sysoperation framework
No controller class.	Controller class to perform operation such as which UI to show.
No contract class. Use of marco	Contract class to store the data which need to display on the UI
No UI class	Separate UI class to handle the event and operation related to UI
No Service class	Service class to perform the business operation base on the input.

In sysoperation framework we have three main classes which are as following

1. Controller Class:
   1. The purpose of controller class is to perform the following operation
      1. Determine which UI should be used.
      2. Determine whether the operation can be perform in Batch.
      3. Determine the caption of the dialog
2. Contract Class:
   1. The Contract class is use to save user input and gives it to service class to perform the service. It has parm methods for each of the field which will be shown on dialog.
3. Service class:
   1. The service class is use to perform the business operation which is required. It must have a method which have attribute of EntryPoint. This method will be called by sysoperation framework when the user click on the Ok button on the dialog. Additionally, the method must take the contract object as the argument of this class.
4. UI class (optional)
   1. The UI class is used to create the UI of the dialog. This is operation class and should only be added if you have some validate need to perform on the modification of dialog control.

After creating these classes you need to create a menuitem to launch this dialog. The menuitem should be created for controller class and it also has service class information in it. Which is given in parameter field of menuitem.