This is not really an 'interview' in the sense discussed above. (In the above examples, the interview questions are placed at the top of a source document, and values are assigned and processed.) Here, were are creating essentially a document titled "Interview" with a single question that results in the selection of an appropriate second document. This is presented here as an alternative to the more elaborate Interview process described in above sections. It is yet another way in the Pathagoras arsenal to guide an end-user to an ultimate 'destination.'
Here is an example:
1.Create a document called "Will Interview." This document will contain a single Options text block consisting of one multi-part question, with a series of document references enclosed within "<<" and ">>" brackets being the 'answers. (It can also contain anything else you want.)
<<*Options*!Family Structure!Married with one or more children/Married, no children/Single (divorced or never married), with one or more children/Single (divorced or never married), no children*<<Married with Children>>/<<Married no Children>>/<<Single with Children>>/<<Single No Children>>>>
The 'administrative section (the text in blue) provides 'questions' that will be presented to the end user when that user calls up the "Will Interview". The remainder of the text block provides the references to the document that will be called based on the selection made. The "<<" and ">>" marks surrounding the document names indicates that you intend a document (or glossary clause) by that name to be called. (Without those boundary markers, you would get just text.)
Of course, there must actually be documents or glossary terms called "Married with Children.doc", "Married no Children.doc", etc. which respectively provide the text appropriate for "Married with one or more children", "Married, no Children" etc., wills.
2.The answer to the options posed in the 'first' document will result in a call to an appropriate 'second' document. This second document can contain 'terminal' questions (the full Interview, as it were) or can lead to additional documents in the Interview sequence. There is no limit to the nestings and references that can be provided and performed.
•Regular <<*Options*>> and <<*Optional*>> construction rules apply.
•The references can be to a complete document/template (as suggested in the above example) but they also can be to Clause Sets.
•If the reference is composed using the prefix/suffix naming convention (as shown in the example), or if the referenced clauses are stored in the Super Folder or Super Glossary, Pathagoras can quickly find desired clause without more in the clause name. See Search Order Rules.
•If the reference is not in prefix/suffix style, and the referenced clauses are not in the Super Folder or Super Glossary, the target clause either (1) must be found in the same folder as the initial Interview form (and this is likely to be true) or (2) must be fully qualify (with drive and folder designators).