NEW
Improvement Scales
Slope now supports both Standard and Generational Improvement Scales for the purpose of applying a decrement improvement rate. Improvement Scales can be created directly within the Slope interface or imported from an excel file. Documentation on how to create an improvement scale and how the improvement rate is applied can be found here.
Coming Soon: In future releases, users will be able to merge a table structure with a nested decrement table and improvement scale, switch between improvement scales using the drop down list under the improvement scale’s name and see additional validation when editing decrement tables and improvement scales.
New Explore for Comparing Model Points between Projections
The new Model Point Comparison Explore allows users to compare model points between projections for the purpose of identifying differences, including new and terminated model points. This Explore includes both Model Point Fields and Results (variable calculations).
A Left and Right Join Variable Name and Left and Right Projection ID filter is required for this Explore. For the Join Variable Name, select the common variable between your projections’ model points that serves as your unique identifier for comparing data (ex: Policy ID). Then provide the IDs for your two projections in the Left and Right Projection ID filter. Finally, select the fields you wish to display and any filters you wish to apply to the displayed data.
Note: In Left and Right Variable Results, the Filter only fields filter data before the join occurs. The fields found under Dimensions will filter after the join occurs.
CHANGES
API Updates
The Post Data Tables and Post Scenario Tables endpoints have been updated to use “name” instead of “description” to match the interface updates. Additionally, the rate limit for the SLOPE API was increased to 10 calls per second.
FIXES
- The description from the table structure will again display upon hover over a data column on a data table.
- Improved performance for projections that use large data tables with range lower bound lookups.
- Empty booleans on data tables will now be treated as false rather than erroring on a projection.
- Decrement Tables will import without error when they are used in a nested data table following a versioning event.
- Improved Result Writing stability to reduce the need to restart a scenario.
- Projection status will no longer fail to update when ‘output all results’ is enabled and the error limit is reached.
- Improved calculation engine stability to increase projection completion success.