The submit form action flags to be combined to express various characteristics of the action
Namespace: EvoPdf
Assembly: evohtmltopdf (in evohtmltopdf.dll) Version: 10.0.0.0
Syntax
Members
| Member name | Value | Description | |
|---|---|---|---|
| Default | 0 | The default value of the flags | |
| IncludeExclude | 1 | If clear, the Fields array specifies which fields to include in the submission. If set, the Fields array tells which fields to exclude | |
| IncludeNoValueFields | 2 | If set, all fields designated by the Fields array and the Include/Exclude flag shall be submitted, regardless of whether they have a value. For fields without a value, only the field name shall be transmitted. If clear, fields without a value shall not be submitted | |
| ExportFormat | 4 | Meaningful only if the SubmitPDF and XFDF flags are clear. If set, field names and values shall be submitted in HTML Form format. If clear, they shall be submitted in Forms Data Format | |
| GetMethod | 8 | If set, field names and values shall be submitted using an HTTP GET request. If clear, they shall be submitted using a POST request. This flag is meaningful only when the ExportFormat flag is set; if ExportFormat is clear, this flag shall also be clear | |
| SubmitCoordinates | 16 | If set, the coordinates of the mouse click that caused the submit-form action shall be transmitted as part of the form data. The coordinate values are relative to the upper-left corner of the field’s widget annotation rectangle. This flag shall be used only when the ExportFormat flag is set. If ExportFormat is clear, this flag shall also be clear | |
| XFDF | 32 | Shall be used only if the SubmitPDF flags are clear. If set, field names and values shall be submitted as XFDF | |
| IncludeAppendSaves | 64 | Shall be used only when the form is being submitted in Forms Data Format (that is, when both the XFDF and ExportFormat flags are clear). If set, the submitted FDF file shall include the contents of all incremental updates to the underlying PDF document, as contained in the Differences entry in the FDF dictionary. If clear, the incremental updates shall not be included | |
| IncludeAnnotations | 128 | Shall be used only when the form is being submitted in Forms Data Format (that is, when both the XFDF and ExportFormat flags are clear). If set, the submitted FDF file shall include includes all markup annotations in the underlying PDF document. If clear, markup annotations shall not be included | |
| SubmitPDF | 256 | If set, the document shall be submitted as PDF, using the MIME content type application/pdf. If set, all other flags shall be ignored except GetMethod | |
| CanonicalFormat | 512 | If set, any submitted field values representing dates shall be converted to the standard format | |
| ExclNonUserAnnots | 1024 | Shall be used only when the form is being submitted in Forms Data Format (that is, when both the XFDF and ExportFormat flags are clear) and the IncludeAnnotations flag is set. If set, it shall include only those markup annotations whose T entry matches the name of the current user, as determined by the remote server to which the form is being submitted. | |
| ExclFKey | 2048 | Shall be used only when the form is being submitted in Forms Data Format (that is, when both the XFDF and ExportFormat flags are clear). If set, the submitted FDF shall exclude the F entry. | |
| EmbedForm | 8192 | Shall be used only when the form is being submitted in Forms Data Format (that is, when both the XFDF and ExportFormat flags are clear). If set, the F entry of the submitted FDF shall be a file specification containing an embedded file stream representing the PDF file from which the FDF is being submitted |
See Also