Forward

Follow

Forward

The Forward tool allows one mobile user with a dispatch license to forward a form to another user with a dispatch license.

There are several parameters to assist in this process:

  1. You can set ignore required fields when forwarding in the save and send action buttons. If you do not set this and the form has required fields it will not let the first person send the form until all required fields are filled out.
  2. You can have the system automatically clear the forward to field so that the form does not get sent back to the same person over and over again.
  3. You can suppress emails from being sent when the first user submits the form. This will allow the email to only be sent by the second person after the form is complete.

Forms that have been forwarded will appear in the jobs section 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 section and not just the form name.

The Forward tool is executed when the form is sent by User A and received by the website. At that time, the form is dispatched by the website to User B who receives it as a normal dispatch. While a forwarded record will be sent as a dispatch to the receiving mobile device, it does NOT create a new record in the Dispatch tab of the website. Also, it 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 person 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 on the website. Only the most current version of the form record is stored in the View Data throughout the process above.

Below is an example of how the Forward widget might be used in a form:

1. A Lookup widget is used to select a “Forward to:” name and passes the mobile number of the recipient as a destination field.




2. The Forward widget receives the mobile number of the recipient.



4. This is what the “Forward to:” Lookup question will look like in the mobile app.  Selecting either of the names will pass the mobile number of the recipient as a destination field to the Forward widget (which is not visible because of its “hide in mobile” property).

Note the following important details:

  • The mobile number must be an integer value with no spaces or special characters.
  • The Forward widget is executed when the form is sent by User A and received by the website.  At that time, the form is dispatched by the website to User B who receives it as a normal dispatch.
  • While a forwarded record will be sent as a dispatch to the receiving mobile device,  it does NOT create a new record in the Dispatch tab of the website.  Also, it 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 person 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 on the website.
  • Only the most current version of the form record is stored in the View Data throughout the process above.

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 situations, smaller captions should be used where possible.

Hint - Providing additional information on how a question should be answered can be achieved easily using the Hint option. The text for hints is smaller the caption. The maximum number of characters supported is 500, including spaces.

Data name - Since the data name is a required field, doForms will default the data name to the caption/label. If this field is blank doForms will provide a generic name with a sequential number. We recommend that you provide a descriptive data name that is easily identifiable. The data name is used throughout the system and non-descript names can make it difficult to select the item you need for example when performing a calculation.

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

  1. Leave default value blank and prompt the user for a Mobile ID
  2. Type a mobile Id into the default value
  3. Use a lookup and set the forward widget as the destination field equal to the mobile ID field in the lookup table.

To force a forward. Set the default value to the mobile ID and set the read only parameter. You may also want to hide this field.

Other parameters:
Turn off email
Reset - Rest will clear the forward-to destination and will turn on the send email function after the form has been forwarded to the recipient.

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.

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 - The read only option is provided to address a specific circumstance. It allows you to treat dispatchers and mobile users differently so that you can set rules for each independent of the other. One may be allowed to edit a field and the other may not be allowed to edit a field.

In mobile app Determines whether or not this field can be edited within the mobile, web apps and the View Data tab.

When dispatching Determines if this field can be edited in the Dispatch tab or not.

Required - The required option is provided to address a specific circumstance. It allows you to treat dispatchers and mobile users differently so that you can set rules for each independent of the other. What is not required for one can be required for the other.

In mobile app Whether this field must be filled-in when completing the form in the mobile app or web app.

When dispatching Whether this field must be filled-in when dispatching the form.

Hide

In mobile app Check this option if you wish to make the question invisible in the mobile app. You might want to do this so the mobile user cannot change the value, or if the value is being used in some intermediate calculation or logical expression.

in Data and Dispatch tabs Check this option if you wish to hide the question in the View Data and Dispatch tabs of the website.

In PDF and Print Check this option if you wish to hide the question in the View Data and Dispatch tabs of the website.

Action

Only display this question if
This is a very powerful option as it allows you basically hide form elements only exposing them if the answer to a question in your form meets the criteria you have set. For example if you have a choose one question with the answers yes and no than you can say only display this question if the answer to the choose one is equal to yes. You can even combine other criteria like and color is not equal to red. Being to hide fields unless they are needed makes form more user friendly.

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