Hi Camilla, and welcome to the community!
Yes, this is a critical concept and it can be done.
One approach is to use the new Actions feature to track when changes meeting your requirements occur and do something. Like - when a record is updated.
When a record is updated, you don’t really know if the risk score has changed, but you do know that something changed. This is not ideal because you will be firing the action for every record change, whereas, the risk score is perhaps changed less frequently. Actions do not grow on trees; they do have limits, so you need a less aggressive approach.
Here’s how I do it - note, I am biased toward an integrated, low impact solution that is elegant.
Add a new field -
Previous Risk Score.
Create a script action that tests if the field
Risk Score is different from
Previous Risk Score; it should run nightly unless you need real-time tracking (that’s a different solution).
If the values tested are different, update the
Previous Risk Score with the new value; if the values are the same, nothing has changed and the script action can stop without processing #4 below.
If the value has changed, in the same script action create an “analytic” record in a new table we’ll call “Risk Tracking Analytics” that tracks all
Risk Score changes. This new record will be added every time the action sees the score change and it will include the previous value and the new value as well as a date/time.
Create a chart using the Chart block to plot the changes over time using the new Risk Tracking Analytics table.
Have a fine beverage while you watch it update from the beach.