***IMPORTANT UPDATE: Change to Auto-Save Behavior in Performance Management***
Please be aware that the auto-save functionality explained below in this KBA has been changed from 5 seconds of inactivity to 2 minutes of inactivity.
***UPDATE June 2020 *** We are currently working on some performance optimizations, because of that the Autosave interval might be temporarily adjusted to less than 2 minutes in some of our DCs. Please stay tuned for future updates on this topic in this KBA and the Community post.
What is the impact to customers?
- The auto-save functionality (which previously saved data after 5 seconds of user inactivity) was modified to now save after 2 minutes of inactivity. Many users are accustomed to having their data auto-save frequently and therefore may not manually save. It is imperative that customers communicate to their users to manually save often.
What happened that triggered the behavioral change?
- In late October, Operations detected a dangerously high spike in HANA DB CPU usage
- Operations traced the high DB CPU usage spike in multiple DCs to the auto-save concurrencies on the Performance form
- If left unchecked, the spike(s) had the potential to cause a major service disruption for customers
What measure did SAP SuccessFactors take to mitigate the risk?
- Our chief concern was avoiding major service disruption to customers – especially moving into peak season
- Short term decision reached in early November to increase the auto-save interval to cut down on DC CPU usage
- Operations in coordination with Engineering and Product decided to increase the auto-save interval to 2 minutes (i.e., after 2 minutes of inactivity the form will save)
- Engineering and product teams are evaluating both short and long term options to improve the end user experience
System Timeout vs Auto-Save:
Many customers have asked about the relationship and difference between System Timeout and Auto-Save. It is important to understand the differences as this change to the PMv12A form only applies to the Auto-Save functionality. The System Timeout functionality remains as is.
System Timeout - occurs if the system does not detect any interaction between the browsed page and the backend server. Any activity on the form that doesn’t involve interaction with the backend server, for 30-minutes non-stop, would lead to a session timeout If a user for example, clicked “Save” or edited an item, the system will detect it as interaction between the form and the backend. And therefore the “timer” is reset to 30 minutes.
Examples of non-interaction are – typing in a comments box, clicking on a rating, and scrolling. Conceivably if a user is typing in a comments box for 30 minutes non-stop if they do not actually save, they could lose their data after 30 minutes
Auto-Save - occurs when there is no detected activity within the Performance Form after a globally prefixed time interval. This is helpful in cases where there is no backend interaction, such as entering comments, as it ensures the data will save
Further updates on this change will be communicated via this KBA and the Customer Community.
To subscribe to changes to this KBA, select the star icon at the top of this article to "Mark as Favourite".
This KB article explains how the auto-save functionality works on the Performance Form
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
SAP SuccessFactors Performance Management
PMGM, PM, 360, Multi-Rater, multirater, MTR, Review, refresh, auto-refresh, seconds, 5, five, 2, two, minutes, UI, beta, limitation, OCOC, summary, obj-comp, summ-sect , KBA , LOD-SF-PM-FRM , Forms & Templates , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.