Please Add Score Staleness Logic

Currently, if you want to set a score to be stale in a scorecard, you set it on a per-measure basis. There is no additional configurability - it applies to all customers with that scorecard (no segmentation), and all values of that score.

Here’s the context:

We have a manual score we want our CSMs to update. The scheme is Red/Yellow/Green. When the score is “Red”, we want CSMs to update the score every 2 weeks. When the score is “Yellow” or “Green”, we only need them to update it once a month.

While we currently don’t have this use case, it may also be helpful to have criteria for other types of segmentation for staleness, without having to create a bunch of scorecards just to handle this.

Request: Please give us some logic/filter criteria so that we can be more granular with when a score needs to be refreshed.

I know we have the ability to set scores to NA as a type of workaround, but that has its own drawbacks and this request is specifically to use the existing staleness feature and not need another rule-based workaround.