New Functionality and Changes Introduced with FICO Xpress Insight 4.7
This section describes the new features and changes introduced with FICO Xpress Insight 4.7.
New in Release 4.7.0
Summary
- Built in attachment editors for the following file types
-
- Text files
- Decision tables
- Decision trees (FSML 1.0, 2.0, 2.5)
- Decision impact model graphs
- Projects have been renamed to apps. Home page now displays app name and version information
- VDL and JavaScript API 3.2, includes attachment creation and editing capabilities.
- Support for Tableau Parameters
VDL 3.2
- Added attachment creation actions, "create-project-attachment" and "create-scenario-attachment", to the vdl-attachment-button tag.
- vdl-attachment-button elements are disabled if bound to virtual scenario or if the logged in user doesn't have the required attachment edit authority. A detailed reason for an attachment button being disabled is given in the button tooltip.
- Added actions (edit-project-attachment and edit-scenario-attachment) to vdl-attachment-button to open an existing file attachment in the relevant editor for the corresponding file ending.
- vdl-table display state (page size, page number, sorting and filtering) are preserved during a user's web session. This means that table redraws or moving between views and projects within the same browser window will retain table state.
- vdl-table will combine the index set values from all scenarios used by the array entities in the table.
JavaScript API 3.2
- Added View#createProjectAttachment, View#createScenarioAttachment, Project#createAttachment and Scenario#createAttachment methods.
- Added Attachment#getEditor and AttachmentEditor#open for triggering editing an attachment.
- AutoTable and Table display state (page size, page number, sorting and filtering) are preserved during a user's web session. This means that table redraws or moving between views and projects within the same browser window will retain table state.
- AutoTable will combine the index set values from all scenarios used by the array entities in the table.
REST API
- When updating an app via a POST operation to /data/project/{id} , the displayName property can also be updated.
- This in addition to the notes property, that was already available.
- If a settable property is not defined, it will be left unchanged on the app, rather than deleted.
- See the "fixed" section below for changes to handling of the notes property.
Tableau Parameters
An app can now expose Tableau parameters for use when a Tableau report is displayed. Before displaying the report, the user will be prompted to select the value for the parameter.
- Parameters are configured for use with OM using in the tableau section of the companion file.
- The configuration includes the definition of which entity to obtain the possible parameter values from. These are then presented to the user for selection.
- The configuration allows for the parameter to be restricted to a particular workbook and / or view using inclusion and exclusion rules.
Fixed in Release 4.7.0
VDL 3.0+
- Fixed an issue with addrow-autoinc where new rows would disappear immediately after adding if a vdl-validate was referencing the extended index set entity.
- The vdl-attachment-button enabled attribute now evaluates correctly when given an expression.
- Fixed an issue where contents of vdl-if and vdl-visible attributes could be mis-interpreted if they contained low-precedence operators such as ||.
VDL 3.1+
- Fixed an issue where attribute expressions on vdl-execute-button would only be evaluated once, at startup, rather than on each time the button was pressed.
JavaScript API 3.0+
- Fixed an issue that was causing Table, AutoTable and vdl-table components to render very slowly when the end-user sorts a numeric column that contains null (empty) values.
REST API
- Updating an app via a POST to /data/project/{id} no longer erases the notes if the notes property is not set; to achieve that, set the notes property to the empty string.
- Prior to this release, only the notes property could be set this way; now the displayName property can also be set, it became necessary to clarify the behaviour when some properties are defined in the POST operation and some are not.
Web Client
- Fixed missing search box in entity explorer
Fixed in Release 4.7.1
OM server
- Database tables are analyzed after mirroring to ensure optimal Tableau query execution.
New in Release 4.7.2
Summary
- Tableau 10.2, 10.1 and 10.0 compatibility.
- Database upgraded to PostgreSQL 9.5 from PostgreSQL 9.1. Migration is performed automatically during installation on Windows. On Linux the migration steps in the Optimization Modeler Installation Guide must be followed.
- Linux installers now support unattended installation. Options are passed via the command-line. See the Optimization Modeler Installation Guide for more information.
- The database and server now use UTC time zone whereas previous versions used the operating system's local time zone. When upgrading an existing database, scenario data is unaffected by this change. However the scenario creation timestamp and attachment last modification timestamp will shift by the time zone difference between UTC and local. To avoid timestamps being shifted, export the repository before upgrading, perform a clean installation and then import the repository.
- Support for Xpress-Mosel S3 integration. See the Developer Guide for further details.
Fixed in Release 4.7.2
- Fixed an issue where custom view Javascript API files were incorrectly presented as minified while in debug mode.
Fixed in Release 4.7.3
Windows Installer
- Fixed an issue where the installer might be prohibited from launching standard system applications, when running in the presence of certain restrictive third-party security environments.
© 2001-2020 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.