The NEW XpressDox Version 14 is now available!

Edit Content
Click on the Edit Content button to edit/add the content.

XpressDox Support

FormatDate

Dates can be formatted according to patterns defined in the fillpoints.   Command structure: «FormatDate(Date_of_Engagement,”yyyy-MM-dd”)» «FormatDate(Date_of_Signature,”MMM d yyyy”)» «FormatDate(Date_of_Dismissal,”d MMMM, yyyy”)» «FormatDate(Date_of_Signature,”MMMM o yyyy”)» «FormatDate(Date_of_Signature,”dddd MMMM o yyyy”)»   These examples would result in something like, respectively: 2019-02-07 Feb 7 2019 7 February, 2019 February 7th 2019 Thursday February 7th

Read More »

The Max and Min Functions

Max calculates the maximum of two values: The maximum of «Number1» and 100.1 is «Max(Number1,100.1)». Min calculates the minimum of two values: The minimum of «Number1» and 100.1 is «Min(Number1,100.1)».

Read More »

The Now and Today Functions

Now The Now function inserts the current date and/or time into the document. It can be formatted in the same way as for FormatDate. «Now(“d MMMM, yyyy”)» yields ‘4 November, 2010’ «Now(“MMMM o yyyy”)» yields ‘November 4th 2010’ «Now(“yyyy/MM/dd HH:mm:ss.fff”)» yields ‘2011/04/14 17:05:23.010’ which is exactly the same as «Now()»

Read More »

NumberPhrase

NumberPhrase is used to convert a number to words, in several different languages. Command structure: «NumberPhrase(Area,”,’leave’)» Examples of usage: «NumberPhrase(Area,”en-us”,”ToUpper”)» Suppose a data element with name ‘Area’ has a value 1234:This would yield “ONE THOUSAND TWO HUNDRED THIRTY-FOUR” Parameters: Languages supported are ‘en’ (US English, the default), ‘fr’ (French), ‘de’

Read More »

The Replace Function

Replace is used to replace all occurrences of one string in a source string with another string: «Replace(Address,”Ave.”,”Avenue”)» “123 Long Ave., Cape Town” becomes “123 Long Avenue, Cape Town”

Read More »

The StartsWithVowel Function

The result of this function would typically not be included directly in the merged document, but would be used in a conditional, such as: If «When(StartsWithVowel(Fruit),an,a)» «Fruit» is ripe it tastes better than if it is rotten. The function assumes that ‘a’, ‘e’, ‘i’, ‘o’ and ‘u’ (and their uppercase

Read More »

The TableLookup Function

The TableLookup function enables the calculation of an amount from a table. Typically this is used with tax tables, or other tables of tariffs. The normal tax calculation for South Africa for the 2008/09 tax year is based on this table (reproduced from the South African Revenue Services web site):

Read More »

Change the Case of a Value

Regardless of the case of the value entered into the interview or imported from a database, that value can be converted using the following commands into a different case on the assembled document:   ToUpper This will place the UPPER CASE value of the data into the document: «ToUpper(FullName)» “Fred

Read More »

The WindowsLogonUser Function

This function is used to gain access to the user name with which the person running the template logged on to Windows The person running this template is logged on to Windows with the user name: «WindowsLogonUser()». It is often used in conjunction with the SetSavedDocumentFolder and SetSavedDocumentFileName commands in

Read More »

The Define Command

Controlling the layout of your interview in your XpressDox template   XpressDox gives quite a lot of power to template authors in controlling the layout of the interview for a template.   Controlling the layout using multiple commands: For example, the layout commands for an email address might look something

Read More »

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

Read More »

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

Read More »

Filling PDF Forms

PDF documents which have been prepared with PDF Form Fields (using a suitable PDF Form editor) can be filled with data captured with an XpressDox interview.  In fact, the PDF form can be filled with data from ANY source, as long as it is in XML form. There are a

Read More »

Conditional Capture

The Conditional Capture feature of XpressDox will automatically hide merge fields on the data capture interview. This happens when the document assembly logic in the template renders a data element to be irrelevant in a particular situation.

Read More »

The MergeTemplate Function

When XpressDox encounters a «MergeTemplate()» function while running a template, it will keep the template name (which is passed to the function) in a list, called the Templates to Merge List.  After completing the main template, all the templates in the Templates to Merge List will then be run, using

Read More »

Version 3.3.2 (2011/01/06)

A bug which caused a conflict between «Script()» commands and «BaseTemplate()» has been fixed. At the same time, nesting of «UseScript()» within a «Script()» … «ScriptEnd()» is now supported The sample collections process demonstration templates have been updated, and can be downloaded.

Read More »

The RunWordMacro Command

This command enables the template author to cause XpressDox to run a Word macro after the template has been merged. «RunWordMacro(AlignParagraphs,TranslateDoubleQuotes)» The above command will cause the two named macros (i.e. AlignParagraphs and TranslateDoubleQuotes) to be run after the template has been merged. The Delay Option XpressDox needs to accommodate

Read More »

The RunTemplates Command

The «RunTemplates» command enables the template author to specify that more than one template should be run. «RunTemplates(Letter,Contract,DebitOrder,FileCover)» The four templates Letter.xdtpx, Contract.xdtpx, DebitOrder.xdtpx and FileCover.xdtpx will be run, one after the other.  The user will be presented with an interview for each template being run, but each interview will

Read More »

The IncludeTemplate Command

An entire template file can be inserted into the document using the «IncludeTemplate» command. The included template can contain Fillpoint definitions and even issue further IncludeTemplate commands.  It is treated thereafter exactly as if the contents of that included template had been typed directly into the including template. Example: The description of

Read More »

Search for a file using the Explorer

The XpressDox Explorer does not contain an explicit “Search” function.  Nonetheless, you can search in the currently open folder for a file, using the Windows file system’s wild card syntax. The example below demonstrates how the wild card string *letter*.xdtpl will list all (and only) XpressDox templates with the string

Read More »

The Processing Phases of XpressDox

When running a template in XpressDox (i.e. in the Word add-in), you are interacting with five phases of processing. These are: Template normalisation. This process consists of merging the templates referred to in «BaseTemplate()» and «IncludeTemplate()» commands, and also «UseScript()» commands, into one comprehensive template.  All of the commands in

Read More »

Version 3.3.1

Some new commands have been added: SetSavedDocumentNameVersioning can be used to inhibit the default merged document name versioning feature.  In other words, by default if a merged document is saved and there is another document in the same folder with the same start to the name, then a tie-break digit

Read More »

The InterviewIsWizard Command

This command is used in conjunction with the Tab command and causes XpressDox to produce a “wizard” form of interview.   Command structure: «InterviewIsWizard(Yes)» The way this works is that the interview will contain a Next and Back button, which provide an alternative mechanism for the user to navigate from

Read More »

The SaveAsPDF Command

In the configuration of a template folder, the “PDF” option can be specified which will cause XpressDox to create a PDF version of every template merged from that folder. Sometimes not all templates are required to be merged and saved as PDF, and only selected templates should result in PDF

Read More »

The SetSavedDocumentNameVersioning Command

By default, when a merged document is saved by XpressDox, the folder in which it is saved is first searched for any files which have a name similar to the newly merged document’s name.  If any are found, then XpressDox makes sure that the new merged document is saved with

Read More »