Initializing help system before first use

New Functionality and Changes Introduced with Xpress Workbench 3.8

This section describes the new features and changes introduced with Xpress Workbench 3.8.

New in Xpress Workbench 3.8

  • View Designer: Added Tableau Parameter component, this enables you to add one or more Tableau Parmeters to a Tableau component.
  • View Designer: Added Tableau Export and Tableau Clear Global Filters actions, these enable you to trigger the respective actions against a specified Tableau visualization.
  • View Designer: Added the VDL version information, version since, to each VDL component and attribute as tooltips. A component will be shown as in error if it is used within a VDL file that is older than the component version. The attributes panel will also show an error if any attributes are shown that are newer than the VDL file.
  • This release introduces a beta of remote debugging for Python-based Insight apps.
    • Debugging Python files or Insight apps locally in Workbench is disabled, and will be added in a future release.
    • Requires Xpress Insight 5.5+, and Python modules xpressinsight 1.5.0+, debugpy 1.6.5+
    • Debugger pane supports Watch expressions, navigation through call stack, Variable inspection and breakpoints
    • Hovering over a Python entity shows a preview of data and provides a link to inspect data in a separate static text view
    • Conditional breakpoints are supported
    • An input field above the Output pane allows users to enter arbitrary expressions which are evaluated and printed to Output pane
    • Known limitations:
      • The debugging inspection tools do not currently support full traversal of object hierarchies
        • Objects like pandas DataFrames have a default textual representation showing the data in a tabular format
      • Data can be viewed as static text, in contrast to Mosel's live Inspect In Table option
      • As with Mosel, does not support editing of the source during debugging
    • Known issues:
      • Only single-thread debugging is currently supported, e.g. debugging the sklearn module's multithreaded cross_validate method may lead to the debug process freezing
      • If the user, incorrectly, debugs a scenario in an execution mode that requires the scenario to have input data to loaded (e.g. RUN), and the input data is not loaded, the error message informing them of the need for the scenario to be loaded may not appear.
      • If a breakpoint is set exactly as the debug is starting, it may not appear in the UI even though it is in effect. (Causing a redraw in any way will show the breakpoint.)
      • Very rarely, the variables view of the current stack frame may, on loading, not clear out its previous contents first.
Parent Topic Updates from Previous Versions and Known Issues

© 2001-2026 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.