Decide Whether to Allow Uncertainty In User Answers

During an interview, it is possible for attributes to all have a valid value of "uncertain". In its most straightforward application, uncertainty reasoning operates to infer attributes to uncertain when the conditions that prove the attribute are uncertain. This allows the interview to continue until the goal attribute has a value, without requiring the user to answer every question. This means that the goal attribute may end up being uncertain, but it may also be able to return true or false based on other information provided by the user. If a definite answer to the investigated goal can be proved by some means, then it may be that the user does not have to obtain the missing information (for example, where one option in an OR rule is uncertain, but another returns true). In contrast, if the user could answer only 'yes' or 'no' or select a fixed value to every question, the interview would stop until the user was able to answer the question. Unhandled, however, uncertainty can introduce unintended consequences in your interviews so should be carefully applied.

Note that if you are creating or updating required fields in a connected application, you need to ensure that they will have a value when the interview is submitted. Specifically you need to ensure that:

1. For tables in the connected application that are created by an interview, every application required field must be output mapped and set as mandatory on the Intelligent Advisor interview screen (or calculated by Intelligent Advisor).
2. For tables in the application that are updated by an interview, every application required field that is output mapped must be set as mandatory on the Intelligent Advisor interview screen (or calculated by Intelligent Advisor). That is, it is OK to have unmapped application required fields but output-mapped application fields must have a value.