One of the main goals for the December 2012 Service Update release is to have a clean and modern user experience. Modern applications are moving to an implicit save model and we need to adapt to that model. With the new updated forms, we have introduced the capability of auto save and that is what I want to demystify today in this blog.
It appears in the bottom left area of Updated User Experience forms for Contact, Account, Lead, Opportunity and Case as shown in the following screenshot.
The following are the different states of the auto save control
Since this is an update call to the server, the following will get fired when auto save occurs.
Please be aware of this when you write your plugins and workflows and consider using the updates of specific fields to initiate actions rather than with any update.
Auto Save occurs automatically in the following cases:
Auto Save does not occur in the following cases:
Not in this release.
Hopefully this post helps you to understand this new capability.
If I understood you correctly, this sounds incredibly dangerous the record is going to be saved even though the user has not completed all input. So let's say they are correcting the address and they have typed in the correct first line of the address and then get interupted - if they wait longer than 30 seconds - what gets saved is the new first line of the address, but not the new ZIP Code / Post Code (as they have not yet got around to typing this in). If there is then (say) a workflow to notofy someone that the address has changed - this will fire off on the partialy completed address!
Am I correct in my understanding.
In my opinion it is not dangerous! Even, i is very helpful!