Improve calculation transparency and traceability
Add an "evaluate" function to show step-by-step calculation processes. Currently, evaluating calculations in the eTRM can be tedious. You need to rerun permutations every single time you make one change to the calculations. Having an evaluate/look in function, similar to the one in Excel that allows you to see every step along the way, would be helpful so that you do not need to check/run permutations every time. The user can have options on what CZ, BT, MAT, and other parameters they want to run the evaluate/look in function for.This can also be helpful in the MC, displaying how a calculation is evaluated for a set of parameters would be very helpful for base users.
Solutions may include:
Evaluate each calculation to a value table and the ability to export that result
Above + even when the draft is committed or published (for users)
Log in to comment and vote
Comments3
An Anonymous User
May 12
•Merged request
•2 votes
Auto-populate the API name definition in the characterization for embedded calculations
Auto Populate API name in characterization for embedded calculations.
This will allow API names to match exactly with calculations and update automatically with API name changes in other tabs, driving consistency and eliminating review time. Possibly can auto populate description with Column header name.
CA eTRM
May 12
•Merged request
•1 vote
Link API names in calculations back to the source value table and/or calculation
Right now, it is a task for reviewers and base users to trace the API names used in calculations. This makes the measure package harder to read and slow down measure package review. Propose to make the API names used in calculation a live link to the source data (i.e., value table column, calculation, and parameters)
CA eTRM
May 11
“Low priority” because the Characterization is supposed to describe the methodology, step by step, with the embeded live calculation.