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 shown as an alternative to the more elaborate Interview process described in this section. 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."  For this example, it 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. However, it can contain anything you want.
 
The individual references are to documents that contain text appropriate to the response to the options presented. Here is what "Will Interview" might contain.

<<*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) of the options block above provides 'questions' that will be presented to the end user when that user calls up the "Will Interview" document. 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.)  (Please note that the coloring you see is for illustrative purposes. Colors are not required in the actual template or clause.
 
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.

Notes:

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).

 

Don't confuse the Interview (a top of document entity)

with the <<*Options* and *Optional*>> blocks (a document body element)!

  The interview has its own structure rules. The interview is entire optional and most users (currently) don't use it because it does involve a bit of programming. The Interview asks questions and, as asked and answered and values set, they disappear. The interview does not, is not intended to, and cannot be used to provide substantive text within its boundaries. Just a question (converted into an interview form).

   "Asks" and "Ifs" are uniquely Interview functions. They cannot be used within Options and Optional text blocks. Options and Optional text blocks are document body elements

   So, the following is NOT a proper Optional block:

<<*If*!b!=”Yes”,[Borrower Name], [**a] [Borrower State of Organization] [borrower entity type],!b!=”No”[Guarantor Name], [**a] [Guarantor State of Organization] [guarantor entity type]>>

But THIS IS FINE:

<<*Optional*!b![Borrower Name], [**a] [Borrower State of Organization] [borrower entity type]>>

OR (if you want to provide a 'negative' value, add a slash)

<<*Optional*!b![Borrower Name], [**a] [Borrower State of Organization] [borrower entity type]/[Guarantor Name], [**a] [Guarantor State of Organization] [guarantor entity type]>>

   Note that the Optional block structure is very simple and straight-forward.  It contains no 'logic' (If / then) language. It is very straight forward. It tells you right off the blocks 'purpose' (i.e, that it is "Optional" or "Options" text and then it presents the text. If you want to set a group value, or to link the text block with a !group! value that was earlier set, simply type the group name immediately after the Optional or Options call. Then provide the text results. Nothing more. No 'ifs' required (or allowed). See above sample.

,