Troubleshoot Mail-Enabled Field Problems: Field Attributes

When using fields to enable mail routing in workflow applications, using incorrect field values, incorrect parameters, or the wrong number of parameters can cause the workflow to fail. It is important to understand the action caused by setting reserved field values and some errors commonly encountered when designing workflow-enabled applications.

When building mail-enabled forms, you often use reserved fields that have built-in functionality. Many of the reserved fields work in tandem with one another, whereas others override the functionality of one another.

For example, if the MailOptions field is set to “1” and the On Close: Present Send Mail Dialog option is enabled within the Form properties box, the MailOptions overrides the current user's choice selected in the On Close: Present Send Mail Dialog check box. Therefore, if MailOptions is set to “1,” users can select Yes to save the document, No to close without saving, or Cancel to return to the document. The form will be routed regardless of the user's selection. In addition, when implementing mail routing, if the MailOptions field is set to “1” and the user triggers the document to be mailed by using a @MailSend function (possibly located within a button), the document is mailed twice.

Also, if the Sign, Encrypt, or SaveOptions fields are set to a value of “1,” they will override the form property On Close: Present Send Mail Dialog. Even though they override the values in the Send Mail dialog box, they do not change what is displayed within the dialog box.

If the Sign, Encrypt, or SaveOptions fields are set to a value of “1,” they override the user's setting in the Document Save dialog box.