Change where new content is saved
![change where new content is saved change where new content is saved](https://www.thedigitalmediazone.com/wp-content/uploads/2016/02/windows-10-2018-new-content.jpg)
#Change where new content is saved code
You can even avoid the limit for maximum CPU time on the Salesforce servers by replacing Apex code and record-change processes with before-save updates in flows.
#Change where new content is saved update
In a save procedure, before-save updates in flows are executed immediately prior to Apex before triggers.īecause of their speed, we recommend that you use before-save updates in flows to update fields on new or changed records. The previously described record-change process is similar to an after trigger. A flow that makes before-save updates is similar to a before trigger. Perhaps you’re familiar with Apex triggers. Avoiding that extra save procedure means skipping another round of assignment rules, auto-response rules, workflow rules, and other customizations that take time to execute. Before-save updates in flows accomplish that same goal, but much more quickly because each record doesn’t get saved to the database again. Such a process can set the Region custom field automatically on each new case record.
![change where new content is saved change where new content is saved](https://cdn.windowsreport.com/wp-content/uploads/2014/10/change-save-location-windows-10.png)
![change where new content is saved change where new content is saved](https://www.thedigitalmediazone.com/wp-content/uploads/2016/02/windows-10-2018-storage.jpg)
Perhaps you’re familiar with Process Builder and using a record-change process to make additional updates to each record that triggers the process. To activate a flow that makes before-save updates, an app builder needs the View All Data permission. Replace your record-change processes with flows to minimize how often the spinner appears when users save records. For example, a before-save update in a flow is 10 times faster than an update in a record-change process that’s built in Process Builder. Before-save updates in flows are much faster than other available record-triggered updates. In Spring ’20, app builders learned that in Flow Builder they can trigger a flow to run before a record is saved.Ĭreating or updating a record can now trigger an autolaunched flow to make additional updates to that record before it's saved to the database. Update New and Changed Records by Using Before-Save Updates in Flows