On April 6, Salesforce.com is releasing an update that may affect your org if you have an "after update" or "after insert" Trigger that affects workflow or summary rollup fields.
The critical update affects the way the Force.com platform evaluates workflow rules and roll-up summary fields on objects that fire Apex triggers. The update aims to improve the accuracy of data and prevent the reevaluation of workflow rules in the event of recursive operation. Recursion is a situation in which a part of your Apex trigger logic causes the Force.com platform to execute other logic (a workflow or roll-up summary field) twice when saving a record. We ran into this issue when developing our own custom lead assignment processes and studied the trigger and order of execution internal event processing.
It looks like the update may affect alot of customers based upon the criteria of the "after update" or "after insert" trigger that performs any of the following operations:
- Updates the current record
- Updates any child record of the current record, and there is a roll-up summary field on the current record
- Updates any unrelated object that has an Apex trigger which updates the current record
