May 2023: Projection Workflows, Search for Operand in the Formula Editor, New Navigation & More

New

Projection Workflows for Sensitivity Analysis & IFRS 17

Clients can now group and kick off multiple projections in a workflow to allow for easier setup, execution and reporting. The most common use cases for using workflows include IFRS 17 reporting and sensitivity analysis which both require running multiple projections. For information on how to create and run a workflow, visit our support documentation here.

Search for Operand in Formula Editor

Users can now type to search for an operand (variable, data table, formula, etc) for faster formula creation.

After clicking the formula wheel icon (orange circle with three bars), simply begin typing to search across variables and formula types. In the example below, searching for Lapse returns several variables and data tables to select from. Upon choosing the desired operand, you will be prompted to provide any additional details.

Enhancements

Updated Navigation & Projection Changes

The top navigation menu has been updated to provide more descriptive labels. We have also combined the Execute and Analyze modules into a single module now called ‘Projections’. Selecting a projection that has not been run or that is actively running, will open the Projection Details screen. Selecting a projection that has been run, will open the Workbooks screen so you can view results.

In addition to these navigation updates, clients can now duplicate not started and running projections.

View Relationships for Model Point Fields

Users can now view the relationships for Model Point Fields from the Model Point File Definition using a new option within the action menu found next to each field.

Model Copy No Longer Includes Unnecessary Table Structures and Tables

When copying a model (e.g. The Slope Life Library) and selecting some but not all products, the table structures and tables that are not used by the selected product(s) and portfolio(s) on the copy will be removed from the copy. This is to eliminate unnecessary tables from showing up in models and projection templates.

Model Comparison Performance Improvement

The Model Comparison feature found within the Model Governance module is now faster allowing for a quicker review of differences between two models.

Default Cursor in Modals

Now the cursor will default to the first field in a modal so that users can immediately begin typing into the first field without first having to select or click in the field. (e.g. Name on the Create New Variable modal)

Ability to Map Array Values when Merging

Users can now map array values when they are merging a variable with a formula that uses a static array with single value aggregation so that their formula is valid in the target model following the merge.

Fixes:

  • Files with special characters in the worksheet name can now be uploaded without error.
  • The correct excel row # for errors will now be reported when loading model point files (previously off by 1).
  • Projections run with models that are set to “Copy Only” are again showing in the projection list.
  • The Merge module will now show all arrays when merging a variable with a formula that references a static array with single value aggregation set or a constant with a data type of array.
  • When merging an IRR formula, the Merge module will detect and show differences for the Behavior and On Failure (warn/ignore) fields.
  • Run Logs are again available for projections that Failed to Start.
  • Users should be now be able to consistently access Slope Academy when logged into the Slope application.

April 2023: Use a Formula to Read a Model Point Field by Name, Virtual Folders on Projection Templates & Sunsetting Snapshots

New

Use a Formula to Read a Model Point Field by Name

Users can now select a Model Point Field by name using a formula as a more dynamic alternative to selecting a single field by name from the drop down. All formulas that return a string value are considered valid in the variable editor. When the projection is run, Slope will attempt to match the string value to a Model Point Field name and will error if there is not a match.

In this example, the number of annuity accounts can vary from one plan code to another. The formula finds the correct initial balances for starting a projection using a table read.
The Initial Balance MPF column in this data table indicates which model point field should be used.

Enhancements

Virtual Folders on Projection Templates

Users can now select a folder on a projection template so that all projections run from the template are automatically organized into the set folder.

Sunsetting Snapshots

Users will no longer be able to take new snapshots of models. The best approach for preserving a model at a point in time (e.g. after year end valuation) is to set the model to Copy Only using Model Permissions and make all edits to a new copy.

This approach makes it easy to compare the Copy Only (former version) with the edited version using the Manage model to review all changes made to the model.

Additional Information available Available on the Debug View for Arrays

  • When only some of the static array values were run in a projection, the calculated values will display and those that don’t have results will indicate that there is no result available.
  • Array values deleted after the run will be displayed as struck through and explain the value no longer exists.
  • When a variable is changed to be an array variable after the run, and there is a single formula for an array (e.g. dynamic array) the formula will be displayed in the debug view.
  • When there is a result without an array value we will show the result with no array value selected.

Fixes

  • Empty data cell values on data tables are no longer causing unknown errors.
  • The control panel has been removed from the Error report displayed on the Run Logs tab.
  • The Asset Allocation page is properly reloading after an asset is deleted following the use of the search panel.
  • The header of a data table is no longer included in the row count of an error message.
  • Merging a table structure change will now trigger data table versioning on the destination model.
  • Model validation is now being triggered when merging a portfolio or product.