October 2018 – Release History

Release 2018.21

Projections can now be compared in the Change Management module!
Model point fields can now be converted to product variables and vice versa, via a new “convert” icon next to each field and in the variable details:
This conversion process maintains all formula references to the field or variable from other variables.
A new type of system variable, “Projection Period” is now available in all variable editors. This variable returns the projection period (in months) from the projection.

Selecting nodes in the relationship view now loads that node’s formula into the lower pane, so users can more easily peruse the various dependencies and how they interact.
Adjustments have been made to the variable editor to reduce the number of situations in which double scrollbars appear on the variable list.
Formulas referencing input tables are now validated when making changes to the input table’s columns.
Improvements have been made around yield curve point validation so users get immediate feedback.
Yield curve points must now have unique names, for reporting purposes.

Fixed an issue causing the scenario table selection to get cleared out when saving projection period or start date on a projection template.
Fixed an issue causing certain formulas to be interactive on the relationship view.
Performing integer arithmetic in the calculation engine that causes an overflow now reports an error appropriately.

Each node in the Relationship View can now be expanded further, allowing traversal up and down the entire variable dependency chain. For example, here is a view showing the dependencies from a model point field all the way up to a company variable.

More performance improvements have been made to the calculation engine. Users should see reduced runtimes on nearly all projections.
Product Sets and Allocations must now have unique names, for reporting purposes.

Fixed an issue causing projection status to sometimes report as “Completed” instead of “Completed with Errors” when only model point errors occurred.
Fixed an issue where restarting a failed scenario did not always clear the error message after that scenario was successfully run.
Fixed a caching issue when running a large number of scenarios at once (100+) that caused some of the scenarios to fail and need to be restarted.

A new, “static” processing mode has been added to the calculation engine. This can greatly improve performance and efficiency for certain types of products. By default, the calculation engine will automatically detect if a product can be calculated in this way, but there is also an option on projections to override this and force all products to be calculated in this way. For more details about processing order and options, check out our help site articles!
New icons have been added to the Model Development and Assumption Management headers which allow quick navigation between the two modules within the same model.

Significant performance improvements have been made to the calculation engine across all variable types.
There is now a link available on each node in the relationship view that allows the user to navigate to the entity in a new tab/window.
A read-only version of the formula is now displayed below the relationship view on each variable. The panel is adjustable to allow for more space for the diagram, if needed.
Projection names can now be updated when duplicating a projection. By default, a timestamp is appended to the end of the name.
Currencies and Variable Rates must now have unique names, for reporting purposes.
Minor improvements have been made to the calculation engine to allow for more retries in case of transient failures.

Fixed an issue that prevented cancelling of a scenario run in certain situations.
Fixed assumption set table association removals when deleting a data table.

Upgraded several 3rd party libraries/frameworks for performance and security patches.