WebUI Release Notes

All WebUI release notes of AIMMS versions older than AIMMS 24.4 can be found here. From AIMMS 24.4 onwards, the WebUI can be added to your AIMMS project as a repository library from the Library Manager in AIMMS (see here).

WebUI 24.13

WebUI 24.13.5 Release (December 19, 2024).

Resolved Issues

  • The use of webui::ResetRequestQueue (when called from the model), could in some situations cause a (harmless) message “Cannot change value of read-only identifier ‘RequestQueue’”. This specific message will not be shown anymore.

  • A blank error message was displayed during the Page-Leave-Procedure when the StatusDescription field was left empty upon return.

WebUI 24.13.4 Release (December 12, 2024).

Resolved Issues

  • Having an identifier in a Table that was set up to use the store focus feature based on the indices of this identifier, and changing the identifier to another one with different indices, could yield an incorrect error message “undefined: Unknown identifier”.

WebUI 24.13.3 Release (December 11, 2024).

Resolved Issues

  • The page-upon-leave procedure was not executed when the page contained a Tabbed Pages widget.

  • Applying Table filtering to a Table widget where the row or column headers had an identical display text did not work.

WebUI 24.13.2 Release (December 9, 2024).

Resolved Issues

  • There was a navigation problem in the workflow that occurred when the step state was changed to active and a webui::OpenPage call was executed on the same workflow step from within the same AIMMS procedure.

WebUI 24.13.1 Release (December 4, 2024).

Improvements

  • Some aggregators do not make sense in all scenarios for all identifiers in a widget. For example, summing longitude/latitude values. We now provide a mechanism which gives you the possibility to hide specific aggregators for individual identifiers per widget. For details, see the documentation.

  • We extended the Table widget with the possibility to individually hide any index from the row or column header, including the identifier-set index. This gives you more control about how your table looks, which headers are important in your use case and which are not. For details, see the documentation.

  • The behavior of in-cell icons for some types of Scalar Widget values and the alignment of those values, which we tweaked in release 24.12.7, was revisited. Icons will be visible immediately more often and the values will be right-aligned more often like it was the case before that release.

Resolved Issues

  • With the initial release of Table v2, the indices and any slicing information provided for the Display Domain identifier were ignored, and instead, the slicing information from the content identifier was used.

WebUI 24.12

WebUI 24.12.11 Release (November 28, 2024).

  • The Tabbed Pages widget will now use a different styling when it appears as the only widget in a grid layout, like Layout 9 or 11 (defining one single area). That effectively made it look like a whole page (with a single row of tabs), which works better if the background of the content and the widget styling is ‘normal’ like for a page outside a tabbed page.

  • The Tabbed Pages widget incorrectly kept on using pure white as a background color, even when the custom css property for theming it (–color_bg_widget-canvas) was changed. Related to that same background color: for some widget types it was hard to see where they started or ended (like Scalar widgets with their identifier names, values and dropdowns). A border will now visually keep these together (using –color_border-divider_light).

WebUI 24.12.10 Release (November 22, 2024).

  • Webui::MappedBrowserTimeZone would always remain empty when the user’s browser language was set to a language other than English.

  • The recently introduced per-identifier ‘Read Only’ option in the Table widget did not work when the table was comparing multiple cases (as specified in the Data Manager).

WebUI 24.12.9 Release (November 19, 2024).

  • WebUI widgets could show up incorrectly, in case you would lower the access rights of identifiers that were already being displayed in WebUI (by changing the value of the webui::IdentifierAuthorization identifier; see the documentation).

  • When switching between browser tabs and returning to the original tab, the focus would always be placed on the last Table widget on the page, instead of on the one that had the focus when leaving the tab.

  • If opening an option editor when a Table cell was selected (i.e. outlined in blue), the cell remained selected and when selecting a cell in another Table, you ended up with both cells having the focus.

WebUI 24.12.8 Release (November 13, 2024).

  • Changing the page layout to “Classic Layout” did not immediately update the page and its widgets to reflect the classic layout style. Also, for app developers using many pages with “Grid Layout”, the area names and boundaries no longer disappear when using the page navigator to navigate between different grid layout pages.

  • In special cases, especially in tables when clicking in cells that contain long (string) values, table cells could be wrongly aligned (or even not visible at all).

  • When trying to upload a file of over 128 MB in size (the maximum allowed) with the webui::RequestFileUpload function, AIMMS hung and you did not get an error message.

WebUI 24.12.7 Release (November 8, 2024).

  • The dropdown and ‘set to default’ icon for relevant table cells and scalar input fields used to be very small and equally hard to operate with the mouse. Together with the date/time picker icon, these are now shown (when hovering those cells) in a more pleasing way, with better clues as to their interactivity.

WebUI 24.12.6 Release (November 7, 2024).

  • The Tabbed Widget content would also refresh when non-mandatory properties, such as “displayText”, “tooltip”, “icon” or “iconColor” were modified for hidden tabs only.

WebUI 24.12.5 Release (November 5, 2024).

  • The current tab in the Tabbed Widget was not updated when both the tabs specification data and the current tab value were changed in the same AIMMS procedure.

  • A webui::ShowMessage call from the AIMMS model will now always trigger a toast notification: both in developer mode and in the cloud, for any message level (including ‘info’).

WebUI 24.12.4 Release (October 28, 2024).

  • We recently introduced a new per-identifier, ‘Read Only’ option in the Table widget. This option did not work for identifiers that were inside some module or library namespace.

WebUI 24.12.3 Release (October 24, 2024).

  • In recent versions, HTML content was not always shown as intended in tooltips.

  • Sorting a row or column in a Table widget could go wrong if the row or column to be sorted contained some cells that were filtered out because of an associated display domain identifier.

Resolved Issues

WebUI 24.12.2 Release (October 23, 2024).

Resolved Issues

  • In rare situations, changing a value in a table with both row and column headers hidden could lead to the table being ‘locked’. Editing or scrolling was not possible anymore without refreshing the WebUI page first.

  • The webui::proint::casefilesave procedure sometimes did not save defined parameters into a case.

  • In the WebUI combination chart the element text of a set element was used to differentiate the groups (of bars). In the case two set elements had identical element text, they would be part of the same stack, even if the associated index was in the ‘grouped’ part. This behavior of the combination chart has been improved by using the element name (i.e. the label) instead (which is guaranteed to be unique within the set).

  • Sometimes when navigating to a Workflow step that had an UponLoad procedure which both updated the workflow information and triggered a dialog, users faced a “Page Navigation Disabled” error message.

WebUI 24.12.1 Release (October 15, 2024).

Improvements

  • We introduced the ‘Read Only’ option to the Table widget. With this new option, you can display identifiers in read-only mode, which can be useful if you just want to display your data in a dashboard-like page, for example.

  • It is now allowed to specify an element parameter as the webui::AnnotationsIdentifier. This can be used to highlight suspicious input data which might be causing a mathematical model to become infeasible. (The AIMMS feature to find the suspicious input data will be released at the end of 2024.)

WebUI 24.11

WebUI 24.11.2 Release (October 3, 2024).

Resolved Issues

  • When using a DateTimePicker that should only select a month and a year (and no day), the WebUI would give an error.

WebUI 24.11.1 Release (October 2, 2024).

Improvements

  • We added an updated version of the Table widget as an Experimental Feature (called ‘Table V2’). In this Widget, we modernized some option tabs, allowing you to specify options like decimal places and the showing of units for each identifier displayed, instead of for the complete table. For more details, see the documentation.

  • We promoted the following previously experimental features to generally available status: Widget Named Views, the Tabbed Widget and the Diagram Widget.

  • The Text widget has been upgraded with enhanced rich text editor controls, offering improved formatting capabilities.

  • You can now use webui::IdentifierElementText to apply translations to the identifier name displayed on the Slider widget.

Resolved Issues

  • Selecting multiple scattered boolean cells in a Table widget and using Ctrl+Space now toggles the values as described in the documentation.

  • In the Combination Chart, tooltips were already displayed by hovering the blank space in the widget. If you were using large tooltips, this could block the view of the actual chart. Now the tooltips are only displayed when hovering over the points or lines of the chart.

  • Navigating between tabs within a Tabbed Widget was incorrectly updating the webui::CurrentPageId with the page of the current tab, instead of the current page on which the Tabbed Widget resides.

WebUI 24.10

WebUI 24.10.3 Release (September 12, 2024).

Resolved Issues

  • When clicking the ‘preview end-user mode’ button on the WebUI (introduced in WebUI 24.9.1), sometimes a ‘Page not found’ message was displayed instead of showing the preview.

WebUI 24.10.2 Release (August 28, 2024).

Resolved Issues

  • In the Diagram and Map widgets, you can now use sliced identifiers to specify the Center X, Center Y, and Zoom options.

  • The procedure webui::RequestShowNotification can now be called in combination with a call to webui::RequestsPerformWebUIDialog. The OS notification and the WebUI dialog will appear simultaneously to make sure that the user will be notified, even in case the browser is minimized or another browser tab (other than the WebUI) has focus.

WebUI 24.10.1 Release (August 23, 2024).

Improvements

  • To improve performance (especially for cloud applications), the webui::LoadCase procedure will skip the file system scan for all available case files and assume that the list of available cases is not changed.

  • The AIMMS WebUI library has been extended with a webui::ShowMessage procedure. This procedure takes two arguments (the first being the ‘level’ and the second being the message to be displayed) and will show a message to the user in WebUI (i.e. in the browser). For the levels ‘warning’ and ‘error’ a call to the webui::ShowMessage procedure will behave the same as the execution of a raise warning or raise error command from the model. In addition, the ‘info’ level can now be used to send an informational message to the WebUI user (which was not possible in combination with a raise command in the language).

  • In the WebUI table widget, the store focus will now work bidirectional. In case all indices have a store focus element parameter and in case the value of one or more of these store-focus element parameters is changed, the focus cell in the table will be updated accordingly.

Resolved Issues

  • On the Diagram widget, the restriction on reusing the same identifier with different slicing options in the Node Template fields has been removed.

WebUI 24.9

WebUI 24.9.2 Release (August 8, 2024).

Resolved Issues

  • HTML text in Table header cells would show the raw HTML code instead of the resulting HTML if the header content was dynamically updated.

  • The WebUI now offers translation support for the following words/phrases that are used on the Multi-Select widget: Select All, Deselect All, Select, Deselect, Search and Use search box for more results.

  • When switching your network while in a WebUI app on PRO, the app will now remain on the same page instead of redirecting you to the home page of the portal.

WebUI 24.9.1 Release (July 22, 2024).

Improvements

  • We have introduced a new widget type, called “Iframe Widget”. This widget makes it possible to embed external content, such as reports and other web pages, directly into your AIMMS WebUI application. For details about this widget, please see the documentation.

  • We have introduced a new “End-User Mode Preview” button in the page header section. Clicking this button opens the current WebUI page in a new tab, displaying it from the perspective of the end users. This feature provides a quick and easy way to preview how your end users will experience the WebUI.

  • The AIMMS WebUI library has been enhanced with a new webui::RequestShowNotification(message, title) procedure. This feature allows the WebUI to trigger operating system notifications directly from the browser window in which it is running. An example use case is, you can call this procedure after a solve action in an AIMMS procedure to notify the user that the optimization has been completed. See the documentation for more details.

WebUI 24.8

WebUI 24.8.1 Release (July 17, 2024).

Improvements

  • The Diagram Widget now uses the domain condition of the arcs identifier in the following way: in case a connection between two nodes is not in the index domain, the target node will not show any target feedback (i.e. a blue rectangle). And, in case a certain node cannot have any outgoing connection, it will not be possible to create a new arc starting from that specific node in the first place.

Resolved Issues

  • The Table Widget will now restrict mouse wheel scrolling to within the bounds of the data, preventing scrolling beyond the start or end of the table. This should help with the confusion when using Tables in small grid areas, where you are expecting the data to fit perfectly.

WebUI 24.7

WebUI 24.7.4 Release (July 3, 2024).

(Due to internal technical reasons, we skipped the WebUI 24.7.3 Release).

Resolved Issues

  • Changing the updateability of identifiers in a WebUI widget by adding them to (or removing them from) the set CurrentInputs did not work correctly in widgets that contained more than one identifier for which the updateability had changed.

WebUI 24.7.2 Release (June 25, 2024).

Resolved Issues

  • When uploading a large file using webui::RequestFileUpload, a veil is now displayed to indicate that AIMMS is busy. An appropriate message is also displayed.

  • Previously, in the MultiSelect widget, custom annotations, if configured, were listed under the data-annotations DOM attribute of the elements. To maintain consistency across the WebUI, starting with this WebUI 24.7.2 release, custom annotations will now be loaded under the class DOM attribute of the elements in the MultiSelect.

WebUI 24.7.1 Release (June 20, 2024).

Improvements

  • We have created a new widget type, called ‘Tabbed Widget’. This widget makes it possible to show multiple pages inside a single widget, as separate tabs. This can serve as a much cleaner solution than using hidden widgets on a page, as it basically allows you to show anything you need within the same space on a WebUI page, depending on the context. For full details, please see the documentation. The Tabbed widget is available as an Experimental Feature, and it is enabled by default.

  • The Table widget now also supports item actions when clicking in the row or column header of the table. See the documentation for more details.

WebUI 24.6

WebUI 24.6.2 Release (June 18, 2024).

Resolved Issues

  • The Label widget now officially supports HTML content. As a security precaution, any content enclosed within script tags are ignored.

  • When selecting an Element Parameter as an input for Store-Focus options on a Combination Chart widget, it was not possible to select an Element Parameter that is ranged over a Super-Set for the given index.

  • There was a superfluous warning about an uninitialized local string parameter webui::LocalFileNames after creating a new project.

  • Previously, clicking on the labels in Table header cells caused the menu indicator to stay fixed to the cells. Now the chevron appears when you hover over the cells, and the context menu can be accessed by either double-clicking the labels in the header cells or by clicking on the menu indicator.

WebUI 24.6.1 Release (May 24, 2024).

Improvements

  • The store focus mechanism has been extended, such that it does not only work when giving cells the focus, but also when clicking on row or column header cells. In that case, only the element parameters of the indices present in the clicked row or column header cell will be updated.

  • The Table widget now allows copying content from a single cell and pasting it onto a block of cells or multiple scattered cells.

  • Now the widget menu button provides the CSS class name ‘has-widget-actions’ when widget actions are available for a widget.

Resolved Issues

  • The Table Filtering dialog displayed the ‘raw’ identifier names, instead of the translated identifier names using ElementTextIdentifier annotations.

WebUI 24.5

WebUI 24.5.2 Release (May 16, 2024).

Resolved Issues

  • When using Primary Page Actions on a page, and when configuring a label for the button, that label would prevent you from interacting with anything in an even wider area around it, also when not hovering the button itself and the label was still invisible. Now, only the button itself will be ‘always on top’.

WebUI 24.5.1 Release (May 15, 2024).

Improvements

  • The design of and the interaction with the Diagram Widget has been improved to provide better and more consistent feedback while displaying, managing and selecting the nodes, labels and connecting lines.

  • The WebUI library now incorporates information about the customer’s browser language. App developers can leverage this information to deliver language-specific content on the UI. For details, please see the documentation.

  • You can utilize index domain conditions to limit arcs being added from or to specific node types in the Diagram Widget. Previously, when such an arc was added, it remained on the diagram until further interaction. Such arcs are promptly removed from the UI.

Resolved Issues

  • In the previous version, an error was encountered when users clicked on aggregator cells in the table with Store-Focus settings configured. Now, clicking on aggregator cells will effectively clear the store-focus entry from the respective index.

  • We have revised the message displayed on the Combination chart in instances where the chart fails to load all data points.

  • When using the “Upload “.xlsx” action from the Table widget menu in combination with a file format different from .xlsx and.xls, AIMMS would crash. Now only these file formats are enforced.

WebUI 24.4

WebUI 24.4.1 Release (April 25, 2024).

Improvements

  • If an option in the options editor is derived from a Template, this is now indicated properly with a ‘t’ icon next to it.

  • It is now also possible to use Table filtering on Table widgets that are displayed on a Dialog page.

  • We extended the recently introduced WebUI feature that allows you to show ‘raw’ html in a table cell in WebUI (the documentation) to the filtering. In case a certain cell is shown as html, the text filters (e.g. ‘contains’, ‘starts with’) will exclude any text that is within an html tag. For example, if a certain cell that is shown as html contains the value <span class=”author”>Hemingway</span>, the cell will not match when specifying a ‘contains’ filter with search string “author”. In other words, it will only search in the actual displayed text that is a part of the html fragment.