Web Interface Engine

Each web interface of your applications is based on a specific version of the DigitalSuite Web Interface Engine.

RunMyProcess provides periodic updates for the engine to support new functionality or data structures. While it is possible to continue to use a previous version, you may wish to upgrade to a newer version at some point in time, for example, to take advantage of new features or performance improvements.

Before assigning a new engine version, you have to carefully check all changes between the old and the new engine version since they may affect the web interface behavior. You need to ensure that the web interface is fully compatible with the engine you assign and that there are no unwanted side effects. Changes might be required to make the web interface compliant with the changes introduced by the upgrade. Upgrading the engine version for a web interface that is used in production must therefore be handled with utmost attention.

A new web interface has automatically the latest engine version assigned. If you copy a web interface, the copy also uses the latest version which could be different from the one used by the original.

Viewing and Upgrading the Web Interface Engine Version

To view the Web Interface Engine version that is used by a web interface, open the web interface in the WebModeler of DigitalSuite Studio, open the Settings pane, go to Settings > Advanced > Web Interface Engine. The Version field displays the current version.

If an older version is displayed for the web interface, you can upgrade to the latest engine version. Before doing the upgrade, check the changes introduced with Web Interface Engine releases in the section below.

Overview of Release Changes

With the releases described below, changes were introduced that have an impact when upgrading the engine assigned to a web interface. For more detailed information, please contact the RunMyProcess support.

2022-03-10 - 6.4.0 - Reserved Variable Names

As of engine version 6.4.0, web interfaces cannot be saved if they include reserved variable names.

2018-11-07 - 5.19.2 - Custom Widgets

Engine versions as of 5.19.2 display the correct value for input widgets in web interface instances for widgets that are nested in two or more custom widgets. This affects all types of widget for which the Initialize option is set in order to initalize the widget with a specified value.

2018-02-05 - 5.17.1 - JSON Arrays in Variables

Engine versions as of 5.17.1 now validate variables with patterns using square brackets ([...]) before submitting a form. If the widget holding the variable is wrapped by an array widget, only the value that corresponds to this widget index is validated. Otherwise, the whole JSON value is validated against the configured pattern.

2017-10-12 - 5.16.0 - Validation Rules in Custom Widgets

This release fixes an issue that prevented validation rules from working when defined within a custom widget.

2017-06-29 - 5.15.0 - Filter in Reports

This release fixes an issue that prevented filter settings in report definitions from being effective. The MP_Report.add(Measure)Filter JavaScript function is now available if a user filter is set.

This release fixes an issue which prevented the web interface designer from manually changing the hour in date widgets.

2016-11-23 - Thibault v1 - Disable Property Changed for Text Input

Due to a W3C specification update, this release introduces a change in widget properties. Non-active widgets of type Text Input, Date Input, URL Input, Captcha, and Upload no longer allowed selection, copy/paste, and error display in specific web browsers.

In web interfaces using the Thibault v1 or a more recent engine, widgets of these types are now set to read-only, i.e. the Editable property is not set

2016-09-28 - Mongo v3 - Label for Checkbox Lists

This release fixes an issue that prevented the label in checkbox lists to be displayed above the checkboxes. Selecting Above as Label position in the settings of all checkbox list widgets does now have the correct effect.

2016-02-03 - Wight v1 - JavaScript Report and Variable Visibility

This release reduces the scope of variables and functions defined in the Loading data script which is used in JavaScript reports. Variables and functions defined within the script are therefore no longer accessible from outside of the script.

When upgrading from an older engine version, you have to make sure that there are no references to these variables and functions from outside the script.

2015-11-12 - Java v2 - Array

Engine versions as of Java v2 support the following syntax in dynamic rules:

[[myarray.column1]][P_index]

Web interfaces using the Java v2 or a more recent engine need to be tested to ensure that the syntax change does not result in any problem.

2015-06-03 - Lifou v3 - Post-Loaded Script of Reports

Web interfaces using the Lifou v3 or a more recent engine execute the post-loaded script of reports each time data is loaded into the report (e.g. when computing a filter, navigating from page to page, or refreshing the data via JavaScript or manually). Web interfaces using the Lifou v2 or an older engine, however, execute the post-loaded script only when loading the data for the first time.

2015-04-15 - Lifou v2 - Escape Character in Scripts

Web interfaces using the Lifou v2 or a more recent engine use an escape rule in embedded scripts that is different from the rule used in older engines. A simple backslash (\) is used to escape special characters instead of a double backslash (\\). This applies to all scripted properties of widgets, for example scripts, URLs, or regular expressions.

The following example shows the pattern in an email widget. The email widget is simply text input that uses a regular expression to check if the information that is filled in is indeed an email.

Pattern before the Lifou v2 release:

^([a-zA-Z0-9_\\-\\.!#$%&'*+-/=?\\^_`{|}~]+)@((\\[[0-9]{1,3}\\.[0-9]{1,3}\\.[0-9]{1,3}\\.)|(([a-zA-Z0-9\\-]+\\.)+))([a-zA-Z]{2,6}|[0-9]{1,3})$

Pattern with the Lifou v2 release:

^([a-zA-Z0-9_\-\.!#$%&'*+-/=?\^_`{|}~]+)@((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.)|(([a-zA-Z0-9\-]+\.)+))([a-zA-Z]{2,6}|[0-9]{1,3})$

2013-06-13 - Mogador v1 - Introduction of JQuery and CSS Change

Web interfaces using the Mogador v1 or a more recent engine require JQuery to work correctly. This means that when creating a new web interface from an existing one, for example by copying it, you have to add the JQuery framework if the web interface source was created with an older engine.

To add the JQuery library, open the web interface in the WebModeler of DigitalSuite Studio, open the Settings pane, and go to CSS & JS > JS. In the JS section, add the standard jQuery library available on the DigitalSuite platform. This will then be used in the header and footer of your web interace.

Please be aware that the look and feel of a web interface will be significantly different when using the Mogador v1 or a more recent engine since the CSS was completely rewritten for the Mogador v1 release.