Posts Tagged ‘update notes’

TechnoFeature: HotDocs Transformed – A Review of HotDocs 2006

AS IT APPEARED IN TECHNOLAWYER:

Buying a new pair of shoes is fairly simple – you pick out styles you like, try them on, and go with the pair that fits and looks best. But picking out shoes and picking out a document assembly program are two entirely different animals. In this article, technology consultant and HotDocs expert Seth Rowland takes the guesswork out of your search and arms you with all you need to know about the newest edition of LexisNexis’ popular document assembly software.

HotDocs 2006. Seth gives you the lowdown on the pros and cons as well as his wish list for future editions. Whether you’re new to document assembly or an experienced coder, we think you’ll find Seth’s exhaustive review helpful in your evaluation process. This article contains 2,753 words.\

INTRODUCTION: HOTDOCS AND ME

For the past eleven years I have dedicated my consulting practice to bringing “document assembly” to lawyers. As a “recovered lawyer” (University of Pennsylvania Law School ’88 and veteran of Cravath, Swaine & Moore and Kramer Levin LLP), I see document assembly as central to the survival of the practice of law. As law becomes perceived as a commodity service, only by embedding knowledge in expert systems and practice automation can the lawyers of today deliver competitive high-quality legal services.

In the past decade, I have implemented document assembly solutions on a range of different document automation platforms. I have worked with HotDocs since version 4.2, serving at various times as a HotDocs Reseller, a HotDocs Consultant, a HotDocs Partner and now as a HotDocs Certified Independent Consultant (“CIC”). I have participated in several beta programs for HotDocs and posted hundreds of support e-mails to the HotDocs list since 2001. Members of my staff and I have logged several thousands of hours working with HotDocs and teaching others to use it. I can safely say that I know the product pretty well.

TEST LAB EQUIPMENT

In reviewing HotDocs 2006, I have tested it on an older Compaq Presario X1000 (1.5 Mhz Pentium M with 512 MB RAM) and a newer Dell Dimension 4600 (2.66 Mhz Pentium IV with 2 GB of RAM). Both systems run Windows XP, Service Pack 2, with Microsoft Word 2003.

WordPerfect users should note that LexisNexis continues to support WordPerfect templates. However, some of the new features (like Markup View) are only available for templates developed in Microsoft Word. Unfortunately for users of Mac OS X, no Macintosh version exists at present, although with the newer Macs running on Intel, you can dual boot into Windows XP and run HotDocs.

To check for compatibility issues between HotDocs 2005 templates and HotDocs 2006 templates, I installed Altiris Software Virtualization Solution (available from www.altiris.com). With Altiris, I could install each version as a separate application layer. This enabled me to switch between the two versions without rebooting.

TRANSFORMATION OF HOTDOCS

Starting with HotDocs 6 and culminating in HotDocs 2006, LexisNexis has completely rewritten the HotDocs engine. HotDocs has shifted from a powerful dialog-box based template-filler, into a true interview-driven application.

In HotDocs 5, the assembler would parse a template sequentially, and present a series of dialog-boxes, as needed, to complete the assembly. With HotDocs 6, the dialog-boxes were merged into a single interview with the ability to navigate from one dialog to another through an interview tree. This change began the shift from a template-driven system into a scripted interview-based application.

Over time, the developers added features to the interview. Via tabs, you could see a blank questionnaire and a fully completed questionnaire. In HotDocs 2005, they added a dynamic document preview. As the answers in the interview changed, the text in the preview changed. Variable text was marked in blue with hotlinks to actual questions. You could now use a comparison tool to visually compare the text under different scenarios.

With the inclusion of the HotDocs database connection (and its enhancement), as well as the Time Matters connector, HotDocs entered the world of workflow, giving it the ability to easily pull in data locked in company and law firm databases.

HotDocs 2006 represents the culmination of this evolutionary process: easier, faster, more powerful, more flexible, and with a richer user experience. LexisNexis has also addressed the need for lawyers to better understand the templates through markup tools and coloring that hides the complexity of the systems.

PROS OF HOTDOCS 2006

Below you’ll find just a few of the new features available with the latest release of HotDocs.

The Error Is Your Fault – And Now You Know Why

Perhaps the best new feature of HotDocs 2006 is that “IT WORKS.” Stability issues plagued a number of the new features that emerged in HotDocs 6, but these have now been ironed out. HotDocs 2006 doesn’t crash; it gives you an error message and takes you to the text of the template or the portion of the script that has caused the error. Most “crashes” result from template developer error (sorry folks, it is sometimes your fault). The problem was lack of information in a complex multi-template system; i.e. identifying the location of the error. The system will now halt the assembly and take you directly to the error.

In the template development environment, you can click a button to “Test Assemble” the document. In this Test Mode, you can use the Document Preview tab to test for errors under different scenarios and then use the editor to right-click on an offending variable or dialog to edit the script or text.

You Would Be Foolish Not to Use These Tools

Haven’t you realized that “real” template developers use toolbars? Seriously, template development is complex with myriad opportunities to make mistakes. In recognition of this, you now have a range of tools on the Word toolbar to assist in spotting potential errors in coding and adding codes:

Markup View/Developer View

This feature enables the developer to hide all the “blue code” in a template and present it to the knowledge specialist with a simplified markup. Green square brackets denote the borders of conditional text. Blue italic text in square brackets denotes fields — very much like standard word merge-text fields. In this manner, you can edit the text of the template without the distracting conditional logic. And then, with a single click, you can convert the template back to developer view with all the HotDocs codes revealed. Making templates more readable is always a good thing.

HotDocs Outliner

Have you ever wanted to know which questions were ONLY asked if the Borrower was a corporation, or some other special criteria? With the HotDocs Outliner, you have a visual tree of all HotDocs variables in a template. If they appear in conditional text, the outliner will show all the parent conditions which determine the relevance of that particular variable. This feature really works; but you need to be in Developer View (see above) to use it.

Apply Colors -> Nested

In HotDocs 2005, the concept of colors for conditional logic was introduced, along with the ability to number rules. In HotDocs 2006, this feature has been refined with the addition of a nested color schema. This means that by visual references (green is top level), you can tell all the parent conditions for a particular block of text. In plain English, you can now know “why” that darn paragraph did not show up in the template … or the converse. As part of this feature, HotDocs will throw an error if there is a missing END IF or an extra END IF and bring you to that point in the template to fix it. HotDocs also has a “sequential” coloring scheme. While the colors are pretty, this feature is only marginally helpful in diagnosing errors in template design.

Other Refinements to Toolbar Buttons

Match Fields and Label Fields are useful tools. The first enables you to click on a conditional expression and find the matching END IF (or converse). The Label Fields formalizes what has been known by developers for years — that you can provide documentation inside a HotDocs fillpoint which does not affect the automation by using a “//” followed by the comment. Label Fields now enables you to control the visibility of those comments as well as supply a sequential identifier for each block of conditional text.

Bake the Cake and Eat It Too with Span Tags

How often have you wanted to change a section of an automated document, while preserving the automation so that you could reassemble the document? With the addition of a SPAN instruction, developers can now control document editing by marking sections of a template as a SPAN. This enables users to edit that section of text at the Document Preview tab of the assembly window. You can then save changes made during assembly to the answer file so that you can reassemble the same document later and have your changes reapplied. Used judiciously, this is a great feature. It moves the editing process into the Document Interview. For some users it may appear counter-intuitive: to edit an automated document, you need to “assemble” it, click on “preview” and then make your changes. This is not yet the “holy grail” of document assembly, but it gets closer.

The Razzle-Dazzle of Dialog Elements

HotDocs now provides a new Dialog Element component that enables you to add additional text, hyperlinks, buttons, graphics, lines, and spacing to dialogs more easily. HotDocs has gotten rid of the ugly undeclared component known as “additional text.” What used to be done by special scripting of “additional text” now is done much more logically with this new component. You should really care about this because it makes the “user” experience so much simpler.

What the Heck Are “Dot Codes”?

HotDocs 2006 introduces a new feature called dot codes, which enables you to 1) format text results derived from computation scripts, 2) insert special characters in plain text and template text, 3) format variable prompts and additional text, and 4) punctuate non-repeated lists of answers. This stuff is “cool.” If I had the last item, the punctuation codes, I would be much poorer today, for I have charged clients thousands of dollars to implement proper punctuation in automated agreements.

SOME AREAS OF CONTINUING WEAKNESS

Speeding Up Complex Interviews

With so much now riding on the interview that needs to be rendered dynamically, certain aspects of HotDocs has slowed down. There are pauses when you exit a question before the screen refreshes that can last a second or two as HotDocs crunches through the implications of each change. HotDocs has provided a solution, a button to “turn off dynamic interview.” This will substantially speed the performance since HotDocs will not refresh the interview tree until you exit the dialog.

Answer File and Document Management

HotDocs has historically been built around single template assembly off a shared client or matter answer file. If you don’t have a document management system (“DMS”) like Hummingbird, iManage, Worldox, or Time Matters, you will have to manage documents with Windows Explorer. This works fine when producing one document at a time. However, when you use a single interview to produce 20 documents (e.g. a loan package), HotDocs does not give you control (in the Interview script) to define the name and location of the answer file based on questions in the interview or to provide an output folder and location for the documents being assembled. A clunky workaround for the ASSEMBLE command exists, but more explicit control in scripting would go a long way in giving HotDocs workflow functionality.

Autosave an Answer File

The HotDocs API (Application Programming Interface) is very powerful. In the hands of an experienced database programmer, miracles can happen. However, most template developers are not experienced programmers; they generally come from the ranks of lawyers, paralegals, and legal secretaries and are self-trained. I would love it if some of the functions of the API could be incorporated as functions in the component manager — in particular, the ability to force a “SaveAs” which incorporates a HotDocs Variable into an Interview Script.

More Sophisticated Event Management

When a programmer talks about events, she is not talking about parties. HotDocs supports only two types of events: a global on change and a local on click. The on change happens when you change a variable. Every time you change a variable, it is checked against all scripts in the system. If there is a match, that script fires and things happen in your interview. By contrast, the on click event happens ONLY when you click a button. It would be better to have a middle ground, where you can tie an event directly to a single variable and have it fired “on exit” from that variable.

Rationalizing Complex Dialogs with SubTabs and More Variables in a Row

Computer monitors provide only so much screen “real estate.” For dialogs with lots of variables, the screen fills up with questions (and the infernal scrollbar emerges). This happens because HotDocs only enables you to put three variables in a row. This made sense when we had VGA screens with 640 x 480 resolution. But I run two 19-inch LCD panels with 1280 x 1024 resolution and my three variables in a row dialogs look ridiculous. The ability to layout additional variables would go a long way in making the dialogs more user-friendly. HotDocs could add a new dialog element called a “SubTab”. By default, all variables in a dialog would be on the primary tab. However, once you inserted a SubTab, all variables that followed would reside on the SubTab. Tabs would have titles and run across the top of the dialog. So rather than scrolling (to see what you can see), you could click on the tab button.

WISH LIST FOR THE NEXT VERSION

Developers always want “more.” So I’ve compiled a speculative wish list for LexisNexis to consider.

Component File Plugins

HotDocs enables the developer to use “pointed component files.” In so doing, the developer can avoid “rebuilding” dialogs and variables for each template. With HotDocs 2006, the “pointing component file” can have a single computation component that contains a special interview script that calls on the master component file. This is the first step to making HotDocs more modular. Ideally, you’d have a master component file that at runtime can pull in elements from multiple other component files. This would enable you to develop special-purpose CMP files that function essentially like plug-ins to extend the power of the program.

Custom Functions

HotDocs has a powerful scripting language, with a number of special functions for text, number, and data manipulation. There are times, however, when there is no function available for the task at hand. The current approach is to create repetitive computations. So if a special format is required for fractional shares, a new computation script is created for “each” variable that needs to be converted into a fractional share. With a function, you can pass an argument to it, e.g. and then reuse that computation for handling other variables.

Style Sheets and Library Level Customizations

With HotDocs 2006 you can change the appearance of the HotDocs interview, selecting colors, font type, and font size. This approach works much like a Web-based cascading style sheet, enabling the same interview to be rendered differently depending on the settings in the styler. If the style settings could be stored at the HotDocs Library or the Component File level, content providers (and office managers) could provide a distinctive look and feel for each form-set (e.g. Red is for Real Estate and Blue is for Corporate).

EXPERIENCE WITH TECH SUPPORT

Technical Support for HotDocs falls into two categories: (1) application support, and (2) template development support. LexisNexis provides very effective application support: installation assistance, compatibility issues, support for links to word processors and document management systems. If the program won’t load, or the PDF writer won’t work, LexisNexis support technicians will work with you until it does.

However, LexisNexis draws the line at template development support. Any issues regarding the proper design or functioning of templates, development of interviews, formatting, etc. is handled either through paid consulting services offered by LexisNexis; through a searchable and extensive HotDocs knowledgebase; or through the HotDocs Listserver.

The HotDocs List (with over a thousand registered members) is a unique place for freewheeling discussion of ideas, problems, and best-practices. Unlike other lists, HotDocs developers (both those working for LexisNexis and those working independently) actively monitor this list and review and respond to posts by users. Many discussions started on-list move to off-list calls and exchanges and real solutions. The response time for posts can be measured in minutes, whether it is from a developer or a fellow user with a similar issue.

CONCLUSION

If you take your law practice seriously and plan to stay in the law business over the next decade, you should seriously look into document assembly, and more specifically HotDocs. It is a truly great product that can dramatically enhance your productivity and profitability. Buying the software, however, is only the first step. Like my membership at New York Health and Racket Club, merely paying dues doesn’t make you healthy and fit.

Copyright 2006 Seth Rowland, Esq. All rights reserved.

ABOUT THE AUTHOR

Recovered attorney Seth Rowland was named TechnoLawyer Consultant of the Year in 2002 for his contributions to TechnoLawyer on the subject of document assembly and law practice automation, and more importantly, his service to law firms around the country. He is a nationally known technologist whose company has helped many law firms and content providers build document assembly applications for both internal use and for resale. Please feel free to visit his blog for the latest on document assembly or the video tours page to see what such a system can look like. Basha Systems currently offers document assembly consulting services in HotDocs, DealBuilder, and Perfectus.

Basha Systems Document Assembly Blog Ready for Syndication and HotDocs 2006

We have been busy restructuring all our website in the Basha Systems family: Bashasys.net, our client new client portal, Bashasys.com, our main consulting site, Bashasys.org our Fogbugz project tracking site, store.bashasys.com, our store.  There are two other sites almost ready to go live to support our Nebraska Probate System V and a new system for Building Inspectors. With these items out of the way, I am ready to return to commenting on developments in Document Assembly.  In particular, HotDocs 2006 is about to go into Full Beta. I have gathered posted by chief architect of HotDocs Marshall Morrise to the public HotDocs list.  When the product comes out of beta and is released, come back for a discussion of these innovative new features.

There has been discussion on the HotDocs List of several potential features in the HotDocs 2005 Beta.  I will confine my comments to posts from Marshall Morrise, the chief architect of HotDocs to the HotDocs ListServer.  These posts reveal some major new features under the hood that will catapault HotDocs to the lead as a full fledged document assembly development platform.

February 9, 2006: Feature Set

All new features we have discussed on the list over the past several months (including the one referred to below) are being implemented in HotDocs 2006. The one exception is support for WordPerfect X3, which has been added to HotDocs 2005 SP3 (available soon). The reason we put this into a 2005 version is that WordPerfect X3 is already out and we don’t feel we can expect customers who upgrade to it to wait until HotDocs 2006 comes out in June.

Feb. 9, 2006: Access macros from an non-loaded template

The discussion regarding macros stored in a secondary template had to do with HotDocs 2006. We have implemented the feature we discussed. A new component file property allows you to specify a Word .dot file that contains PLAY macros. The .dot file must be in the same folder as the template that includes the PLAY instruction. Thus, if you distribute a template set where one or more of the templates includes a PLAY instruction, instead of requiring users to copy the PLAY macros into normal.dot, or putting them in a template that must be copied to the Word Startup folder, you can simply include the .dot with the template set.

January 20, 2006: Pretty Templates

In this example, variable titles have been substituted for variable names and square brackets have been substituted for IF/END IF pairs. Color would be used to identify variables and the brackets for IF instructions (which I can’t show here because the list server just strips color out). Footnotes would be used to show the actual IF logic. Other things would be done as well.

December 13, 2005: Required Fields

Because the HotDocs 2005 Server interface mimics the desktop interface, it does not include asterisks for required fields. Instead, the fact that a required field is not answered is indicated by a red asterisk in the interview outline. That said, requests for the asterisks have been frequent enough that both the desktop and server interfaces for HotDocs 2006 will include a user option to show red asterisks at the left side of prompts for required fields.

November 23, 2005: Update Table of Contents and Indexes in Word

In HotDocs 2006 we’ve added a component file option titled “Update table of contents and index after assembly”. If you turn this on, HotDocs will automatically update the TOC and indexes so you don’t have to PLAY a macro to do it.

November 17, 2005: Inserting an OR in a document based on rules

At the moment, the only way to accomplish what you are asking about is to write some computations that figure out which lines get included in the document. Someone on the list can probably help you out with an approach. For everyone’s information, a feature that will make this very easy (no computations involved) will be included in HotDocs 2006.

November 2, 2005: Master Component File – But Independent Document Interviews

Just so you know, HotDocs 2006 will allow you to specify a different interview component for each template that points to a shared component file. While this doesn’t address all of the issues raised regarding using shared component files, it does address the issue Bart mentions immediately below.

October 19, 2005: Unique Values in a Multiple Choice Variable

I have received a request to produce a function that will filter out unique responses from a repeated multiple choice variable.  To get this list of unique selections across the repeated set of answers, I have to do quite a bit of scripting, including setting a counter, copying over options from the Favorite Desserts variable to a temporary collection variable, using a WHILE to look through the collection variable to make sure I don’t duplicate a choice, etc.

October 6, 2005: Text Manipulation Functions

We have discussed the addition of some built-in text manipulation functions to HotDocs to make it easier to manipulate text answers, particularly multi-line answers. There have been a number of suggestions, including “normalizing” multiline text to make it single-line, stripping off white space, etc.

After reviewing the emails and suggestions offered, we proposed to create the following built-in text manipulation functions:

STRIP(, , , )

text variable = any text variable
characters = characters to be stripped off
frombeginning = TRUE if characters to be stripped from the beginning of the text
fromend = TRUE if characters to be stripped from the end of the text

Characters to be stripped off can include the following “pseudo-codes”:

^t for a tab
^s for a hard space
^p for a paragraph mark/hard return
^w for any white space

etc. (rather like what you can do with Find and Replace in Word)

REPLACE(, , , )

text variable = any text variable
searchfor = character string
replacewith = character string
all = TRUE to replace all occurrences of with instead of just the first one

Searchfor and replacewith can include the same pseudo-codes shown for STRIP above.

SPACE()

Yields the answer plus a space if the text variable is answered or an “answered nothing” otherwise.

Examples of use:

SET MultiLineAddress TO STRIP(MultiLineAddress, “^w”, TRUE, TRUE)

Strips white space from the beginning and end of a multi-line address.

SET OneLineAddress TO REPLACE(MultiLineAddress, “^p”, “, “)

Replaces returns in the multi-line address with a comma and a space to form a single line address.

With SPACE, instead of a computation containing:

ClientFirstName + “ “
IF ANSWERED(ClientMiddleName)
RESULT + ClientMiddleName + “ “
END IF
RESULT + ClientLastName

you could use:

ClientFirstName + “ “ + SPACE(ClientMiddleName) + ClientLastName

October 6, 2005: Bold, Italics and Underline in Computations and List Punctuation

Issue

1. Quite a number of developers have requested a way to identify bold, underscore, and italics in text produced by computations for insertion into a document.

2. A similar number of developers have requested a way to get bold, underscore, and italics into additional text or prompt text in a dialog.

3. A smaller, but still meaningful number of developers have requested a way to get “a, b, and c” style punctuation into a document without using a repeat. For example, if I want to list a client, the client’s spouse, and their children as “My family consists of myself, my spouse Sam Jones, my son Tim Jones, and my daughter Sue Jones”, where the children come from a repeated dialog but the parents do not, I have to do some tricky scripting.

Proposed Solution

We propose to implement a new kind of field that can be inserted into text. The field will contain something I’ll call a “dot command”. Here are some
examples (using single angle brackets in place of chevrons):

In a computation script:

SET Variable TO “Please be <.b>very<.eb> careful when moving the cannister.”

The “.b” and “.eb” commands represent bold and end bold respectively. When this text is merged into a document, or when it is displayed in a dialog, the visible dot commands will be replaced by actual bolding of the word “very”.

Similar commands would be implemented for italics (.i) and underscore (.u).

It might be good if we used longer words for the dot commands, like “.begin bold” and “.end bold”. These would be easier to recognize in the text. The downside is, they’re long.

It might be good if we were to use some other character to “introduce” the new commands. We need to use something that has never been allowed as a valid character to being a HotDocs component name. One suggested character has been the backslash. We (I) like periods because they’re fairly unobtrusive.

QUESTION 1: How do you feel about this scheme of allowing visible fields in text that will be translated into the “real thing” in documents or dialogs? If you don’t care for it, do you have other suggestions?

QUESTION 2: Do periods (dots) work for you, or do you think some other character would be better?

QUESTION 3: Are you OK with short, mnemonics (like “.b” and “.be”) or do you prefer longer commands (like “.begin bold” and “.end bold”)?

In addition to dot commands for specifying bold, underscore, and italics, we’ve considered commands like:

<.an> inserts “a” or “an” depending on the word that follows
<.> inserts a period, but only if no punctuation precedes the dot command (useful when inserting a sentence typed by the user as an answer)
<.lq> inserts a curly left quote
<.rq> inserts a curly right quote

There are more things we’ve thought of (curly apostrophes, other conditional punctuation, etc.)

QUESTION 4: Are there other commands of this sort you’d like to see implemented? If so, please describe them.

As the solution to non-repeated list punctuation, we propose to implement:

<.p “format”> identifies the beginning of a punctuated list and gives the format
<.p> identifies the spot where punctuation characters should be inserted
<.pe> identifies the end of the punctuated list

Using the family example described above, you could have something like:

<.p “a, b, and c”>My family consists of myself<.p>my spouse <.p>my Name><.p><.pe>.

which would be assembled as

My family consists of myself, my spouse Sam Jones, my son Tim Jones, and my daughter Sue Jones.

QUESTION: Will this be useful to you?

I should mention that we expect to do two things:

1. Create an interface for inserting dot commands (so you don’t have to remember them).
2. Make it possible to hide dot commands so users who preview your templates won’t see them.

Basha Search

Loading

Basha Network

Basha Product Sites