Forward

Follow

The Forward tool allows a mobile user with a dispatch license to forward a form to another user with a dispatch license or to an email address. The Forward tool is executed when the form is sent by User A and received by the doForms portal. At that time, the form is dispatched by the website to User B, who receives it as a normal dispatch.

Note the following:

  • While a forwarded record will be sent as a dispatch to User B, it does not create a new record in the Dispatch tab of the doForms portal.
  • A forwarded record does not affect the "Completed status" of a record completed by User A in the Dispatch tab.
  • While the form is being forwarded from one user to another, the most current version of the form is stored in the View Data tab. This means that, after forwarding, the data is safely stored in the doForms portal. Only the most current version of the form record is stored in the View Data tab throughout the process.
  • Forms that have been forwarded will appear in the Jobs tab of the mobile device. It is important to ensure that your form has a record name so that the second person sees information in the Jobs tab and not just the form name.
  • If you create a "Save and Send" Action button, you can select the Ignore required fields in forward option within the Action button settings. If you do not select this option, and the form has required fields, it will not let User A send the form until all required fields have been entered.
    When forwarding to an email address the account will be charged 1 credit per forward and 1 credit to submit. For exmaple, if USER1 forwards to example@doforms.com and then example@doforms.com submits the form, the account will be charged 2 credits.

**IMPORTANT** The forward tool is designed to be forwarded to one person at a time. If there is multiple forward tools in your form active at the same time the last user to submit the form will update any previous users submission of the same form. In other words, if User 1 forwarded Form A to User 2 and User 3 at the same time, both users would recieve the forwarded form. If User 2 submitted the form, the information they entered on the form would be viewable in View Data. But, if User 3 then filled out and submitted their forward after User 2 had submitted their forwarded form, User 2's data would be overwritten by User 3's data in the View Data Tab. Essentially no matter how many people recieve a forwarded form the last person who submits the form to the web portals will be visible.

Properties

Caption text: The caption is used in most cases to ask the question. In others it may be a column heading. This is a required field. Please keep in mind that captions will wrap when form elements do not fit within the width of the screen. It is important to consider how your captions will be displayed. Captions on a larger screen might look perfect, but on a smaller device, they may be forced to wrap several times. In this situation, a smaller caption should be used.

Hint: Provides additional information to the mobile form user on how a question (i.e., Caption text) should be answered. The Hint font size is smaller than the Caption font size.

Additional HTML styling can be applied on hints and captions.

Data name: Because this is a required field, doForms will default the Data name to match the Caption or Label. If these are blank, doForms will generate a generic Data name name with a sequential number (such as "untitled10"). Since it is used throughout the system, it is recommended that you enter a descriptive Data name that is easily identifiable. Nondescript Data names are difficult to find and select at a later time (e.g., when performing a calculation).

Default value (mobile ID): The mobile ID you wish to forward the form to. The mobile ID must be an integer value with no spaces or special characters. There are three ways to set the mobile ID:

  1. Type a mobile ID into this field as a default value.
  2. Leave the field blank, and prompt the user to enter a mobile ID.
  3. Use a lookup and set the Forward field as the destination field equal to the Mobile ID field in the lookup table.

Note that, to force a form to forward to a mobile user, type a mobile ID into the field, and then apply the desired Read-only parameters (described below). You may also want to hide this field by applying the desired Hide parameters (described below).

Turn off email: The system will suppress emails from being sent when User A submits the form. This will allow the email to only be sent by User B after the form is complete.

Return to Sender: The forward tool will automatically put the senders mobile number into the receipients forward tool. This setting is used when the forwarded form needs to return to the person who originally forwarded it.

Reset: The system will automatically clear the Forward form to field so that the form does not get sent back to the same person over and over again.

Length: If selected, allows you to set the minimum and maximum length of the forwarding mobile id.

Appearance: doForms allows you to set a default set of appearance parameters. This eliminates the need for you to have to set colors and other parameters each time you add an element to your form. You can however override the default settings for any tool by simply picking the Custom option. You can also edit the default by clicking on the edit defaults option.

Justification: Allows you to apply text justification settings to certain elements of the tool. Choose the appropriate radio button for the Caption, Hint, and/or Answer fields as follows:

  • L: Left-justifies the text.
  • C: Center-justifies the text.
  • R: Right-justifies the text.

Remove Space - This parameter is used to remove the space just before and just after the tool. By removing space two elements can be made to appear linked or as a single element.

Read only - These settings allow you to control which users can enter data into or edit this field. The settings are as follows:

  • View data edit: Restricts a web portal user from editing this field when editing a submitted form through the 'View data' tab
  • View data new: Restricts a web portal user from entering data into this field when filling out a new form through the 'View data' tab.
  • Dispatch edit: Restricts a web portal user from editing this field when editing a submitted form through the 'Dispatch' tab.
  • Dispatch new: Restricts a web portal user from entering data into this field when creating a new dispatch through the 'Dispatch' tab.
  • Mobile: Restricts a mobile user from entering data into this field when filling out a form.
  • Web App: Restricts a web app user from entering data into this field when filling out a form.
  • Form Links: Restricts a web portal user from editing this field when editing a form that was sent using a form link

Required - These settings allow you to control which users are required to enter data into this field. The settings are as follows:

  • View data edit: Requires a web portal user to enter data into this field if editing and saving a submitted form through the 'View data' tab
  • View data new: Requires a web portal user to enter data into this field when filling out a new form through the 'View data' tab.
  • Dispatch edit: Requires a web portal user to enter data into this field if editing and saving a submitted form through the 'Dispatch' tab.
  • Dispatch new: Requires a web portal user to enter data into this field when filling out a new dispatch through the 'Dispatch' tab.
  • Mobile: Requires a mobile user to enter data into this field when filling out a form.
  • Web App: Requires a web app user to enter data into this field when filling out a form.
  • Form Links: Restricts a user from submitting a form link without answering this this field.

Hide - These settings allow you to hide the form field from users in specific situations. The settings are as follows:

  • View data edit: Hides this field from a web portal user when editing a submitted form through the 'View data' tab
  • View data new: Hides this field from a web portal user when filling out a new form through the 'View data' tab.
  • Dispatch edit: Hides this field from a web portal user when editing a submitted form through the 'Dispatch' tab.
  • Dispatch new: Hides this field from a web portal user when filling out a new dispatch through the 'Dispatch' tab.
  • Mobile: Hides this field from a mobile user when filling out a form.
  • Web App: Hides this field from a web app user when filling out a form.
  • In PDF and Print: Hides this field when the form is converted to PDF or printed.
  • Form Links: Hides this field on forms that are sent as form links.

Actions

Only display this question if

This is a very powerful option as it allows you to hide form elements, only exposing them if the answer to a question in your form meets the criteria you have set. Being able to hide fields unless they are needed makes form more user friendly. For example, if you have a Choose One question with the answers Yes and No, then you can say "Only display this form element if" the answer to the Choose One is "equal" to "Yes." You can combine criteria with other criteria, thus creating complex criteria for showing/hiding form elements.

This setting is used to prevent forwards from being executed if a specific condition is not met. For example, a forward could only be executed if the question "Send to Supervisor" is equal to "Yes". If "No" is selected, the forward would not be executed.

Jump to

This option allows you to navigate the user to a specific location in the form based on how they answer the current question.

Have more questions? Submit a request

Comments

Powered by Zendesk