Usually, after applying changes made in the Select transactions to audit the developer selects the K2B Audit/Create audit triggers menu option to generate the code required to start auditing all selected items. If Execute Create Triggers code preference is true, it also compiles and executes the generated code.
The first time the developer executes this menu option a dialog pops up stating that the Analyzer Knowledge Base for this Audited Knowledge Base is not created. The dialog lets you create the Analyzer Knowledge Base before continuing or cancel.
If the developer chooses to create the Analyzer Knowledge Base, it is created and initialized as described in Creating the Audit Analyzer Knowledge Base.