Use Google to find help fast. For example, search on "xpressdox choosefromlist".

The MaximumRepeats Command

There are times when you have a repeater but you do not want the user to be able to add more than a certain number of instances of the repeater in the interview.

You could use a Rule command, but then the user will only get the message once they have pressed the “OK”, or “Assemble” button.

The command

«MaximumRepeats(Child,3)»

would prevent the user from entering more than 3 Child instances in the interview.

The command is very flexible, and supports a function or data element in the second argument. This makes it possible to have a different MaximumRepeats for different situations.

For example, you could say that if there is no Parent value, then the number of children should be zero, otherwise the maximum should be 2, like this:

«MaximumRepeats(Child,IIf((Parent = ''),0,2))»

For completeness sake – the Required command will ensure that at least one Child is entered, if that’s what is needed:

«Required(Child)»«MaximumRepeats(Child,3)»

This would ensure that at least one but at most 3 Child elements would be input in the interview.

The PdfUserPassword Function

This function gives you the ability to provide a user password to a PDF that is created by running a template. In other words, a person wanting to open the PDF file produced will have to supply the password to the application (e.g. Adobe Acrobat) which is being used to open the document.

As an example:

«PdfUserPassword(FormatDate(DateOfBirth,'yyyyMMdd'))»

This will create the user password which is the date of birth provided in the interview.

The template will also need the «SaveAsPDF()» command to be present in order for the feature to take effect.

The DateAsNumber Function

If you want to compare two dates, then typically you want to know whether one date is later than another. The default way that dates are stored in XpressDox is in the format yyyy-MM-dd (e.g. 2018-05-02), but can also be understood by XpressDox in other formats, like “May 2, 2018”. The hyphens or other non-numeric characters inside the date means that the only comparison that can be made between two dates is whether they are equal or not. In order to compare two dates to see which one is before or after the other, the dates need to be made into numbers.

This could be be done by the following:

«If(FormatDate(Date1, ‘yyyyMMdd’) < FormatDate(Date2, ‘yyyMMdd’))»Date1 is less than Date2«End()»

The DateAsNumber function is a shortcut for the above (which is open to "finger trouble" and mis-typing), as follows:

«If(DateAsNumber(Date1) < DateAsNumber(Date2))»Date1 is less than Date2«End()»

Saving Assembled Documents into iManage

Configuration

All that is needed for this feature to be enabled is that a drive letter be configured to refer to the iManage system.  This configuration operation can be accomplished by a user with a Supervisor license, which will give the user access to the Foreign File Systems tab in the XpressDox configuration screen.

 

Choose the Foreign File Systems tab, click the Add New button on the left, and then enter the name and drive letter that you would like to use. The name is purely a description, and any drive letter that you know is unused can be chosen.  You will see that two file systems are currently supported, i.e. Windows and iManage – but Windows is disabled as this is the default and it is not necessary to define the Windows file system for any drive letters.  But you do need to choose the iManage radio button.

It is then necessary to click the Use File System’s Editor button which will present you with a form to complete.

 

Notice that the various fields can contain the <> syntax – in the above example the values of the iManageUserName and iManagePassword data elements which are active at the time access to the iManage system is done will be filled in.

After saving the configuration, you can then press the Test button to make sure the information has been configured correctly.

Addressing the iManage System

Once this configuration has been done, saving assembled documents into iManage is done just by specifying the path to the folder or sub-folder and using normal syntax for a file path for the Windows file system. For example

The file name will be provided either by a command in the template, or will default to the template file name with a .docx extension.

There are many “profile properties” that can be set for a document in the iManage system.  XpressDox will default some of them, but all of the defaults, plus the custom properties, can be set inside the template using the SetCustomDocumentProperty command, as in the following examples, that set the custom1 and custom3 properties for the document:

«CreateDataElement('Custom1','MYCUSTOM1-2')»

«SetCustomDocumentProperty(XDFsProf-custom1,<Custom1>-1)»
«SetCustomDocumentProperty(XDFsProf-custom3,MYCUSTOM3-1)»

Note that XpressDox will regard custom document properties with the name starting with XDfsProf- as being applied to document management systems, and the part of the name following that prefix is the name of the DMS profile property.

 

The GetDataset Function

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(), 'XMLBlob',GetDataset(), 'Description',Name)»

In the above, the value of the Guid() function would be used as an arbitrary, unique, ID of a staging table, XMLBlob is the name of the BLOB column into which the data set (from GetDataset()) is written, and the Description and Name are the name and value (respectively) to be written into another column in that row in the table.

The ApplyRulesToDataset Command

It may be that all, or at least some, of the data set to be used to assemble a document comes from some place other than the interview.  For example, it might be that the data are in a data base, or retrieved from a web service or some other data source.  Often data sets like this can contain data elements which are wrongly formatted or which in some other way do not conform to the business rules for the template that is being run.  In this case it might cause a dangerously inaccurate document to be assembled from the data and template.

The ApplyRulesToDataset command will cause all the Rule commands to be executed against the data set, regardless of whether there is an interview or not.

The Rules will be evaluated just before the data set is passed to the assembly engine where the data set is merged into the template. If any of the rules fail, then an error message will be displayed and the assembly terminated.

The ApplyRulesToDataset takes one argument, with the following meanings:

  1. «ApplyRulesToDataset(Yes)»: the command will be applied.
  2. «ApplyRulesToDataset(IgnoreSoftRules)»: any “soft” rules (see Tips and Hints using the Rule Command) will be ignored.
  3. «ApplyRulesToDataset(No)»: the command is ignored completely.

 

The AppendPDF Command

AppendPDF enables the user, and also the template author, to choose one or more PDF files which will be appended to the document assembled by the template in which the command appears.  The SaveAsPDF(Yes) command is issued implicitly.  In other words, PDF files can only be appended to other PDF files.

Example – user supplies the file name

«AppendPdf(PdfFileName)»

will present the user, in the interview, with a place to enter the name of the PDF file to be appended.

Example – template author supplies the file names

«AppendPdf(‘.\ClauseFiles\Pdf File.pdf|.\ClauseFiles\Test Proposal.pdf’)»

will cause the two files Pdf File.pdf and Test Proposal.pdf to be appended to the assembled document. Note that the “pipe” symbol is used to separate files in the list of files to be appended.

The Data Set Data Source

When you have a system of templates and have run them a number of times, say for a number of your customers, the saved data set files become a source of valuable information.  It would be nice to be able to access those data files as though they were a database.

That’s what the XpressDox Data Set Data Source will do for you.

You configure the data set data source in much the same way as any other data source – via the XpressDox configuration.

Choose the New Data Source button and you will be presented with a list of choices.  Towards the end, on the right, is the radio button with the caption “XpressDox Data Set Data Source”.

Choose that and press “Finish”.

After that, you will need to give the data source a name, press Tab and then press the Use Data Source’s Editor button to edit the Definition String.

Once you’ve pressed that button, then the really exciting work starts. You will see a form like this:

Pressing the little “?” on the top right of the form will give you some help on the different options.

In the end, a picture is worth a thousand words, and the best way to find out what this data source does is to try out various options and test the result (with the “test data source” button, or just double-click the data source name) and see what XML structure is created. Thereafter you will probably know quite well how to address the data inside a template.