This content has been marked as final. Show 4 replies
OPA interviews are generally goal directed. It is the rule logic that leads to the goal that determines what data is collected.
In other words, if a particular attribute of an entity needs to be known in order to reach a decision, the screen that collects that attribute will be displayed to the user to collect instances of that entity.
To give a practical example. If you have a goal "the interview has been complete", you can write a rule which says something like
If you start to investigate this goal, an automatic screen will appear to ask you the person's name. This is how an interview is Goal Driven
the interview has been completed if* the name of the person is known.
The example above is a fairly simple and artificial example of how a goal driven interview works. A more practical (and complex) example might be something like
In order for the goal "the applicant is eligible for benefits" to be answered, all the information in the sub clauses will need to be collected. Age, number of children, the age of each child.
the applicant is eligible for benefits if the age of the applicant is < 30 the applicant has at least one child Exist(the applicant's children, the child is under eighteen years of age)
You can specify a particular interview flow, and customised interview screens,to enhance the a goal driven interview. For more information on this, see: Interviews and flows in the Oracle Policy Modeling User's Guide (http://docs.oracle.com/html/E27987_01/toc.htm)
Edited by: frank.hampshire on Jul 3, 2012 8:41 AM