DocuPhase Forms latest - This documentation is for DocuPhase Forms v11.3. Not for you? Earlier documentation is available too.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

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.

v11.1 Forms and Workflow Homepage.PNG

The new layout will display the same menus horizontally across the top, with content below them and centered.

v11.3 Designer HomePage with Notes.PNG

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.

v11.3 User ID hovertip.PNG

You will also notice new icons throughout the user interface. For example:

Screen Shot 06-04-24 at 10.20 AM.PNG
Screen Shot 06-04-24 at 10.20 AM 001.PNG
Screen Shot 06-04-24 at 10.20 AM 002.PNG

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.

v11.3 Admin Home Page.PNG

v11.3 Manage Users.PNG

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.

v11.3 End User Homepage.PNG

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

// Move most of the details to the palette controls docs, keep this page high level. drafting here for now.

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.)

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

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.

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.

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 Google Connector

New SharePoint Connector

Retired Features 


Migration Considerations









  • No labels