Calculation Improvements

If you have a table with a large number of records, each record with a number of calculations, some of which use today’s date in them, your Exchange could start needing to check large volumes of records each night.

Within the admin area of your Exchange, your Configuration Specialist can set some rules per table so that records which have not been modified since before a given date are not sent to the processor each night to recalculate, e.g. to update rolling number of lost days, or to send out reminder emails when an action is 7 days overdue. You may determine that records in a given table which have not been modified since before a certain date likely do not need to be processed each night. If they are edited and re-saved, they will have been modified since that date and therefore would start to be processed nightly again.

The change we have released is an extension of the above. Rather than a static date which would need to be updated regularly to be of most use, we can use a number of days. In this example, you may wish to apply a restriction to a table where it is not processed nightly unless it has been modified in the last 2 years (730 days).

This is just the latest addition to other tools we use, such as scheduled calculations. If you feel that there are tables within your Exchange which could benefit from this type of restriction, please speak to Helpdesk.

•Customers may have lots of different types of calculations in each record across their system. Customers accumulate many records which means that some Exchanges process a large number of calculations each night.

•Large numbers of background calculations negatively impact user experience and contribute to hosting costs.

•We can choose to not calculate a given record if it has not been modified since a given date, but this date is static so not practical to regularly update this as a maintenance task