Suppose you would like to write a sentence something like one of the following, depending on the age of a child: My child <ChildName> is a teenager and is allowed to watch movies rated for 13 and older. OR My child <ChildName> is not a teenager but in any case, being <Age>,
Sometimes it is syntactically impractical to use the characters < and > in a particular context. For example, you might want to use a Dynamic Caption which is something like this (to use the word “names” or “name” in the caption depending on the number of children): «Caption(DependantNames,Enter the <IIf(count(Child)
The style (i.e. bold, italic and/or underline) and color of a Caption or Heading can be set to enhance the usability of the XpressDox data capture interview.
Suppose you want to get the date of the last day of a month. There are a number of ways to achieve this with XpressDox. With version 8.2.1 of XpressDox, this can now very easily be achieved using the LastDayInMonth function. Brute Force Method Assume that you have a data
XpressDox will create a data capture interview automatically, using the data elements defined on the template. The sequence in which the data elements appear on the interview can be controlled with the CaptureDataElement command, and the Heading and Tab commands can assist with further layout.
The official XpressDox Cookbook contains various recipes for different aspects of XpressDox. It is intended to complement the User Reference. The latter document is comprehensive in that it covers all of the XpressDox commands and functions, but does so to a limited depth. The Cookbook is designed to give in-depth coverage of certain commonly used aspects.
Conditional processing is one of the most powerful features of XpressDox Docussembly™. In particular, this applies to removing empty lines from a merged document. One application of this is removing address lines which contain empty data.
Sometimes a letterhead needs to dictate not just things like the company’s logo and fairly static items like the directors’ names, but also the position of the addressee information and data elements like ‘Your Reference’ and ‘Our Reference’, for example.
You may not want to have to define 3 or 4 or some maximum number of address line data elements, and have the user capture them one at a time, and still provide conditional formatting logic to suppress any empty data elements. XpressDox document assembly supports this by the concept of long text fields.
Sometimes you will have marked up a template and then when you run it, one or more of the data elements don’t appear in the data capture interview. Conversely, sometimes the data element may appear in the capture interview but not on the merged document. This Cookbook recipe gives the background to why this might be, and what you can do about it.
After data sets have been saved as a result of running templates, it is possible to use those data sets, either individually or in batches, to produce mass mailing documents.
It is sometimes necessary to test whether at least one (Any) of a group of repeated items meets a particular set of criteria, and also to test whether All of the group meet those criteria. This article discusses how to construct those tests.
Often the name of a data element is descriptive enough to for a user to know what to enter when capturing data. But sometimes more help is needed. XpressDox has a number of mechanisms available for the template author to provide the user with help in capturing data, in particular using the Help command.
There was a change in Version 4 with the style handling with BaseTemplate, IncludeTemplate and InsertTemplate template. How it worked in version 3 of XpressDox With version 3, when Source formatting was used, XpressDox would create a new style in the destination template for every style in the source template, but
The contents of this article apply to Version 4 (and later) of XpressDox. Enhanced calculation support has been added in Version 9. If you have that version installed and are licensed for it, rather read Arithmetic in XpressDox XpressDox uses a technology called XSLT at the core of its assembly
Enterprises lose credibility and brand awareness when published documentation is out of date or inconsistent. XpressDox Docussembly™ document assembly makes it possible to ensure consistent use of branded documents throughout the enterprise.
XpressDox does not integrate with document management (DM) systems, in the strict sense of the word. However, there are various tools available to the template author to make cooperation with a DM almost seamless. Configuration Firstly, the configuration can be set up to stop XpressDox from saving the merged documents
Some of the sample templates which are delivered with XpressDox make use of one of the early instances of the Microsoft AdventureWorks SQL Server database. This database can no longer be obtained from any Microsoft web site, and so a backup is made available here. You can download the .zip