...
You can enter multiple comma separated addresses To, Cc, Bcc and a single Reply To address. The email address may either be a static address such as info@frevvo.com or a dynamic address by using template syntax such as {person}@frevvo.com if you want the name dynamic and the domain static or {emailAddress} to make the full email address dynamic.
We suggest you uncheck "Send Data" if you don't need the xml attachment. Also leave the "Send Snapshot" dropdown blank if you do not need the form image attachment. Both options have small performance and memory overheads. So don't select them if you're not going to use these attachments.
...
| Code Block |
|---|
<center>
<a href="javascript:void(0);" onClick="window.open(document.location.toString().split('?')[0] +
'/service?_method=POST&target=http://[myhost]:[myport]/Myservices/service/print/myForm')">Print</a>
</center> |
...
Your transformation service should return html to the browser window. You can style the message control as a button by adding a border, background color and even dragging into a panel to size the "button".
Print View
All frevvo forms are printable. By selecting a form's [[V4_Designing_Forms#Printable_2 | printable checkbox]] a print 
icon will be displayed at the top of your form. When the form is used and the printer icon is clicked the form is rendered in a new browser tab in an HTML printable format.
See also [[V4_Using_Forms#Printing_Forms | Printing Forms]]
==== PDF Integration ==== Forms submission can be converted to PDF documents. The PDF document can be saved in frevvo's Submission Repository, sent as an attachment to a submission email, or as an attachment to a POST to a back-end system such as a document management system.
The [[V4_Designing_Forms#Form_.26_Doc_Action_Wizards | Form and Doc action wizards]] for email and post submission control whether or not the form is converted to a PDF document and attached to the submission. You can control which form fields are added to the PDF via the [[V4_Designing_Forms#Printable | printable property]] on each field in your form.
=== Document Service ===
frevvo's built-in document service can be used for processing your form data prior to submission.
The document service is accessed via the Url /service. It supports the following parameters:
* '''method=POST''' -- required and should be left POST * '''target=[url]''' -- [url] is the path to your servlet
The target will be passed name/value pairs of all of the controls in your form with their current values. The target will also be passed the collection of xml documents comprising the form's current data. The collection will include at least one document in the namespace 'form' which contains all the data in controls added to the form from palette. The collection will also include one xml document for each data source added to the form.
==== Custom Print View ====
One example use of frevvo's document service is to provide a print preview different from frevvo's default print view.
All forms by default are printable. To make a form printable edit the form and check the [[V4_Designing_Forms#Printable_2 | printable property]]. Sometimes form designer required a highly customized print view. By calling frevvo's document service you can pass all the form's xml documents to another target servlet that transforms the data into exactly the format you need and then returns html to another browser window.
To do this:
* Add a message control to your form * Add the following html to your message control
<pre> <center> <a href="javascript:void(0);" onClick="window.open(document.location.toString().split('?')[0] + '/service?_method=POST&target=http://[myhost]:[myport]/Myservices/service/print/myForm')">Print</a> </center> </pre>
Your transformation service should return html to the browser window. You can style the message control as a button by adding a border, background color and even dragging into a panel to size the "button".
=== Integrating with REST applications ===
...
Integrating with REST applications
From the point of view of the user interface, most web applications can be thought of simply as CRUD (Create, Retrieve, Update & Delete) operations on documents. In the diagram below, the form is being used to initially display a Customer and Order and then to update them. If you think in REST terms, the form is a View Resource that composes multiple Entity Resources (in this case a Customer Resource and an Order Resource), displays their current state and allows you to update them.
[[Image:Compose_Documents.jpg]]
...