Controlling Message Class Use

With so many message classes and pages in use, how did the developers specify which ones would be opened under which conditions? This is done in several ways, some during development and some during deployment:

• While authoring the form, you can define standard or custom actions on the Actions page. An action specifies in detail how to respond to events such as Forward or Reply to Folder. This specification includes what type of form to use and where to make this action available in the user interface.
• The Outlook form's script provides granular control over the display of a form's pages and its versions; see Displaying the Form's Pages. For example, the script uses CDO to create, populate, and finally send a message of the IPM.Post.ToApprover message class. See LitCrit_Agent.asp Event Service Script.
• During deployment, you can choose to install only forms of specific message classes into a folder and set a default form for that folder. See Creating and Configuring the LitCrit Public Folder.