| |
|
| |
Specifies which datagroups are filtered when the form is transmitted. |
| |
|
| |
Specifies the format a form will be saved in. An XFDL form may be saved as XFDL compressed or uncompressed formats. |
| |
|
| |
Specifies individual items that are filtered for a particular transmission. |
| |
|
| |
Specifies which groups are filtered for a particular transmission. |
| |
|
| |
Specifies types of options that are filtered for a particular transmission. |
| |
|
| |
Specifies types of items that are filtered for a particular transmission. |
| |
|
| |
Specifies individual options that are filtered for a particular transmission. |
| |
|
| |
Signature and transmission filters are applied with an order of precedence. This prevents potential filter conflicts, in which one filter might stipulate that you omit an item while another filter might stipulate that you keep an item. |
| |
|
| |
Specifies individual pages that are filtered for a particular signature. Filtering pages means keeping or omitting a page and all of its contents. |
| |
|
| |
Provides the url to a target, such as a file or application. |
| |
|
| |
Identifies the item that triggered a form submission. Items triggering form submissions have a type option setting of refresh, submit, or done. |
| |
|
| |
Divides a portion of the form into sets of items, and then controls which set is shown to the user. For example, you may have a form page with Basic and Advanced settings, and may only want to show one type of settings to the user at any given time. |
| |
|
| |
Sets a button or action item to perform an XForms submission. The rules for the submission are defined in the XForms data model. The xforms:submit links a button to a particular set of rules, which are then carried out when the button is clicked. |
| |
|
| |
Optional: Only pertains if you are using XFormsReplaceAll. |
| |
|
| |
You can collect data from the form by creating a submission. A submission is initiated when the user has completed the form and is ready to submit it for processing. |
| |
|
| |
You can create a submit button that when clicked, sends the form to a server or to an email address. You can submit the entire form or you can create a filter that submits part of the form. |
| |
|
| |
Filtering is an advanced feature that allows you to control which parts of a form are sent when a transmission occurs. For example, you can filter all of the buttons out of a form, or filter out everything but the buttons. |
| |
|
| |
After you have created a submission, set the values of its properties. |
| |
|
| |
Before creating an XForms submit button, you should create an XForms submission for the instance that you want to submit. |
| |
|
| |
You can collect data from the form by creating a submission. A submission is initiated when the user has completed the form and is ready to submit it for processing. |
| |
|
| |
Filtering is an advanced feature that allows you to control which parts of a form are sent when a transmission occurs. For example, you can filter all of the buttons out of a form, or filter out everything but the buttons. |
| |
|
| |
Before creating an XForms submit button, you should create an XForms submission for the instance that you want to submit. |
| |
|
| |
You can create a submit button that when clicked, sends the form to a server or to an email address. You can submit the entire form or you can create a filter that submits part of the form. |
| |
|
| |
After you have created a submission, set the values of its properties. |
| |
|
| |
Optional: Only pertains if you are using XFormsReplaceAll. |