Looking for best practices on how to use AIMMS? Check out the AIMMS Knowledge Center.
AIMMS improvements
- The new procedure ProfilerCollectAllData allows you to retrieve the profiling measurements of statements that are executed on the server and thus display this data in the WebUI.
- Knitro 12.0 has been added.
- The AIMMSXLLibrary has a new option axll::TrimLeadingAndTrailingSpaces. If you set this option to 1, any leading or trailing spaces in a cell value will be removed before passing it to AIMMS.
WebUI Improvements
- The WebUI now supports name changes in the AIMMS model. Before this version, using identifiers in the WebUI that had their name changed in the AIMMS model, required you to re-select the changed identifier(s) where used in the WebUI. From now on, model name changes are propagated to the WebUI.
- AIMMS has been extended with a procedure 'webui::SetProgressMessage' which allows you to replace the text of the 'busy' message in the WebUI with something more suitable to your specific situation. You can update/change this message multiple times during execution. For details, see the documentation.
- We added Page Actions to the WebUI, which help your users to get quick access to actions that are needed often, while at the same time reducing unnecessary clutter on their WebUI pages. For details, see the documentation.
- WebUI now offers, similar to the Page Open Procedure, a Page Leave procedure, which is called upon leaving the page for which it is specified. For details, see the documentation.
- We are currently working on our Workflow support feature in the WebUI. For more details and information on how to get access to this experimental feature, see the AIMMS New Features Page.
- When selecting a widget in the widget manager that is not in view on the current page, the page is now scrolled such that the widget will be in view, in order to be highlighted properly.
Resolved AIMMS Issues
- There was a problem related to the resolution of identifier names that contain both a library prefix and a suffix. This, a.o., could lead to unexpected errors when using case comparison in WebUI of identifiers that were declared in a library.
- The postsolve step did not always work correctly for models with SOS constraints containing continuous variables.
- When runtime identifiers are added or deleted (by another thread) the Model Explorer now updates its tree accordingly.
- In functions with both an iterative and a regular signature (such as first and last), compile warnings were suppressed and compile errors were misleading.
- During the first compilation at startup of a project, annotation identifiers that resided in a library were not always resolved correctly.
Resolved WebUI Issues
- When resetting the Minimum Resource Height in the Gantt Chart, the chart did not react immediately.
- On the IE 11 browser, when the Gantt Chart with the Minimum Resource Height specified opens, all resources were loaded within the viewport first and only then the vertical scroll appeared.
- If a Gantt Chart showed the resolution error message, and you adjusted the Minimum Resource Height in order to tackle that, you would still get the error, only now with a scrollbar added to the widget.
- When having a Table widget of which the data depends on another widget and selecting a value in that Table, this could lead to the Table data jumping to its first row again after making a change in the widget on which it depended, thus losing the highlight on the value that you previously selected.
- Sorting a Table widget did not work when the Table was displayed on a Dialog Page.
- Widget actions will now close when the focus is lost(i.e. the user clicked on an other widget).
- On a WebUI page that has a PageLeaveProcedure with a requestid, executing a WebUI::OpenPage procedure would throw a "WebUI cannot run nested dialogs" message.
- Text inside Gantt Chart bars on pages with multiple Gantt Charts are now shown properly.
- Not all buttons were visible when placed in a Group Widget.
- When running under PRO/Cloud, the value of the project option 'WebUI_maximum_number_of_entries_in_widget' was not correctly initialized.