XpressDox Support

Footing – XpressDox

The «Footing()» command can be used to place text below a data element on the interview. Use the Heading and Footing commands to bring some context to the fields on the interview, or insert breaks

Read More »

Format – XpressDox

When concatenating strings together (see Concatenating Strings), it is not always easy to visualize what the end result will look like. This is especially the case when the strings being concatenated are a mixture of

Read More »

FormatDate – XpressDox

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

Read More »

Most Often Used Commands

Learning XpressDox is a bit like learning a new language. It takes a little practice (and patience) to become fluent. Although there are many commands at your fingertips, this article addresses some of the most common ones. Start here and you will be well on your well to authoring great templates!

Read More »

FormatSeconds – XpressDox

If you have calculated (or been supplied) an elapsed time in seconds, then you can format that into a nicely legible format without having to divide by 60 for minutes, etc. «FormatSeconds(‘3675′,’HH:mm:ss’)» will render as

Read More »

FormatTime – XpressDox

If a value has been captured as a time of day, then it can be formatted and inserted into the merged document in a format desired by the template author.  For example, a user may

Read More »

GetDataset – XpressDox

This function was introduced to enable the entire dataset to be saved as a BLOB in a data base. Typically, this function will be used in the context of a SetDataSourceData function, something like this: «SetDataSourceData(‘StagingDataSource’,Guid(),

Read More »

Decide on data element naming conventions

Putting some thought into how you name your data elements has a huge pay off later on. The re-use of data is a big advantage in document automation but this can only be done if the data element names are the same. Consistency is key.

Read More »

GetListItem – XpressDox

This function is used to extract a value from a list. In the first example, the data element contains a number (an integer) which is used to get an item from a list, where the

Read More »

GetRegistryValue – XpressDox

This function does as its name implies: gets a value from the Windows registry. For example: «SetV(‘UserPrivileges’,GetRegistryValue(‘HKEY_CURRENT_USER\Software\VB and VBA Program Settings\Accounting\Options\UserPrivileges’)» This will get the registry value HKEY_CURRENT_USER\Software\VB and VBA Program Settings\Accounting\Options\UserPrivileges and put it into the

Read More »

Set Web Information for a Template

These commands will enable the template author to control the workflow around templates which are uploaded and run on an XpressDox server.   SendWebEMail You can provide as many of these commands as necessary. The

Read More »

GetValidFileName – XpressDox

The GetValidFileName function will examine a value for characters which are illegal in a file name, and either remove those illegal characters, or replace them with a string supplied to the function.

Read More »

Formatting individual data elements

Formatting functions can be applied to any data element name where the value of the data element is to be included in the resulting text, that is when the data element name would otherwise exist in a Merge Field all on its own, or inside a List command.

Read More »

Guid – XpressDox

This function returns a new GUID (Globally Unique Identifier) whenever it is called. The usages for GUIDs are discussed in various places, a starting point would be this Wikipedia article. An example of usage in

Read More »