How to trigger update action before saving configuration

We've run across quite a few issues where our users are changing values in their configuration and pressing save without pressing the update button in the configuration first. This is causing pricing to be incorrect, as the rules aren't running to recalculate. Is there a way to force the update action to run when the save action is run as well? Or is there any way to block the save action until the update action has been completed after any changes were made at all?