The most conservative (that is, safest) approach for managing auto-validation is to set an auto-validation level

for each particular report that can be given by the project. The disadvantage of this approach is that for larger projects (e.g. projects with hundreds of different comments) the number of reports that need to have an auto-validation level setting becomes too large to manage easily. Hence for these larger projects, it is advisable to manage auto-validation using report sections, or using rules.

To set autovalidation levels on a report-by-report basis:

  1. Use the menu Auto-validation | Report Settings to show a table of all reports that have been recently given by the project, that is, given within the last month.
  2. Review each report in the table. Reports that already have some level of autovalidation set will have a tick in the Allowed column, and possibly a percentage in the Level column. Note that clicking on a column heading will sort the table by the values in that column. For example, clicking on the Given column will order the reports according to how often each report has been given by the project.
  3. The Rejected column shows how many times the corresponding report was corrected during validation, that is, was inappropriately given by the project. Reports that are never, or rarely, rejected are possible candidates for auto-validation.
  4. If you decide to set a non-zero auto-validation level for a report, click the Edit button and set the desired auto-validation level for that report. The Allow auto-validation check box will be checked automatically if you set a non-zero auto-validation level.

For more information on the report table, see Reports.

Changes made to auto-validation settings are effective immediately.