anchor.diff:  
   +
   A row with conflicting cells never executes.
  +* Broken *Unique Hit* Policy
  ++
  +When the *Unique Hit* policy is applied to a decision table, only one row at a time can be executed and each row must be unique, with no overlap of conditions being met. If more than one row is executed, then the verification report identifies the broken hit policy. For example, consider the following conditions in a table that determines eligibility for a price discount:
  +
  +** When Is Student = true
  +** When Is Military = true
  +
  ++
  +If a customer is both a student and in the military, both conditions apply and break the *Unique Hit* policy. Rows in this type of table must therefore be created in a way that does not allow multiple rules to fire at one time. For details about hit policies, see <<_hit_policies_con>>.
   * Defiency
   +
   Defiency is similar to a conflict and occurs due to incompleteness in the logic of a rule in a decision table.
  
positive.code: 
  == Verification and Validation of Guided Decision Tables
  
  
  In Business Central, the guided decision tables are a way of representing conditional logic (rule) in a precise manner, and they are well suited to business level rules.
  
  === Introduction
  
  
  Business Central provides verification and validation feature to help ensure that a guided decision table is complete and error free.
  The feature looks for gaps in the logic of a guided decision table and validates the relationship between different cells.
  
negative.code: ** when Deposit < 20000 then Refuse Loan
  
  +
  These two rules may lead to confusion for a person who is over 20 years old and has deposited less than 20000.
  You may add more constraints to avoid the conflict after noticing the warning to make your rule logic complete.
  * Missing Columns
  +
  In some cases, usually by accident, the user can delete all the condition or action columns.
  When the conditions are removed, all the actions are executed and when the actions columns are missing the rows do nothing.
  Both may or may not be by design, usually though this is a mistake.
  * Incomplete Ranges
  +
  Ranges of field values are incomplete if a table contains constraints against possible field values but does not define all possible values. The verification report identifies any incomplete ranges provided. For example, if your table has a check for if an application is approved, the verification report reminds you to make sure you also handle situations where the application was not approved.
  
  
  === Reporting
  