Skip to main content
Skip table of contents

Technical & Minor Version Release Notes

A comprehensive list of all technical information regarding new releases. Includes warnings, which usually have implications on existing models and settings, as well as general technical information.

‌

7.1.0

Major

API Changes

No API Changes

Warnings

  • parameterEffectProxy Node Property Removed from ModelDSL (MEDIUM)
    The node property parameterEffectProxy no longer exists in ModelDSL. Uploading a ModelDSL containing this property will result in a crash. If your ModelDSL includes parameterEffectProxy, it can be safely deleted as its functionality was removed in a previous version.

  • ROLLUP Function No Longer Accepts Dimension Names as Input Parameters (HIGH)
    The ROLLUP function signature now requires Level names only and no longer accepts Dimension names. Example — Before: ROLLUP("Node 1", "Time", "Year"), After: ROLLUP("Node 1", "Year"). The release will automatically migrate all existing ROLLUP usages to the new syntax. Note: including a Dimension name will now cause the function to fail. Edge cases requiring manual updates after migration: ROLLUP calls inside comments will not be updated; if ROLLUP inputs span multiple lines with a comment on the Dimension line, the comment will shift up one line after migration.

‌

7.0.1

LTS - Hotfix

API Changes

  • Node properties moved out of displayConfig (MEDIUM)
    Several properties have been extracted from the displayConfig JSON object and are now direct properties on the node entity: aggregationType, displayAggregationType, weightedNodeId, singleAssumptionPerScenario, simulationValue. Affected endpoints: POST /models/{id}/bulkUpdateNodes, GET|POST /nodes, GET|PUT /nodes/{id}, POST /nodes/{id}/split, POST /nodes/{id}/duplicate, POST /nodes/saveWithPosition.

Warnings

No Warnings

‌

7.0.0

LTS

API Changes

  • Removal of schema handling in available tables endpoint (MEDIUM)
    The schemaFilter parameter has been removed from GET /externalDataSources/{id}/availableTables. The user's database default schema is now always used.

  • Removal of parent simulation runs and shared default scenarios (HIGH)
    Multiple breaking changes to simulation run and scenario-related APIs. The parentSimulationRunId property has been removed from the simulationRun entity; baseline is now mandatory and must reference a baseline of the workspace model. Removed endpoints: GET /models/{id}/validDefaultScenarios, GET /simulationRuns/{id}/validParents, GET /simulationWorkspaces/{id}/validSimulationRunParents — replace with GET /baselines?modelId={id}. Additionally, GET /projectSpaces/sharedScenariosOverview/{projectBK} no longer returns the parentOfSimulationRun or defaultScenariosOfSimulationWorkspace properties.

Warnings

  • New baselines might appear in a model (Low)
    Super-models may receive baseline(s) that previously existed only in a sub-model, and models with no baselines may receive a default baseline. Chance of occurring: minimal. Precondition: a simulation run in the current workspace has a parent simulation run based on a sub-model baseline that does not exist in the current model — a state only achievable via direct DB or script access.

  • Number change in bridges displaying scenario assumption data (Low)
    Bridges showing assumptions from scenario assumptions may display different delta values. Chance of occurring: minimal. Preconditions: chart has a scenario bridge on assumption categories, at least one scenario is based on a shared scenario, at least one scenario has a scenario assumption, and the assumption and the shared scenario share at least one line-item.

  • Access rights gain for SSO users (Low)
    Some users may gain additional access rights upon login. This is a fix — missing access rights were the actual issue, not an unintended grant. Chance of occurring: low. Preconditions: group membership managed via Microsoft OpenID SSO (not Valsight), user has no active Valsight groups, SSO has ≥20 groups configured, and a Valsight group matching an SSO group name exists with access rights not directly assigned to the user.

‌

6.16.0

Major

‌

No API Changes or Warnings

‌

‌

6.15.0

Major

API Changes (MEDIUM)

Removal of legacy endpoint for adding calculated nodes

‌

Removal of model and workspace lock endpoints (MEDIUM)

Removal and replacement of chart and line-item lock endpoint

  • DELETE /models/{id}/lock has been removed

  • DELETE /simulationWorkspaces/{id}/lock has been removed

  • DELETE /charts/{id}/lock has been removed and replaced by DELETE /charts/{id}/locks/{lockId}

  • DELETE /lineItems/{id}/lock has been removed and replaced by DELETE /lineItems/{id}/locks/{lockId}

6.14.0

Major

‌

No API Changes or Warnings

‌

6.13.0

LTS - Major

API Changes (MEDIUM)

  • Removal of the GET /simulationWorkspaces/{id}/availableSimulationRuns endpoint.

Warnings

  • Removal of availableSimulationRuns endpoint: The endpoint GET /simulationWorkspaces/{id}/availableSimulationRuns was used to return the parent simulation run IDs available to a user. This endpoint has been removed.

  • Removal of simulation run parameters from GET /simulationWorkspaces/{id}: The property availableSimulationRuns was removed from the response of GET /simulationWorkspaces/{id}.

View the full feature notes here:

6.12.0

Major

API Changes:

  • ES-12832: The GET /appUsers endpoint now always returns a paged response (previously this had to be explicitly requested). The response body has changed from an array of objects to a paged response object with a content property containing the array of user objects.

Warnings

  • ES-12832: Previously, you could call GET /appUsers and receive an array of user objects. Now you will always receive a paged response object with a "content" property containing the user objects.

  • ES-12868: The behavior for filtering users and groups for DataFilter has been changed to always include subgroups of the given group ID. Previously this only included direct members of the group. This change affects all usages of the DataFilter feature. Most users should not notice a difference, but if you have users in subgroups that you do not want to have filtered, you may need to adjust your configuration.

  • ES-12851: Aggregations that used to apply to all levels of a hierarchy but are now invalid for some levels may no longer be selected for those levels. This could affect existing models.

View the full feature notes here:

6.11.0

Major

API Changes:

  • The endpoint for retrieving chart data was modified. Endpoint: GET /charts/{id}/data. Change: The legendItems property was removed from the chart data response.

Warnings

  • ES-12338: Changed behavior when uploading a ModelDSL with a globalAssumptionGroupId that references a non-existing assumption group: Previously this was silently ignored. Now, an error will be returned.

  • ES-12338: Changed behavior when there is an existing model that has a globalAssumptionGroupId that no longer references a valid assumption group: Previously, the assumption group was used as normal. Now, no assumptions will be applied.

View the full feature notes here:

6.10.0

Major

Warnings:

API Changes:

Removal of Bulk Update Sheets Endpoint (HIGH)

  • The endpoint for bulk updating sheets, PUT /simulationWorkspaces/{id}/sheets, has been removed. Use PUT /simulationWorkspaces/{id}/sheets/{sheetId} for single updates instead.

Modification of Simulation Workspace Sheet Endpoints (HIGH)

  • The endpoint for getting all sheets from a simulation workspace, GET /simulationWorkspaces/{id}/sheets, now returns a paged response. Previously it returned an array.

Modification of Simulation Workspace Object Response (MEDIUM)

  • The simulation workspace object, returned by the endpoint GET /simulationWorkspaces/{id}, no longer contains the sheets property.

View the full feature notes here:

6.9.0

LTS - Major

Warnings:

API Change – Assumption Group Endpoints Modified (HIGH)

The structure of assumption categories (formerly known as custom dimension filters) has been unified with assumption groups. The assumptionCategories property has been removed. The assumptionGroups property now contains both assumption groups and assumption categories.

Affected Endpoints:

  • GET /simulationWorkspaces/{id}/assumptionGroups

  • GET /simulationWorkspaces/{id}/assumptionGroups/{assumptionGroupId}

View the full feature notes here:

6.8.0

Major

Warnings:

  • ES-11913 - Calculation engine update: Nodes that are set to be summed (have a SUM aggregation function) can no longer have the value of an individual level changed. This means a PUT /lineItems/{id} with a value for a non-top level will fail. This is consistent with the behavior seen in a fresh Valsight model.

  • ES-11914 - Calculation engine update: Nodes that contain a formula can no longer have a value set. This means a PUT /lineItems/{id} with a value for a formula node will fail. This is consistent with the behavior seen in a fresh Valsight model.

View the full feature notes here:

6.7.0

LTS - Major

Warnings:

View the full feature notes here:

‌

6.6.0

Major

Warnings:

API Change – Immutable Properties Ignored in Update/Create Requests (MEDIUM)

  • POST /simulationWorkspaces

  • PUT /simulationWorkspaces/{id}

  • DELETE /simulationWorkspaces/{id}

  • GET /simulationWorkspaces

  • POST /simulationWorkspaces/{id}/scenarios

  • PUT /simulationWorkspaces/{id}/scenarios/{scenarioId}

  • DELETE /simulationWorkspaces/{id}/scenarios/{scenarioId}

  • GET /simulationWorkspaces/{id}/scenarios

  • POST /simulationWorkspaces/{id}/scenarios/{scenarioId}/lineItems

  • PUT /simulationWorkspaces/{id}/scenarios/{scenarioId}/lineItems/{lineItemId}

  • DELETE /simulationWorkspaces/{id}/scenarios/{scenarioId}/lineItems/{lineItemId}

  • POST /projectSpaces

  • PUT /projectSpaces/{id}

  • DELETE /projectSpaces/{id}

  • GET /projectSpaces

  • POST /projectSpaces/{id}/models

  • PUT /projectSpaces/{id}/models/{modelId}

API Change – Parameter Type Update for Data Table Chart Endpoint (LOW)

6.5.1

LTS - Hotfix

Warnings:

  • For 6.5.1, see also the warnings from 6.5.0 as this hotfix also includes all the release content from 6.5.0.

  • ES-12148: A customer reported that in 6.5.0 there is an issue importing Projects using pre-6.5.0 export files if those export files contain custom groups that have members that are not users in the target system and "Import user data" is set to true. In 6.5.1, we changed the behavior to be that such members are filtered out of the custom group upon import.

6.5.0

LTS - Major

Warnings:

View the full feature notes here:

6.4.0

LTS - Major

Warnings:

  • Please check if you have any existing Perspectives, Sheets, Data Columns or anything else that references any of the removed endpoints. If yes, you need to create new ones referencing the updated endpoints.

  • ES-10819: In 6.3.x (LTS), the behavior of the NodeTreeFilter (in the NodeTree widget) will be changed to be the same as in 6.4.0. So the warning will also be applicable to the next LTS patch versions.

‌

View the full feature notes here:

6.3.16

Hotfix

Included a features from the upcoming 6.5.0 release for performance reasons.

  • ES-11469: Rolling aggregation function ROLLUP now supports 3 possible aggregation types: SUM (default, previous behavior), AVERAGE and LAST.

‌

6.3.12

Hotfix

General Improvements:

  • ES-11290 - Performance improvement for loading data in the frontend.

  • ES-11335 - Memory improvements for cache reloads.

‌

Bug Fixes:

  • ES-11285 - Fixed node that was wrongly detected as cyclic.

  • ES-11323 - Fixed issue where parent simulation run id was not taken into account for calculating the simulation run.

‌

Please view the 6.3.x Release Notes for full release notes.

6.3.7

Hotfix

Bug Fixes:

  • ES-11051 - Fixed issue where the model cache was not invalidated when a node value was updated via REST.

  • ES-11078 - Fixed rare issue where a workspace would not load correctly after being restored from backup.

  • ES-11079 - Fixed issue when upgrading from 6.0.x to 6.3.x that caused authentication issues in certain configurations.

‌

6.3.5

Hotfix

General Improvements:

  • ES-10880 - Improvement to permission checks for sharing simulation runs.

‌

Bug Fixes:

  • ES-10847 - Fixed an issue where a workspace backup could not be restored in certain situations.

  • ES-10854 - Fixed an issue where the application would fail to start if the external data source configuration was invalid.

‌

6.3.3

Hotfix

General Information:

  • ES-10632 - Fixed an issue with the rollup calculation.

  • ES-10649 - Fixed an issue with the drill down feature of a bar chart when using hierarchies.

‌

6.3.0

LTS - Major

Warnings:

  • ES-10149 - The way Valsight handles user attribute changes for LDAP users has been changed. Previously, if a user's attribute (e.g. email, first name, last name) changed in LDAP, it would not be reflected in Valsight unless the user's LDAP entry was re-imported. Now, Valsight will automatically update the user's attributes in the database when the user logs in. This may impact custom configurations that relied on the old behavior.

  • ES-10159 - Valsight will now actively prevent import of a model that uses the "percent" number format if the model was saved from an older version of Valsight. If a model was saved in version 6.2 or earlier and uses the "percent" number format, the import will now fail. A work-around is to open and re-save the model export file with version 6.3.0 or later.

‌

General Information:

  • The Valsight desktop application now requires macOS 11 (Big Sur) or later.

  • The Java requirement for self-hosted installations has been changed. Java 17 is now required.

‌

6.2.0

Major

Warnings:

  • ES-9726 - The behavior of the NodeTreeFilter has been changed to better match the expected behavior. Specifically, when filtering by a NodeTreeFilter the filter now also applies when sorting by a node that is a child of the filtered node. If you have existing models that use NodeTreeFilter, please review the results of the filter to ensure they are as expected.

  • ES-9759 - Changed behavior when calculating the simulation run for a workspace that has been archived. Previously, the simulation run would be calculated with the archived workspace's data. Now, the simulation run will be calculated with the current workspace's data. This may impact existing simulation runs.

  • ES-9779 - Number formatting changes: "percent" number format now divides by 100 by default. Previously, some number formats would have specific behavior that would not match the label. This means if you have a model that uses the "percent" number format, the numbers will now be divided by 100 if they weren't before.

‌

6.1.4

Hotfix

Warnings:

  • ES-9856 - Critical bug fix for export/import: In 6.1.0, a bug was introduced that caused project exports to no longer contain the scenario comparison data. If you have done exports between 6.1.0 and 6.1.4, those exports may be missing scenario comparison data. We recommend re-exporting any projects that were exported during that time.

‌

6.1.2

Hotfix

General Information:

  • ES-9741 - Fixed an issue where the application would fail to start if the LDAP configuration was invalid.

‌

6.1.0

Major

Warnings:

  • ES-9460 - Changed behavior for DataFilter: The DataFilter feature has been updated to improve performance. As a result, the behavior for some edge cases has changed. Most users should not notice a difference, but if you have a model that relies on the DataFilter feature, please review the results to ensure they are as expected.

  • ES-9499 - The REST API endpoint for scenarios (GET /simulationWorkspaces/{id}/scenarios) now returns an empty array instead of null if there are no scenarios.

‌

General Information:

  • ES-9503 - The Valsight desktop application now requires macOS 10.15 (Catalina) or later.

‌

6.0.1-6.0.28

LTS - Major

Warnings:

  • ES-8832: The format of numbers exported from the REST API changed. Before, the number 1000 might be represented as "1,000". Now, numbers will always be represented without thousands separators, e.g., "1000".

  • ES-8859: The result type of the ROLLUP aggregation has changed. Previously, ROLLUP would always return a numeric result. Now, ROLLUP can return a non-numeric result, e.g., a text or a date.

  • ES-8923: The behavior of the ROLLUP aggregation has changed. Previously, ROLLUP would calculate the aggregation for all levels of a hierarchy. Now, ROLLUP only calculates the aggregation for the top level of a hierarchy.

  • ES-8946: The default aggregation type for new nodes has been changed from SUM to AVERAGE.

  • ES-8963: The behavior for nodes that have both a formula and a value set has changed. Previously, the value would override the formula. Now, the formula will override the value.

  • ES-8972: Changed behavior when importing a project that has models with nodes that have both a formula and a value set. Previously, the import would fail if the formula and value were in conflict. Now, the import will succeed and the formula will override the value.

  • ES-9013: The behavior of the ROLLUP aggregation for non-numeric data has changed. Previously, ROLLUP would return null for non-numeric data. Now, ROLLUP will return the last value in the hierarchy.

  • ES-9070: The behavior for formula nodes that have a circular dependency has changed. Previously, the calculation would fail silently. Now, the calculation will return an error value.

  • ES-9071: Changed behavior for formula nodes that reference nodes that do not exist. Previously, the calculation would fail silently. Now, the calculation will return an error value.

  • ES-9111: The behavior for nodes that are set to be summed (have a SUM aggregation function) has been changed. Previously, SUM nodes could be set to have a value for an individual level. Now, SUM nodes can only have a value for the top level.

  • ES-9130: Changed behavior for the export of nodes. Previously, nodes with a formula and a value set would be exported with both the formula and the value. Now, only the formula is exported.

  • ES-9148: Changed behavior for importing nodes. Previously, importing a node with both a formula and a value would import both. Now, only the formula is imported.

  • ES-9156: The behavior for filtering by a time hierarchy has been changed. Previously, the filter would include the parent of the filtered level. Now, the filter will only include the filtered level.

  • ES-9170: The behavior for the NodeTreeFilter has been changed. Previously, the filter would include the parent of the filtered node. Now, the filter will only include the filtered node.

  • ES-9203: Changed behavior for the SUM aggregation when applied to a hierarchy with missing values. Previously, the SUM would return null if any value in the hierarchy was null. Now, the SUM will return the sum of all non-null values.

  • ES-9230: The behavior of the ROLLUP aggregation when used with a date hierarchy has changed. Previously, ROLLUP would use the date of the last level in the hierarchy. Now, ROLLUP will use the date of the first level in the hierarchy.

  • ES-9251: Changed behavior when running a simulation that has nodes with missing values. Previously, the simulation would fail if any node had a missing value. Now, the simulation will use a default value of 0 for missing values.

  • ES-9299: The behavior for nodes that have a value set for multiple levels has been changed. Previously, the value for the top level would override the values for the other levels. Now, the values for the other levels will be used as well.

  • ES-9357: Changed behavior for how Valsight handles null values in the calculation engine. Previously, null values would cause unexpected results in some calculations. Now, null values are handled more consistently and predictably.

  • ES-9386: The behavior for the export of assumption groups has been changed. Previously, assumption groups would be exported with all their members. Now, assumption groups will only be exported with the members that are relevant to the model.

  • ES-9408: Changed behavior for the NodeTreeFilter when used with a time hierarchy. Previously, the filter would include all levels of the time hierarchy. Now, the filter will only include the levels specified in the filter.

  • ES-9424: The behavior for nodes that are set to be averaged (have an AVERAGE aggregation function) has been changed. Previously, AVERAGE nodes would include null values in the calculation. Now, AVERAGE nodes will exclude null values from the calculation.

  • ES-9436: Changed behavior for calculating the simulation run for a workspace that has been deleted. Previously, the simulation run would fail if the workspace had been deleted. Now, the simulation run will use the last known state of the workspace.

‌

General Information:

  • The minimum supported version of Valsight for upgrading to 6.0.x is 5.3.x.

  • The Java requirement for self-hosted installations has been changed. Java 11 is now required (up from Java 8).

  • The Valsight desktop application now requires macOS 10.14 (Mojave) or later.

‌

6.0.0

LTS - Major Release

Warnings

  • ES-8306: The export format of the Valsight model has been changed. A model exported from 5.x versions cannot be imported into 6.0.0.

  • ES-8328: The export format of Project Spaces has been changed. A Project Space exported from 5.x versions cannot be imported into 6.0.0.

  • ES-8356: The REST API has been updated. Clients using the REST API will need to update their integrations.

  • ES-8374: The behavior for calculating the simulation run for a workspace that has been archived has been changed. Previously, the simulation run would be calculated with the archived workspace's data. Now, the simulation run will be calculated with the current workspace's data.

  • ES-8392: The behavior for nodes that have both a formula and a value set has been changed. Previously, the value would override the formula. Now, the formula will override the value.

  • ES-8411: The behavior for the SUM aggregation when applied to a hierarchy with missing values has been changed. Previously, the SUM would return null if any value in the hierarchy was null. Now, the SUM will return the sum of all non-null values.

  • ES-8432: The behavior for nodes that are set to be summed (have a SUM aggregation function) has been changed. Previously, SUM nodes could be set to have a value for an individual level. Now, SUM nodes can only have a value for the top level.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close