Automatic Upgrade for Cloud Customers
DocuPhase Forms cloud-hosted customers receive a seamless automatic cloud upgrade. If you have any questions, please email support@frevvo.com.
New Features
Updated Navigation Menus and Icons
v11.3 introduces a modern, updated navigation layout and new icons to help designers and admins easily navigate your content. While the layout has changed, the underlying functionality and content remains the same.
For example, prior versions Forms and Workflows Homepage was laid out with the main menu to the left, an expandable sub-menu, and the content in the middle, with help and search functions in the upper right.
The new layout will display the same menus horizontally across the top, with content below them and centered.
The menu options remain the same. Clicking on a main menu items that has a sub-menu will open the sub-menu just below the tabs.
The “Welcome <userID>@<tenantID>” message no longer displays at the top. You can still see the currently logged in user id quickly by hovering over the My Account icon.
You will also notice new icons throughout the user interface. For example:
The Admin homepage has a similar layout and updates icons on pages like Manage Users. As with the Designer interface, the functionality remains the same.
End users (e.g. employees filling out forms) may not often interact with the application. For example, they may access their task list via a portal instead. However, if they do utilize the app their interface will be similar but they will only see the My Tasks and Shared Items tabs, and possibly the Reports tab depending on their permissions.
Our documentation may still reflect the previous layouts and icons on some pages. However, the functionality described in the documentation remains accurate.
Format Money and Number Controls
You will now be able to employ automatic money and number formatting on your forms using the Form/Workflow-level Number and Currency Formatting property, the Money control Currency property, and the Number control Format property.
Money
Forms will now display money values for any currency formatted in the current user’s locale including symbol, thousands and decimal separators, and number of decimal places.
The currency can be dynamic, so for example the same form can be used in different offices situated in different countries, and each will display the currency correctly for that country. (Note that there is no currency conversion; the value of the control is as originally entered in the end user’s locale.)
The currency symbol is locale-specific. For example, if you have a Money control set to Brazilian Real, but you view the form in the US locale, you would see the value with the “R$” currency indicator and the US money format: R$150.32. If you run the same form in the Brazil locale, you will see it formatted as 150,32 BRL.
Currency formatting applies to the form control, any snapshot generated from it and when that control is mapped to a pdf field. Formatting does not apply to other submission related views like dashboards, searchable, summary and export fields.
Number
Similar to Money controls, Number controls can display the decimal separator differently for different currencies and locales. By default, the format will respect the Form/Workflow Number Formatting and Currency setting. Specifically, this relates to the decimal separator which is a period in some locales and a comma in others.
Form/Workflow Number Formatting and Currency Property
The form designer can set a default currency at the form/workflow level, which will apply to all Money controls added to the form thereafter. This property allows using typeahead to select a currency from the available list, and displays the selection. This property can also be set dynamically using a templatized string (a currency named in a control in your form.)
The best practice is to design your form so that currency must always be entered (either by the user or programmatically) before the money value is entered. If the currency used in the templatized string is changed after the money value is entered, it may not behave as expected. The money value must be re-loaded to pick up such a change and could become invalid due to differences in symbol, separators and decimals.
If the Currency property is not specified, or the template used resolves to null, the property will take the installation-level setting (if applied) or none (Cloud). For backwards compatibility, the property will be empty on existing forms and workflows at the time of the upgrade.
Money Control Currency Property
For use cases that require multiple currencies in one form, the Money control also has a dropdown Currency property which is set to “Default” (meaning that it picks up the Form/Workflow level setting.) The form designer can change it to any value in the dropdown list for each Money control, overriding the Form/Workflow setting for that control.
Number Control Format Property
For use cases where one or more Number controls on the form should be formatted differently from the Form/Workflow Number Formatting and Currency setting, the Number control allows formatting specific to the user’s locale or no formatting (which retains the current period decimal separator format.)
There are three options for the Number control format (specifically, the decimal separator).
Default (the default setting) will respect the Number Formatting and Currency form/workflow property combined with the locale of the form user. For example, if your Number Formatting and Currency property is set to Brazilian Real, but you view the form in the US locale, your Number format will use a period decimal separator. If you view the form in Brazil locale, the format will use a comma decimal separator.
Automatic respects the locale of the form user.
None uses the original formatting of a period for the decimal separator regardless of locale.
Additional Money Formatting Information and Limitations
Formatting is only relevant for user input in the form; business rules must use a numeric-only format.
There is no support for currency in the schema. So, when a money control is created from schema, the currency is set to Default.
You do not need to create currency name translations since they are available out of the box (based on the browser locale or the locale parameter override).
Mobile View: Previous versions render money, number, and quantity fields as a html input of type number on mobile devices. This displays a spinner on the desktop when simulating mobile while testing - which is only useful for integer fields (quantity). This allows the device to display the numeric keyboard. However, it also will not allow format separators. In order to maintain backwards compatibility and ensure proper display we now render the field as a number only if we determine that no formatting is intended to be applied. Note that the presence of a control template as default is considered as an intent to format (no effort is made to resolve it).
New Read-only Navigation Toolbar Option
The Navigation Toolbar now has a new option: Progress Bar. The Progress Bar display exactly as the default Navigation Toolbar, but the steps are not clickable so the user cannot return to previous steps, but rather, can just see a visual cue for where they are in the workflow.
New Google Connector
New SharePoint Connector
Retired Features
Form/Workflow Actions: Error actions
With our previous major release, we introduced asynchronous post processing which improves performance on submit and allows us to implement the multiple Doc Actions feature explained above. However, this method does not provide an “error” state back to the user at the time of form submission, so the Form/Workflow Actions: Error Action tab was deprecated as any settings in that tab would never be shown the end user. That tab and any settings within it has now been removed
Control Property: Sensitive
The control property ‘Sensitive’ has been removed from the Form designer. The DocuPhase product team is considering alternatives to help mask sensitive data such as SSNs or account numbers. In the meantime, please be conscious of when controls that collect potentially sensitive data are set to printable, used as Searchable, Summary or Export fields, used in templates and who has access to see them via the View Submissions and Edit Submission access control.
Migration Considerations
Dashboards Enabled
Dashboards are now included in your DocuPhase Forms subscription and enabled for all tenants. You will see the Dashboards tab available in your Project sub-menue. If you haven’t checked them out before, learn more here.
Number and Money Formatting
The Form/Workflow Number and Money Formatting will be empty on migrated forms and workflows.
The Currency property will be ‘Default’ on migrated forms and flows. This means it takes the Form/Workflow level property, which will be empty. So, there will be no money formatting on migrated form and flows, and they will retain their previous behavior.
The Format property (Number controls) will be ‘Default’ on migrated forms and flows. This means that formatting will be on if Number formatting and Currency is set, and off if it is not set. Since migrated forms and flows will not have Number formatting and Currency set, formatting will be ‘off’ and Number controls will retain their previous behavior.
No designer action is required to retain your existing behavior. Designers can adjust any or all of these properties as desired.