Difference between revisions of "Form MultiDoc engine"
From All n One's bxp software Wixi
Philip Lacey (talk | contribs) (Created page with "= 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 crea...") |
Philip Lacey (talk | contribs) |
||
| Line 29: | Line 29: | ||
* Modify the HTMLTemplate2 for in-browser signature capture [[In_Browser_Signature_Capture]] | * Modify the HTMLTemplate2 for in-browser signature capture [[In_Browser_Signature_Capture]] | ||
* Create an RTF template called RTFTemplate1 [[RTF_Templates_for_Outcomes]] | * 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]] | ||
| Line 39: | Line 40: | ||
* Basic - Email Box : Customer Email | * Basic - Email Box : Customer Email | ||
* Tidy up the field mapping, as per the question titles | * Tidy up the field mapping, as per the question titles | ||
| + | |||
| + | The form should look like | ||
| + | [[File:multidoc_engine_001.png|800px;]] | ||
| + | |||
=== HTMLTemplate1 === | === HTMLTemplate1 === | ||
| + | |||
| + | |||
| + | * Template Name : HTMLTemplate1 | ||
| + | * Publicly available : True | ||
| + | * Enable Signature Capture: False | ||
| + | |||
| + | |||
<syntaxhighlight lang="html4strict" > | <syntaxhighlight lang="html4strict" > | ||
<font face="Arial" size="3"> | <font face="Arial" size="3"> | ||
| Line 53: | Line 65: | ||
=== HTMLTemplate2 === | === HTMLTemplate2 === | ||
| + | |||
| + | |||
| + | * Template Name : HTMLTemplate2 | ||
| + | * Publicly available : True | ||
| + | * Enable Signature Capture: False | ||
| + | |||
| + | |||
| + | <syntaxhighlight lang="html4strict" > | ||
<font face="Arial" size="3"> | <font face="Arial" size="3"> | ||
| − | Dear -- | + | Dear --strCDA_9_field_0_0--,<br /><br /> |
This is a <em>HTML</em> template email.<br /><br /> | This is a <em>HTML</em> template email.<br /><br /> | ||
Now the signatures<br /><br /> | Now the signatures<br /><br /> | ||
| Line 66: | Line 86: | ||
--strAgent_Firstname-- | --strAgent_Firstname-- | ||
</font> | </font> | ||
| + | </syntaxhighlight> | ||
=== RTFTemplate1 === | === RTFTemplate1 === | ||
| + | |||
| + | |||
| + | * Filename : RTFTemplate1.rtf | ||
| + | |||
<syntaxhighlight lang="xml" > | <syntaxhighlight lang="xml" > | ||
{\rtf1\ansi\ansicpg1252\deff0\nouicompat\deflang6153{\fonttbl{\f0\fnil\fcharset0 Calibri;}} | {\rtf1\ansi\ansicpg1252\deff0\nouicompat\deflang6153{\fonttbl{\f0\fnil\fcharset0 Calibri;}} | ||
\viewkind4\uc1 | \viewkind4\uc1 | ||
| − | \pard\sa200\sl276\slmult1\f0\fs22\lang9 Dear -- | + | \pard\sa200\sl276\slmult1\f0\fs22\lang9 Dear --strCDA_9_field_0_0--\par |
This is an \b RTF \b0 Template\par | This is an \b RTF \b0 Template\par | ||
Kind regards,\par | Kind regards,\par | ||
| Line 80: | Line 105: | ||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| + | |||
| + | |||
| + | |||
| + | == 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 | ||
| + | |||
| + | |||
| + | [[File:multidoc_engine_002.png|800px]] | ||
| + | |||
| + | |||
| + | |||
| + | [[Category:Module Specific:Form Management]] | ||
| + | [[Category:Topic:Outcomes]] | ||
| + | [[Category:Topic:Mail Merge]] | ||
Revision as of 17:16, 10 September 2016
Contents
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
- Basic - Text Box : Customer Surname
- Basic - Email Box : Customer Email
- 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_0--,<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_0--,<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_0--\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
