XpressDox News

The Define Command

XpressDox gives quite a lot of power to template authors in controlling the layout of the interview for a template. For example, the layout commands for an email address might look something like this: <<Caption(EmailAddress,Email address for correspondence)?Enter the email address or choose one from the list.>><<ChooseFromSamples(EmailAddress,,jlsmith@ipprovider.com,egjones@inkpen.com,mcontrary@inkpen.com)>><<Heading(EmailAddress,|^b^@Navy@CONTACT INFORMATION)>> <<Required(EmailAddress)>> <<SetInitialValue(EmailAddress,audrey@inkpen.com)>> <<Rule(EmailAddress,hard,IsEmailAddress,'The value is not a […]

go to article

Version 3.6.0 (2011-03-31)

An underscore in the data element name is converted to a space when the data element name is used as a caption in the interview. The Command Editor and the XpressDox My first template document are loaded automatically the first 3 times that XpressDox is loaded. The <<Define()>> command is introduced – enables definition of […]

go to article

Convert templates from other systems to XpressDox format

Templates authored in HotDocs®, GhostFill® and other document assembly systems can, with varying degrees of certainty, be converted to run successfully with XpressDox. Why this works In principle, almost any delimiters can be used by XpressDox as fillpoint delimiters. For historic reasons, the << and >> pair were chosen as the default (with effect from […]

go to article

Version 3.5.0 (2011-03-04)

Templates coded in some earlier document assembly formats will now run without change (except for conversion to XpressDox template format, i.e. Word 2003 XML), as long as the fillpoints are “simple”.  A “simple” fillpoint is one which has no functions or commands or conditional assembly, e.g %[Name], «PostalCode» .  Also, the fillpoint name (i.e. data […]

go to article