Automatic creation of <<*Ask*>> commands:
At your request, Pathagoras can scan your source document for any <<*Options*>>, <<*Optional*>> and <<*Repeat*>> blocks that are present. It can pull the essential elements from each such block and then create a basic <<*Ask*>> command for each such block, placing it the top of your document. You can further edit and refine the prompt so that it best meets your needs.
Note: Only <<*Options*>>, <<*Optional*>> and <<*Repeat*>> blocks that contain a !group! reference will be processed. So, before running the routine discussed below, you may wish to add a !group! reference to your <<*Options*>> and <<*Optional*>> text blocks to take advantage of this feature. Even if there is only a single member of the group, you may find that the benefits of the <<*Ask*>> command are worth the effort to do so.
To create the <<*Ask*>> commands in this automated fashion:
|1.||Make sure that the document to which you want to add <<*Ask*>> commands is on screen.|
|2.||Click the Pathagoras | Authoring/Editing Tools | Create Ask Blocks element.|
When clicked, Pathagoras will scan the document for any <<*Options*>> and <<*Optional*>> text blocks that contain a !GroupName! reference. Pathagoras parses out the administrative content of each one and placed it into an <<*AskOptions*>> or <<*AskOptional*>> block, as appropriate, at the top of the document. An additional 'instruction' block is added containing usage information.
|3.||Review the prompts that were created. Modify the questions as appropriate to make the appropriate response as unambiguous as possible.|
Clause Sets: If you assemble documents using Clause Sets, the actual <<*Options*>>, <<*Optional*>> and <<*Repeat*>> blocks may not be present in the 'raw' document, and therefore are not going to be picked up by the tool discussed above. Here are the steps to follow in that instance:
|•||create a 'complete' document which contains all possible options and optional text blocks.|
It is not important at this stage that the resulting document contains more text than would ever be used. The idea here is to have a document that contains all of your <<*Options*>>, <<*Optional*>> and <<*Repeat*>> elements.
Before you create this 'huge' document, you should turn 'off' processing so that the <<*Options/Optional/Repeat*>>blocks are not automatically processed.)
|•||Run the automatic <<*Ask*>> command creator described above. |
|•||Edit the <<*Ask*>> commands to your satisfaction. |
|•||Copy and paste the entire block of <<*Ask*>> commands into the first clause that you use when assembling via Clause Sets. (Typically, the 'first clause' is the same throughout all documents in the topic, but not necessarily. |
|•||If some <<*Ask* >> commands seem inappropriate to a particular Clause Set, just delete it (for example, when a clause set creates a Will for a family with no minor children, delete <<*Ask*>> commands referencing a !Guardian!).|
|1.||The source <<*Options/Optional*>> block must each contain a !GroupName!. Reason: the <<*Ask*>> command must have a !group! reference in order to link with <<*Options/Optional*>> blocks further below in the document.|
|2.||The <<*Options/Optional*>> must either contain 'prompt' statements/questions or, if no such statements, actual text options whose combined length is less than 150 characters. (If longer than 150, an <<*Ask*>> block will still be created, but you will be prompted to create manually the actual prompts that will be asked of the end user.)|