1 Overview

When using bxp forms it may be necessary to mail a series of documents to a client.

bxp through its outcomes has the ability to facilitate multi-document creation. Then with the documents created include them as links in the body of an email and have the email sent out to a recipient.

This process also facilitates the in browser signature capture engine available for document creation In_Browser_Signature_Capture

What follows is how to set up and use this feature.

2 Setup

2.1 Initial steps

We need a form and some templates to play with to demonstrate the engine.

Create a form Start_Here_-_Building_your_first_form
Create a HTML template called HTMLTemplate1 Writing_HTML_Emails
Create a second HTML template called HTMLTemplate2 Writing_HTML_Emails
Modify the HTMLTemplate2 for in-browser signature capture In_Browser_Signature_Capture
Create an RTF template called RTFTemplate1 RTF_Templates_for_Outcomes
Edit the first outcome and rename the initial Outcome as MultiDoc Form_-_What_is_an_Outcome

2.1.1 Form build

Type : Blended
ID: 9
Basic - Text Box : Customer First Name (strCDA_9_field_0_1)
Basic - Text Box : Customer Surname (strCDA_9_field_0_2)
Basic - Email Box : Customer Email (strCDA_9_field_0_3)
Tidy up the field mapping, as per the question titles

The form should look like

2.1.2 HTMLTemplate1

Template Name : HTMLTemplate1
Publicly available : True
Enable Signature Capture: False

<font face="Arial" size="3">
Dear --strCDA_9_field_0_1--,<br /><br />
This is a <em>HTML</em> template email.<br /><br />
Kind regards,<br />
--strAgent_FirstName--
</font>

2.1.3 HTMLTemplate2

Template Name : HTMLTemplate2
Publicly available : True
Enable Signature Capture: False

<font face="Arial" size="3">
Dear --strCDA_9_field_0_1--,<br /><br />
This is a <em>HTML</em> template email.<br /><br />
Now the signatures<br /><br />
--bxp_Signature_Capture-- = This will be replaced with the first signature captured<br /><br />
--bxp_Signature_Capture_DateTime-- = This will be replaced with the date and time that the first signature was captured<br /><br />
<br /><br />
--bxp_Signature_Capture_Add1-- = This will be replaced with the second signature captured<br /><br />
--bxp_Signature_Capture_DateTime_Add1-- = This will be replaced with the date and time that the second signature was captured <br /><br />
<br /><br />
Kind regards,<br />
--strAgent_Firstname--
</font>

2.1.4 RTFTemplate1

Filename : RTFTemplate1.rtf

{\rtf1\ansi\ansicpg1252\deff0\nouicompat\deflang6153{\fonttbl{\f0\fnil\fcharset0 Calibri;}}
\viewkind4\uc1 
\pard\sa200\sl276\slmult1\f0\fs22\lang9 Dear --strCDA_9_field_0_1--\par
This is an \b RTF \b0 Template\par
Kind regards,\par
--strAgent_FirstName--\par
\par
}

2.2 Turn on the MultiDoc engine

The MultiDoc engine is activated by an outcome. Outcome edit the MultiDoc outcome.

Use MultiDoc engine : True
Notes : Please ensure that you create and select HTMLTemplate1, HTMLTemplate2 and RTFTemplate1 before proceeding.
HTML Templates Allowed : HTMLTemplate1 and HTMLTemplate2
RTF Templates Allowed : RTFTemplate1.rtf

2.3 Set the External Communications email

When we do finally send the email to the end customer we need to have our comms engine working

External From Address: multidocDemo@gmail.com
External To Field: strCDA_9_field_0_3 - Customer Email
External BCC Email address : your own personal address
External Subject : Whatever you like, can be useful to put a ref in there e.g. MultiDoc Demo - Wixi example Ref : [ [ --intCDA_9_Id-- ] ]
External Body :

Dear --strCDA_9_field_0_1--,<br />
This is the body of the HTML email in the outcome external communications.<br /><br />
--MultiDoc_Docs--
<br /><br /><br />
Kind regards,<br />
--strAgent_FirstName--<br />

3 Operation

3.1 Use and log a record

So now we're ready to using the engine. Job number one here is to log a record and choose the MultiDoc as our outcome.

You will then be transferred to the MultiDoc engine screen

3.2 Using the engine

From here you can use the options to generate

Form MultiDoc engine

Contents