What's New in FICO® Xpress Workbench Version 3.7
New in Xpress Workbench 3.7
- View Designer: Upgraded to VDL version 5.0 for all new VDL files created from a template or the quick start app.
- View Designer: Support for VDL 4.8 files remains for existing VDL views.
- View Designer: Added Tableau component, this enables you to configure one or more Tableau visualizations within your view.
- Tableau Workbooks: once published to an Insight 5 server, Tableau Workbooks are no longer synced between Workbench, Insight, and Tableau. A Full Publish to an existing Insight 5 app will now remove any Workbooks that are no longer present in Workbench.
- Insight Companion files created from File menu or via the Views control on the Insight pane will now be written for Insight 5 apps. There are comments in the newly-created Companion file, advising users of earlier versions of Insight of the changes they will need to make in order to downgrade.
- When launching a Mosel process, PATH and related environment variables have the relevant location for the Xpress installation applied to the start, so they take precedence over any others that may be in the environment variable already. (Previously, the Xpress installation folders would not be added to the start of the path if they were present already.)
Fixes in Xpress Workbench 3.7
- (Desktop, macOS) The long path name issue referred to in the 3.6.2 section of these notes has been ameliorated; it now only affects extremely long paths that will not fit on the command-lines of some executables.
- (Desktop) Opening multiple projects at once would fail due to network ports not being available.
New in Xpress Workbench 3.6.2
- Upgraded some third-party dependencies
Fixed in Xpress Workbench 3.6.2
- An issue where Workbench can crash on macOS 12 (Monterey).
Known Issues in Xpress Workbench 3.6.2
- (Desktop, macOS) There have been rare instances where, on publishing a new app to Insight 5, an app with a long path name (usually stored deep in folder hierarchy) can fail to publish. As a workaround: build the app into a zip file, and upload it to Insight manually (via the Upload App button on the homepage); then when publishing from Workbench, select the new app from the list (rather than "Create new app"). Subsequent publishes to the existing app should not have this problem. This will be addressed in a future release.
- (Desktop, macOS 12.x Monterey) There have been reports of a very rare behaviour where, on first opening a project after installing the latest version of Workbench, it gets stuck on the project loading screen. We have found that rebooting after installation remedies this issue.
Fixed in Xpress Workbench 3.6.1
- (DMP) Issue where upgrading from pre-3.6 components left users with just read-only access to file system
New in Xpress Workbench 3.6
- Support for Mosel 6
- Support for publishing to, and debugging on, Xpress Insight 5 (Desktop only)
- Support for Microsoft Edge browser (Microsoft Internet Explorer is no longer supported)
- Support for VDL 4.8
- Updated VDL examples to version 4.8
- View Designer
- View Designer: Support for opening and editing VDL include files, i.e. VDL files that are used to include in VDL views and do not contain the vdl-page element
- View Designer: Added VDL Include component
- View Designer: Added VDL Progress Bar component
- View Designer: Added VDL Spinner component
- View Designer: Added VDL Job Message action
- View Designer: Update VDL Chart Series to include new Entity X attribute
- View Designer: Updated the Schema Explorer to identify progress entities and allow filtering of entities by type
New in Xpress Workbench 3.5
- Jump To Definition and the Outline pane now support Mosel include files.
New in Xpress Workbench 3.3.3
- Support for Scenario Types in Insight XML companion file auto-completion.
- Support for more Python features in editor's syntax highlighter.
Fixed in Xpress Workbench 3.3.3
- UI failing to update in response to changes in file system content.
- Issues where logging to output pane can fail to appear, or be corrupted on window resize.
New in Release 3.3.2
Console error stream output starting with "INFO" will not highlight in red
Fixed in Release 3.3.2
- No longer incorrectly enabling local debug of Python files
- In Python Insight models, the "if __name__ == '__main__'" code branch is now taken
- New HTML File template now using correct version of Insight Javascript API
- Workbench now detecting Insight Execution Modes when attached to declarations
- "App has been published" message reworded when incremental publish means no upload was necessary
New in Release 3.3
- Added support for Insight apps written in Python rather than Mosel (on-premise only).
- Can register existing Insight View file (VDL, HMTL, Tableau) in XML Companion File.
- When creating a new VDL View, user can select (or create if needed) the nested sub-folder(s) in which to place the file.
- More reliable detection of Execution Modes, based on analysis of compiled rather than source code-This now means that the compiled .bim must be present before custom Execution Modes will be listed, either on the Xpress Insight tab or in the View Designer.
- View Designer
- Palette redesign. Icons, searchable and collapsible groups.
- VDL Set Sorter in Palette.
- Repeat Contents on palette and wizard.
- Support for VDL Actions and related tags. Rendering and palette extension.
- Execution modes attribute editor.
- VDL Event attribute editor.
- VDL Action wizard creates a vdl-header (if one doesn't exist) and a vdl-action-group to house new VDL Action.
© 2001-2022 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.