01-20-15 Website Release 2.9.8


We are pleased to announce Version 2.9.8 of the mydoForms website.  This release provides a number of functional improvements for customizing reports, displaying and exporting data, creating dispatches, customizing forms, as well as enhanced security.

Hide Empty Rows and Columns in Custom Reports

We have added some new script functions to Custom Report Templates that “hide” rows and columns based on the value of a question answer.  Normally, to insert the answer value of a question into a Custom Report Template cell, you would include a data-name tag such as {mydata_name}.  But suppose you would like to use the value of the mydata_name field to hide selected rows and columns in the Custom Report Template.  These new script functions allow you to do just that.

Below are a few examples that illustrate how this script function works.

Example 1:  Suppose your tag {mydata_name} is in row 37 but you would like to hide row 37 if the returned value to the field is empty (null).  Then instead of using just the {mydata_name} tag in the cell where you want this value placed,  use the tag:
{<script> if (value == "") {hideRow(“37");}</script>mydata_name}  
This script will hide row 37 if the value mydata_name is empty.  For example, if mydata_name corresponds to a picture, but no picture was taken, then this script could be used to hide the row reserved for the picture.  This would consolidate the format of the report.

Example 2:  Suppose you would like to hide row 37 and column P if the returned value to the field “mydata_name” is equal to the text “abc123”.  Then instead of using.just the {mydata_name} tag in the cell where you want this value placed,  use the tag:
{<script> if (value == "abc123") {hideRow(“37"); hideCol("P");}</script>mydata_name}
This script will place the value “abc123” in the desired cell and will also hide row 37 and column P.

Example 3:  Suppose you would like to hide rows 30:32,34,37 and columns P,Q, A:H if the returned value to the field “mydata_name” is equal to the number “88.3”.  Then instead of using just the {mydata_name} tag in the cell where you want this value placed, use the tag:
{<script> if (value == "88.3") {hideRow(“30:32,34,37 "); hideCol("A:H,P,Q");}</script>mydata_name}.  
This script will pace the value “88.3” in the desired cell and will also hide rows 30 to 32,34,37 and columns A to H, P,and Q,.

More information about creating custom reports 

Hiding Labels Empty Repeatable Loops in View Data

New options View Data > Options > View Settings now provide controls for hiding columns corresponding with Label widgets.  You can also hide columns corresponding with repeatable loops that do not contain any values (i.e., empty repeatable).  Use the new settings to simplify the View Data tab.  These settings are also provided in the Dispatch tab.  

Similar settings are provided in View Data > Options > Export Settings as shown below.

More information about Repeatable Section containers
More information about Label widgets

Hide Grids and Tables with Relevance Logic

You can now use relevance logic to hide entire Grid and Table containers as desired to control the appearance of your forms.

Form Template Library Redesign

We have redesigned the format of our Form Template Library.  You can quickly browse this library to preview form templates and add them to your account.  Once added, you can use them directly or as starting points for customizing your own form.

New Standard Icon Sets

We have added over 200 new icons to our Icon Library.  Use these when customizing Action widget buttons or the mobile app user interface (or upload your own graphics).

Dispatch Web App UI

The Web App version Dispatch tab user interface has been optimized for large lookup tables.  When a dispatch is sent, the user interface below will remain open for additional dispatches to be sent.  This eliminates the delay caused by reloading large lookup tables for each dispatch transaction.   Your Dispatchers will be happy!

More information about dispatching forms

Required and Read Only Fields

You can now control the use “Required” and “Read only” properties for most widgets separately as used in the mobile app and when dispatching.  For example, certain “Required” fields might apply to a dispatcher but not to the mobile user.  Or certain “Read Only Fields” might apply to the mobile user but not to the dispatcher.   Use these new properties to fine-tune the behavior of your forms.

Forward Reset

A reset property has been added to the Forward widget.  Checking this property caus the “forward to” email address in the widget to be reset to “null” after  form is forwarded.  Use this to prevent an undesired chain of forwards.

More information about the Forward widget

Import and Export Functions in Mobile Units tab

We have added Import and Export functions to the Manage > Mobile Units tab to make it easier to manage large mobile workforces.

More information about managing mobile units

Control Website Privileges by Project

In addition to controlling View Data tab and Dispatch tab access by “mobile group” and “mobile number”, we have added the ability to control access by “project”.  This means that the designated Web User will have access only to specific projects.  To control these settings go to Manage > Web Users and select Edit from the Row Menu of the user, then set the “Project View Restrictions” as desired..  In the illustration below, the user is restricted to  “Edit” privileges to the “Main Project” only.  None of the other projects in the account will be accessible to her.

More information about setting up website users

Security Enhancements

To enhance security, we are now directing all website logins to our HTTPS/SSL Google App Engine domain (https://mydoforms.appsot.com).  All communications with this domain are encrypted using Secure Socket Layers (SSL).   We have also added automatic browser session expiry after 2 hours of website non-use.

More information about security

Have more questions? Submit a request


Powered by Zendesk