Attributes list

Allows you to specify additional signature boxes on the PDF form. E.g.for Joint applications it needs the following data:
PAGE=p |

The template for the BCC address of the email. It can be either a static address or a variable from the merge data.

The template for the CC address of the email. It can be either a static address or a variable from the merge data.

The path the “merged” document is to be saved. If this document is to be saved in the database set this value to pDocuments

A file mask that can be used to build up a new file name for the “merged” document. It can contain any variable from the merge data i.e. [CON_SYSID]

The format the merged document is to be saved as. The options are: PDF, RTF, HTML, TXT, ODT, XPS or DOC.

The template for the From/Sender address of the email. It can be either a static address or a variable from the merge data.

The template for the From/Sender display name of the email. It can be either a static address or a variable from the merge data.

This allows you to specify the attachment is another merge template that needs to be merged before being added to the Email. The format of the parameter is: TemplateID^SendAsFileName

This is the HTML version of the Template message and can be a static string or contain variables from the merge data

This allows you to set the status that the pFulfilment record will be updated to, once the letter has been merged. If not specified it will default to COMPLETE.

This allows you to define the data mappings between the PDF form and the database, using the format:
PDF-FIELD |

A text string used by the merge process.

A Y/N flag to indicate whether or not you should overwrite any existing files.

This allows you to add a clickable checkbox to the PDF Form, using the values:
NAME=name |

This allows you to add a editable textboxto the PDF Form, using the values:
NAME=name |

The plain text version of the email message. It can be a static string or contain variables from the merge data.

This is used to set the priority flag of the email:
- 1 – Low
- 5 – Normal
- 9 – High

The page number onto which the "Sign here" box will be added.

The x location of the "Sign here" box.

Tthe y location the "Sign here" box.

The full path to the document that is to be used in the merge process.

This allows you to include a static file with each Template created. The format of the parameter is: OriginalFilename^SendAsFileName^CIDName^mode, where mode is either inline or attachment.
For letters these will hold the references to the images that have been embedded in the template.

The template for the subject of the email. It can be either a static string or contain variables from the merge data.

The template for the To address of the email. It can be either a static address or a variable from the merge data.