Performance Alerts: special development considerations
The Performance Alerts are all set up on the actual application, and NOT in the builder.
For very specific performance alerts and you may need to set up specific fields in your form to calculate historical information to get the most from the performance alerts
When you create a new performance alert for a numeric field you can select to be notified of anything from % change to a new personal best. However, most of the alerts are based on the last value entered to the next value. It does not work over a set number of days or a specific time period.
If you want to know if there has been a specific change over a certain time period then you need to set this up as a historic calculation IN the actual event form on the builder application and then go back to the application to set up the performance alert for that specific field.
To add in a specific time based field to calculate out change you need to use a Historical Calculation
For this example we are calculating the difference from Yesterday's weight to today's weight. If there is no value entered for yesterday, the calculation will not calculate and the equation will be left blank. If you wrote it as:
safe (lastvalue(Historical Today's Weight ))- Today's Weight it would calculate out 0- Today's weight to give a negative number which would set off an alert.
Other types of historical calculation used include setting a maximum, minimum and mean of a value over a specific time period (e.g. sleep over the last month)
If you want the calculations to be hidden and not show during the data entry, in the field's advanced properties set default shown in table=no
DO NOT set the field up as a hidden field or it will not appear in the selection on the performance alerts field selection list. But you can select it to be hidden by default in tables.
Alternatively, you could set up an additional section in the form where the entire section is hidden based on specific visibility settings so that they don't appear during data entry (as shown below).
N.B. Always ensure you enable the Autocalculate so that it can recalculate if you update data in the event form.
An example of adding all of of the additional calculations in a section with visibility settings for it to be hidden.
No go back to the application and set up the performance alerts you require based on these historical calculations
Create a new Performance Alert based on the new fields in your form e.g. decrease in average hours slept
Or even if average hours slept drops below 6 hours for the month
ALWAYS test your performance alerts and the historical calculations on a demo athlete to ensure that you have set it up correctly
Always go to into the event form and enter in a data for a test or demo athlete to ensure that the field is set up correctly in the form, and also that the performance alert is set up correctly. If may mean entering a months worth of fake date for one athlete, but it is better to get it right than miss the critical information that you need.