User Reference
User Reference
| Using fillpoints to include variable data September 13, 2009 Documents containing XpressDox syntax are called templates, and are constructed in Microsoft® Office Word with the fixed text typed as in any normal document, but the pieces of variable data are entered as Fillpoints. A Fillpoint is the name of the data element, enclosed inside the fillpoint delimiters, which are « and ». |
| Source and destination formatting September 14, 2009 When including part (or all) of one document into another, which is the basis of the |
| Using CaptureDataElement during data capture September 14, 2009 The background to this command probably needs a bit of experience in authoring more complex templates. Because XpressDox uses XSLT technology to format the documents, it is possible to use XSLT and XPath expressions to control some of the processing. |
| Notes on XpressDox syntax September 28, 2009 XpressDox Docussembly™ document assembly syntax is fairly straightforward, and by paying attention to these few rules you can ensure your templates work first time, every time. This articles describes the syntax rules for data element names, command names, and functions, and describes when to use quote marks. |
| Configuration for folder settings September 28, 2009 Every folder where templates can be stored, and from which they are selected with the Run Template function, can have a configuration saved in it. When a folder is selected as the Configuration for folder, it means that the configuration settings entered on the screen will be saved in that folder. |
| Merging configurations September 28, 2009 Although other systems have concepts like ‘Private Folders’ and ‘Shared Folders’, these concepts are not necessary as such in XpressDox, as they can be provided for, and more flexibly, by the combination of the features of Merged Configuration and Helper Folders. |
| Configuring office settings September 28, 2009 XpressDox Docussembly™ document assembly software allows you to configure your installation to centralize letterheads, clause libraries, data sources, and XpressDox Explorer. This is a powerful yet simple way to scale the benefits of XpressDox Docussembly™ across your organization. |
| Managing favorite templates September 28, 2009 This tab is only available for the Home folder. It enables the user to specify a number of templates that they use frequently, and these templates are then presented in the Microsoft® Office Word UI in a menu, so that the user can have quick access to them. |
| Standard data element configuration September 28, 2009 These are data elements that appear as data elements on standard templates. A typical example is the user’s email address and telephone extension on a letterhead. In order to save a user typing their own details into the data capture UI every time they run a template, the Standard Data Elements feature allows them to enter these details into the configuration of a folder. |
| Layout the interview form using headings and footings September 29, 2009 This command enables you to apply section headings to different parts of the data capture interview. |
| Delimiters: How to choose your own fillpoint delimiters September 29, 2009 It is possible for fillpoint delimiters to be re-defined on any given installation of XpressDox. The decision to do this needs to be taken seriously because as soon as any significant number of templates have been authored using a particular choice of Fillpoint markers, a change to the markers will require a change to all the templates authored up to that point. |
| Configuring data sources September 29, 2009 The Data Sources facility provides a way for data captured into some other system to be merged into templates. For example, users may wish to be able to have address and other contact information from Microsoft® Outlook inserted into letters. This would be achieved by defining the Outlook Contacts as a Data Source. |
| Advanced file handling September 29, 2009 As well as configuring the folders where documents and data are to be stored, the filename which will be given to the saved documents and data can be defined, using the ‘Pattern for saved file name’ described in configuring standard folders. |
| Configuring Helper Folders in XpressDox September 30, 2009 In XpressDox Docussembly™ document assembly software any number of Helper Folders can be configured. A typical example of a folder for which this type of shortcut is defined would be one in which letterheads or other standard templates like fax headers, etc. are kept. In this way these standard templates can be kept separately to the templates that use them. |
| Configuring standard folders September 30, 2009 The Document Save Folder will be the default folder to which documents produced by running a template will be saved. When a template has been run, the user will be asked to provide a name for the document via a Save File dialog, and at that stage will be able to change the place where the document is saved. |
| Using and storing variables September 30, 2009 Here are some examples to illustrate the concept which enables the results of calculations to be stored for further use in the template, and even for future templates. |
| Getting data from data sources into a template September 30, 2009 XpressDox document assembly software makes it easy to include data from a data sources, and using the ‘Refresh’ and ‘Save’ options with templates using data sources. |
| Data capture in XpressDox September 30, 2009 XpressDox has been designed to fill marked-up templates in two general situations: The first is when data is captured and stored as part of an application; and, the second is to assist users who use the system within Microsoft® Office Word to produce standard documents. |
| Using block commands in XpressDox Docussembly™ September 30, 2009 The |
| Formatting individual data elements September 30, 2009 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 Fillpoint all on its own, or inside a |
| The Caption Command October 1, 2009 Use the Caption command to change the name of the data element in the interview to make it something a little more readable |
| The List Command October 1, 2009 List the repeated items which appear in a <<ForEach>:> command |
| Min October 1, 2009 Calculate the minimum of two values |
| The SetSavedDocumentFileName Command October 1, 2009 Force documents to be saved with a specified file name |
| The Now Function October 1, 2009 Insert the current date and/or time |
| The Today Function October 1, 2009 Insert the current date |
| The Required Command October 1, 2009 The Required command indicates that a data element must be given a value in the interview. |
| The ComeHereAfterRun Command October 1, 2009 Places the cursor at the position of the ComeHereAfterRun command when the template has been run and the document is merged. |
| The SetSavedDocumentFolder Command October 1, 2009 Define the file path of auto saved documents |
| The If Command October 1, 2009 Automatically Include or exclude text from a merged document based on the answer set provided by the user |
| The Contains Function October 1, 2009 Test for a string anywhere in another string |
| The SetSavedDataFileName Command October 1, 2009 Force data sets to be saved with a specified file name |
| The Help Command October 1, 2009 This command can be used to provide help text for the XpressDox interview. |
| The ChooseFromFile Command October 1, 2009 The user of the template is given a drop down list which is populated from a text file. |
| The ExcludeFromIV Command October 1, 2009 Hide fields from the interview with the ExcludeFromIV command. |
| The SetSavedDataFolder command October 1, 2009 Define the file path of auto saved data sets |
| The Count Function October 1, 2009 The Count Command returns the number of repeated items inside a ForEach |
| The Debug Command October 1, 2009 Troubleshoot missing or floating End() commands |
| The StartsWith Function October 1, 2009 Test whether a string starts with a given string |
| Inserting templates with variable names October 1, 2009 In some situations, the name of a file to be included in the document is contained in the Data Set. In these cases, instead of |
| The ChooseUsingCheckBox command October 1, 2009 This command presents the user with a true or false checkbox |
| The EndsWith Function October 1, 2009 Test the end of a string |
| Customizing and using base templates October 1, 2009 Sometimes it would be useful to be able to customize a source template for more than just the letter body. For example, it may be that the Data Set contains data for more than one set of addressees and the source document needs to be able to indicate which of these addressees is to be included on the base template. |
| The BaseTemplate Command October 1, 2009 Letterheads are of special interest because they are used as the basis for many documents. With XpressDox it is possible to create one letterhead template, and by referring to it with the |
| The Footing Command October 1, 2009 Insert text below a data element on the interview |
| The Heading Command October 1, 2009 Place text above a data element on the interview |
| The ChooseFromSamples Command October 1, 2009 The ChooseFromSamples command is used to present the user with a list. The user may either select one of the existing samples or type in their own value. |
| The ChooseFromData Command October 1, 2009 Choose the value of a data element from a data source |
| The ChooseFromRDBList Command October 1, 2009 Present the user with a list of choices in the form of ‘Radio Buttons’ |
| The ChooseFromList Command October 1, 2009 Instead of capturing a value for a data element, the ChooseFromList command can be used to present the user with a list of options for the value of a data element |
| The CaptureDataElement Command October 1, 2009 Capture a data element, without it appearing at that point in the document, for use in If/When conditions or to rearrange the order of the questions in the interview |
| The CaptureAsLongText Command October 1, 2009 Use the CaptureAsLongText Command to place a multi-line control on the interview into which data can be captured |
| RemoveParagraph: remove unwanted paragraphs October 5, 2009 Although XpressDox does a lot to make sure it leaves no unwanted empty paragraphs behind, it is sometimes necessary to manually remove the unwanted paragraphs. The RemoveParagraph() command will empower the template author to do this. |
| ForEach, List, Ordinal: Handling repeating data October 10, 2009 The central issue with repeating data is that the number of repeated data elements is not known at the time the template is authored, and so XpressDox offers the ForEach, List and Ordinal commands as a way of processing a variable number of repeated data elements. |
| XML and Data Sets October 13, 2009 XpressDox merges XML data into templates to produce a final merged document. This article discusses the concept of a Data Set and how XpressDox handles and even constructs Data Sets. |
| Using XSLT functions October 14, 2009 XpressDox uses XSLT technology to insert data elements into Fillpoints. This means that a vast amount of functionality is available to the experienced user, especially the XSLT functions, which are used to format data. XpressDox functions and XSLT functions can be mixed in one Fillpoint |
| Caption command: provide a useful name for data capture October 16, 2009 Names of data elements can sometimes not be very descriptive, and so their usefulness as labels of data capture controls is debatable. The Caption command empowers the template author with a tool for providing understandable names to data elements on the data capture interview. |
| Using Tabs to control the layout of the interview October 27, 2009 With the Tab command the template author can split long or complex data capture interviews by use of Tabs in XpressDox Docussembly™ document assembly software. |
| The Max Function November 1, 2009 Calculate the maximum of two values |
| Trouble Shooting XpressDox Startup November 16, 2009 This article provides guidance on possible solutions when XpressDox does not load, either immediately after installation, or at a later stage. |
| GetValidFileName function – removes or replaces illegal characters from a file name November 28, 2009 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. |
| The CreateDataElement Command November 28, 2009 The CreateDataElement function adds a new data element to the data set for the template. |
| Conditional Capture January 28, 2010 The Conditional Capture feature of XpressDox will automatically hide fillpoints 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. |
| The RenderAsNumeric function January 28, 2010 The calculation features of XpressDox require that values conform to a specific format. This format permits numeric digits, an optional leading sign (+ or -) and an optional decimal point. Thousands separators, spaces and other such characters are not permitted. The RenderAsNumeric function assists with this. |
| Conditional processing – If, Else, When January 29, 2010 Text can be included in or excluded from the merged document depending on the value of one or more data elements in the data set. |
| Set a Custom Document Property March 3, 2010 Using the SetCustomDocumentProperty command in an XpressDox template, a Word Custom Document Property can be defined in the merged document. |
| How to Convert Numbers to Currency May 11, 2010 An amount of money can be stored as a numeric value, and rendered as a natural language phrase when needed. The |
| What is the difference between Commands and Functions June 5, 2010 Commands and functions appear the same, but their functionality is different and in some cases this difference is important. |
| The Comment command June 5, 2010 Sometimes a template author will want to record the reasons for using specific commands or document logic, and record this inside the template itself. The Comment command is available for this. |
| The SetInitialValue Command June 5, 2010 The SetInitialValue command enables a template author to provide an initial value for a data element to be captured in the interview screen. |
| The SetMultipleDocumentFilter command July 15, 2010 The SetMultipleDocumentFilter empowers the template author to designate a filter which will apply when the Document per Repeated Item is used. |
| The ExtractInitials Function July 20, 2010 It is unkind to a user to expect them to fill in the full names of a person and then to type in the initials of that person. The ExtractInitials function relieves the user of this burden. |
| The FormatNumber Command July 20, 2010 A numeric value can be formatted in many different ways under control of a pattern string. |
| The CountOf Command July 27, 2010 The CountOf function returns the number of occurrences of one string within another. |
| The Script Feature October 4, 2010 The <<Script()>> command enables the template author to give a name to a chunk of text, and to use that chunk repeatedly in a template by using the <<UseScript()>> command where the chunk is required. |
| The Rule Command October 4, 2010 Using the <<Rule()>> command the template author can make sure that data values entered by the user in the interview for a template are syntactically correct and to some extent that they are consistent with each other. |
| The CurrencySymbol command October 4, 2010 The CurrencySymbol command aids in the internationalisation of a template in that the currency symbol is not hard coded in the template. |
| The RequiredVersion Command October 4, 2010 Running a template on an old version of XpressDox might give rise to confusing error messages if new features are used. |
| Trouble Shooting Office 2010 Installations October 12, 2010 Installing XpressDox for Word 2010 can fail if the version of XpressDox which was downloaded was for the Word 2010 version of the other “bitness” |
| The InterviewTitle Command October 19, 2010 The InterviewTitle command can be used to set the title to something more meaningful to the user than the default title |
| Multi-language Support November 30, 2010 XpressDox supports the user-facing interface in the language of the user. Bi-lingual interviews are also supported. |
| The RestrictToLicenses Command December 21, 2010 A reseller who invests a lot of time into a set of templates may want to protect those templates from being used by unauthorised users. The RestrictToLicenses command helps with this. |
| The Trim Function December 21, 2010 Leading and trailing white space can be removed from a value using the Trim function |
| The SetSavedDocumentNameVersioning Command December 21, 2010 The default system behaviour resulting in multiple versions of merged files being saved into a folder can be switched off by the SetSavedDocumentNameVersioning command. |
| The SaveAsPDF Command December 21, 2010 A template author can specify, by template, which templates should be merged and saved in PDF format using the SaveAsPDF command. |
| The InterviewIsWizard Command December 23, 2010 The user can be presented with a series of interview forms that are navigated via Next and Back buttons. |
| The Processing Phases of XpressDox December 28, 2010 There are a number of processing phases performed when a template is run. Understanding these phases is useful when using the advanced file handling and other features of XpressDox. |
| The IncludeTemplate Command January 3, 2011 Insert an entire template in the document |
| The RunTemplates Command January 3, 2011 Related templates can be run with one command using <<RunTemplates>> |
| The RunWordMacro Command January 3, 2011 The RunWordMacro command will cause the named macros to be run after the template and data have been merged. |
| The MergeTemplate Command January 22, 2011 While a template is being run, the MergeTemplate function can be used to cause further templates to be run after that template has been completed. |
| Testing parts of a string January 22, 2011 There are various ways that XpressDox functions can be used to test the contents of strings and manipulate strings. Some examples are given. |
| The Define Command March 30, 2011 Using the <<Define()>> command, the template author can define the interview layout properties of a data element. |
| The WindowsLogonUser Function April 14, 2011 The WindowsLogonUserFunction enables the template author to gain access to the Windows® user name with which the person running the template logged on to Windows®. |
| Change the Case of a Value April 14, 2011 Various functions are available which change the case of values |
| The TableLookup Function April 14, 2011 This function provides a table lookup mechanism for retrieving values from a table of values. |
| The StartsWithVowel Function April 14, 2011 This function aids in selection of the correct definite article in a sentence. |
| The Replace Function April 14, 2011 Replace all occurrences of one string in a source string with another string. |
| The NumberPhrase Function April 14, 2011 This function converts number to words in various languages |
| The Now and Today Functions April 14, 2011 The Now function inserts the current date and/or time into the document. |
| The Max and Min Functions April 14, 2011 Max and Min calculate the maximum and minimum, respectively, of two numbers. |
| The FormatDate and IncrementDate Functions April 14, 2011 Dates can be formatted in many different ways and languages. |
| The HardSpace Command April 14, 2011 This function converts spaces to “hard” or non-breaking spaces. |
| The GetListItem Function April 14, 2011 Extract an item from a list given the number of the item. |
| The Ordinal Command April 18, 2011 Use the <<Ordinal>> to return the ordinal value (first, second, third) of an item in a list |
| The IncrementV Function April 18, 2011 This function will add a value to the value of an XpressDox variable. |
| The OrdinalSuffix Function April 18, 2011 The “th” in “25th December 2011″ can be produced using the OrdinalSuffix function. |
| The Gender Function April 18, 2011 The Gender function enables the template author to insert the correct gender-related pronouns in the finished document. |
| The Plural Function April 18, 2011 |
| Filling PDF Forms July 4, 2011 XpressDox can fill PDF forms with data from an XpressDox interview, or any other data. |
| The LinkToDataSource Command July 5, 2011 Any control on an XpressDox interview can be linked to a data source so that data in that control, or any other control, governs which data is to be retrieved. |
| The Hyperlink Command July 5, 2011 Attach a hyperlink to a heading or footing in the interview. |
| The OptimizeParsing Command July 5, 2011 Optimized parsing can be switched off using this command, for particular situations which warrant it. |
| The ChooseFromDataSource Command July 7, 2011 This command will create a control in the interview that allows the user (when the template is being run) to choose the data from a data source. |
| The SendWebEmail Command July 20, 2011 Upon the completion of a document generated in the cloud, an automated email can be sent using the <<SendWebEmail>> command |
| The SetWebReturnURL command July 20, 2011 Specify a result page after the document has been assembled |
| The SetWebButtonText command July 20, 2011 This command allows the template author to change the text of the ‘Assemble’ button at the end of the interview |
| The PlaceHolder Command July 27, 2011 A PlaceHolder can be used to include conditional headings and/or footings on an interview. |
| The ShowIfHasValue Function July 27, 2011 Sometimes, if a data element has an empty value, then the paragraph containing that data element should be removed from the merged document. The ShowIfHasValue function achieves this. |
| Set Web Information for a Template October 25, 2011 Control the emailing of documents and data sets, setting the button text for the Assemble Document button, and setting the return URL are possible with this set of commands. |
| The SetInterviewDataOnly Command October 25, 2011 A typical usage of this would be in conjunction with the MergeTemplate function, where the template is a master template and based on the values of data input by the user, different templates are merged. |
| The RegionToX and XToRegion Functions February 15, 2012 Calculations using numbers which are not in XSLT-compliant format need the intervention of the RegionToX function. |
| Relevance February 16, 2012 Construction of the XpressDox interview involves algorithms which determine whether or not data elements should appear on the interview, in other words the relevance of each data element. |
| The CaptureAllDataElements Command February 16, 2012 In the context of “relevance”, sometimes the template author would like all data elements mentioned in the template or assembly to be captured, regardless of whether their values are used in the construction of the merged document or not. |
| The ChooseUsingDatePicker Command February 16, 2012 Specify that when a data element appears on the interview it should have the date picker control. |
| The DaysBetween Function February 16, 2012 Get the number of days between two dates. |
| The Empty Marker February 16, 2012 Define a coded string which will be placed in the merged document when the data element in a fillpoint is empty. |
| The ExcludeFromDataSet Command February 16, 2012 Exclude data elements from the saved data set. |
| The IncludeCodeTemplate Command February 16, 2012 When the code template is included using this command, then any of the paragraphs in the included template which contain no XpressDox fillpoints are removed from the document. |
| The LinkToOtherData Command February 16, 2012 When the user enters a value in a control in the interview, the equivalent of pressing the User Other Data button is performed. |
| The OnExitSet Command February 16, 2012 The value of a data element, caption, footing or heading can be set in the interview, depending on the value of data entered by the user. |
| The ReadOnly Command February 16, 2012 The value of the data element will be shown in the interview, but the user will not be allowed to modify it. |
| The RepeatWhile Command February 16, 2012 Allows iteration through repeated values in a single data element. |
| The Round Function February 16, 2012 Round a value to the nearest integer, or fraction. |
| The SaveAsText Command February 16, 2012 XpressDox can create files which are not necessarily Word documents, such as XML, HTML, CSV, or any text format. |
| The SetRepeaterQualifier Command February 17, 2012 Build up a meaningful signature for repeating elements in the interview. |
| The HideEmptyInterview Command February 23, 2012 Empty interviews can be suppressed using the HideEmptyInterview command. |
| The EscapeForXml and GetValidXmlElementName Functions March 1, 2012 XpressDox can be used to transform an XML document to another format. The two functions covered here will make the task possible. |
| The ChooseFromDataElements Command April 13, 2012 A drop down list of values sourced from the current data set can be presented in the interview. |
| The Chr Function April 13, 2012 This function can be used to return a character based on its numeric value. |
| The CaptureOnlyEmptyValues Command April 13, 2012 This command presents an interview which contains only those data elements which are empty. |
| The YearsBetween Function April 26, 2012 The age of a person can be calculated using YearsBetween |