top of page

Save Buttons? Where We’re Going, We Don’t Need Save Buttons.

Updated: Jun 11, 2021

And if my calculations are correct, you're going to see some serious autosaving. Let us explain how it works.

The Autosave Feature

This isn't as complex as time travel in a movie, but in order to understand this better, let's review how the typical save process works.

  1. Open a record edit screen.

  2. Update information in a field.

  3. If the 'save' button is clicked, the form closes and it goes back to the start. In order to avoid clicking 'save' and having to reopen the edit screen many times, we keep adding information without saving. However, the longer we wait to save, the more information we risk losing by not sending to Salesforce.

What a paradox!

Then there's always the possibility we don't have all the required information or we encounter an error or validation rule that prevents a successful save at all.

Enter the Rukblik Autosave. When using the Rukblik edit screen, it automatically saves field edits as a draft after changes are detected. This is great because it relieves us of all the problems in step 3 of the typical save process. With autosave as a draft, the process looks like this.

  1. Open the Rukblik edit screen.

  2. Update information in a field.

  3. If there are no further field changes, they are saved as a draft and the screen stays open. The more changes on the form, the more information is saved. And the data will be saved no matter how complete/incomplete or whether there are errors or validation rule issues because it's saved as a draft.

Whoa, this is heavy.

What does it look like? The Rukblik edit screen has visual indicators not seen in a standard edit screen. They are;

  1. A 'Last Saved date/time',

  2. Vertical red lines to show which fields are required on the page layout before publishing.

  3. Green highlighting for fields that are saved as part of the draft.

  4. Orange highlighting for fields that are saved as part of the draft and will overwrite the field value on the record when published.

  5. A toggle button to enable/disable autosave.

For comparison, here is the standard edit screen without an autosave.

In summary, we can replace the typical 'save' button save process with Rukblik autosave to guarantee field edits are saved automatically, regardless if information is complete, an error occurred or a validation rule has fired. The Rukblik edit screen remains open and visual indicators show which fields are saved and which will overwrite values on the record when published.

In the next post we'll talk about the Save Preview future, I mean feature.

67 views0 comments

Recent Posts

See All


bottom of page