Initializing help system before first use

New Functionality and Changes Introduced with FICO Xpress Executor 4.0

This section describes the new features and changes introduced with FICO Xpress Executor 4.0.

New in Release 4.0

General

  • Optimization Modeler Enterprise Edition is now the standard installation, Desktop Edition has been discontinued.NB: The Desktop Edition assigned all content to the single user anonymous. After upgrading or importing a Desktop Edition repository, you can continue to use this account and its content by logging in as anonymous, with password anonymous. It is recommended to change this default password via User Administration after upgrade.
  • Opening and saving scenarios in the Analyst Client is now up to 2x faster.
  • Opening a Tableau view in the Analyst Client no longer fetches the scenario data.
  • Improved handling of multiple view tabs in the Web Client.
  • New authorities SCENARIO_OWNER, SCENARIO_SHARE, FOLDER_OWNER and FOLDER_SHARE provide granular control of ownership and share status that was previously granted implicitly by SCENARIO_EDIT and FOLDER_EDIT. On upgrade to 4.0 or a pre-4.0 repository import, authority groups with FOLDER_EDIT or SCENARIO_EDIT will be granted the appropriate OWNER and SHARE authorities.
  • The default mirror database is used for all mirror operations. The companion file datasource attribute for the database-mirror element has been deprecated and removed.
  • JavaScript 1.4 API has been introduced. For details see the following JavaScript API section.
  • The default installation no longer includes the anonymous account.
  • Showcase samples:
    • Optimization Solution for Energy Pricing - NEW
    • Optimization Solution for Alternative Deal Structures
    • Optimization Solution for Collections Placements
    • Optimization Solution for Marketing Offers
  • Model schema is now captured on project creation, and parameters can be set before loading the first scenario.
  • Real numbers are displayed with at most 4 decimal places by default.
  • Scenario path visible in tooltips in both the Analyst Client and Web Client.
  • Upgraded to Xpress 7.8
  • Upgraded to Tableau 8.2.4
  • Upgraded to Java 1.7.0_71

Tableau Integration

  • Much improved and simplified Tableau installation. Tableau integration is now configured from the Web Administration interface post-installation and supercedes the installer steps and configure_insight command line utility in earlier releases.
  • Tableau health check rapidly diagnoses common configuration issues.
  • Tableau authentication is now performed using named individual Tableau accounts, the shared Tableau account insight is no longer required or used.
  • Tableau accounts are now seamlessly managed by Optimization Modeler for a fully embedded Tableau deployment.
  • Tableau can be enabled per-user offering finer control of Tableau license assignment.
  • WORKBOOK_PUBLISH authority also controls publish rights in Tableau and from Tableau Desktop.
  • Tableau accounts can optionally be managed manually for a peer-to-peer Optimization Modeler/Tableau deployment.
  • Enhanced security model in the mirror database enables Tableau data sources to enforce scenario access rights.
  • Workbooks can be embedded in projects and are automatically published, deleted, imported and exported; controlled by the new companion file attribute managed on the workbook element.
  • Publish workbook capability in the web client will only publish workbooks marked as embedded.
  • Scenario path is now mirrored into the insight_scenarios table.
  • Tableau documentation has undergone a significant revision.
  • New Tableau Server and Desktop installation package.

Analyst Client

  • Cross Tables allow multi-dimensional data to be displayed across multiple columns.
  • Lookup columns allow arrays with different index sets to be displayed together in the same table.
  • Multi-value filters allow more flexibility when filtering tables.
  • New labels can be added to index sets, linking the label with an auto-incremented set value.
  • Index set values can be deleted, causing the corresponding array data to be deleted.
  • Sorting a table can use either the labels or the underlying data values.
  • When pasting data into a table view, values are repeated to fill the selected area.
  • Custom formatting rules can be defined for each entity.
  • Filter drop-downs are progressively updated as you filter other columns to only show values which remain visible in the table.
  • Toolbar button to reset a table view to its default layout.
  • Numbers are displayed right aligned in tables.
  • Server name shown in Analyst Client status bar.
  • Dashboards now appear in the Views pane, instead of on the repository context menu.
  • Line and area charts no longer show a marker for each data point.

JavaScript API

1.4

  • Scenario#getArray now supports asynchronous invocation with success and error callbacks.
  • Add and remove row now support pre and post call hooks. Pre hooks may be used for validation and post hooks for event notification.
  • Tables may now be filtered by column. This is exposed through a DataTables overrides property passed in to Table or AutoTable
  • The rules around sorting of select options defined in AutoTable editorOptionsSet column options has changed. Sorting is determined as follows:
    • If a set sorter has been assigned to the options set then that will determine sorting of the select options
    • If the set has an associated labels array then the data type of that will determine the sorting
    • Else, the options will be sorted according to the set element data type
    Default sorting according to data type will either be numeric sorting or case-insensitive alphanumeric sorting.
  • Table has a new column option, displayType. This is optional and it will default to the value of the existing type column option. It is used to determine what styling to apply to the column. The type option is used to determine sorting behavior and fallback display behavior.
  • AutoTable index columns are now 'td' elements rather than 'th'. They are styled in the same way as before and you can still target them as they have the .index class.
  • AutoForms can now have several run buttons, to support models with different run modes.
  • New 'tooltip' element in VDL to provide contextual information in custom views.
  • Custom views can contain hyperlinks that link to other custom views within the project.

Fixed in Release 4.0

General

  • The scenario-id attribute of the VDL autotable tag is now passed to the generated AutoTable. Previously it was having no effect.

JavaScript API

  • 1.4
    • AutoTable columns containing editorOptionsSet will now be sorted and filtered correctly by their underlying values rather than the displayed values. They also respect the column options filterByFormatted and sortByFormatted.
    • Boolean data types in Table and AutoTable columns can now be sorted.
  • 1.3
    • When setting a column name in AutoTable it is cast into a string so it will now accept any type of primitive or object.
    • Using the old constructor signature for AutoTable, i.e. multiple arguments, was causing JavaScript error in some browsers. This is now fixed.
Parent Topic Updates from Previous Versions and Known Issues

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