Release Notes Plauti Restore
Release 2026 R4, June 15, 2026
| Release | 2026 R4 (0.11.0.0) |
| Release date | June 1, 2026 (Sandbox) / June 15, 2026 (Production) |
| Improved | - API - All of Plauti Restore’s triggers and Apex Classes have been updated to API version 66.0. - Restore Setup - Quickly switch between Setup pages of all of Plauti’s Apps, and find out more about the ones you aren't using yet. |
| Classes added | If you are not using the Plauti Restore permission sets, add the following classes to the applicable Admin and User profiles: - prTelemetryController |
| Fixed | - Restore Setup - A configured Object that no longer exists in the Org can now be removed properly again. |
Release 2026 R3, April 20, 2026
| Release | 2026 R3 (0.10.0.0) |
| Release date | April 7, 2026 (Sandbox) / April 20, 2026 (Production) |
| New | - Change Details - A Change Information modal was added with more record, merge, and restore details. In the Restore Changes overview, click a change’s name to access it. - Restore Audit - Restores are not removed from the Restore Changes overview anymore, giving you a permanent audit trail for every rollback. Changes that were logged but not restored are still removed according to your retention settings. |
| Improved | - Changes Overview - Merge changes are grouped in Multi Merges to clearly display the master record together with its merged loser records. Click ‘Restore’ at the master record to restore all loser records together in one go. - Changes Overview - Restores now display a restore status (Success, Partial, Failed) after a restore operation completes. This helps identify issues that require manual attention. - Object Configuration - When configuring objects for tracking, you are warned if Track Updates or Track Merge is enabled without any fields or related objects configured. Furthermore, the Tracked Related Objects overview now includes a Priority column, to make it clear which related objects will be restored first. In large or complex orgs not all related records might be restored due to Salesforce governor limits. Read more here. - Restore Setup - View the storage usage of tracked changes, broken down by change type (Insert, Update, Delete, Merge) in a chart displayed on the Setup Home dashboard. |
| Fixed | - Restore Merge - In some cases, related records were not restored correctly after restoring a merge. - Restore Setup - Deployment failures now display the correct error message. |
Release 2026 R2, February 23, 2026
| Release | 2026 R2 (0.8.0.0) |
| Release date | February 9, 2026 (Sandbox) / February 23, 2026 (Production) |
| Update Instructions | If you are currently tracking merges, make sure to configure which related Objects are tracked. Without any related Objects configured, no related Objects will be restored when restoring a merge. Take care to configure this as soon as possible after your Org was updated to this version, particularly when automated merging processes are in place. Watch this video for an extensive explanation, or read more here. |
| New | - Merge Tracking - Configure which related Objects are tracked during merges. For records with a large number of related Objects, or a few complex relations, this ensures the most important related Objects get priority upon restore. Without this setting configured, related Objects will not be tracked for recovery anymore. If you are currently already tracking merges, and want to be able to restore related Objects, make sure to configure this setting! Read more here. |
| Improved | - Restoring - Restore multiple changes at once. Select up to 20 changes from a change list view to undo in one go. |
| Classes added | If you are not using the Plauti Restore permission sets, add the following classes to the applicable Admin profiles: - prSObjectService |
| Fixed | - Permissions - Non-admin users that do have one or both of the Plauti Restore permission sets can now merge records again with merge tracking enabled. |
Release 2026 R1, January 26, 2026
| Release | 2026 R1 (0.7.0.0) |
| Release date | January 12, 2026 (Sandbox) / January 26, 2026 (Production) |
| Fixed | - Undo Merge - In some cases, records could not be restored if that would result in duplicate records. |
Release Winter '26 Features, December 1, 2025
| Release | Winter '26 Feature release (0.5.0.0) |
| Release date | December 1, 2025 |
| Improved | - Restore Merges - Previously, when undoing a merge, the master and loser records were all restored; but if upon merge some field changes had been made to the master record, these needed to be restored individually. Now, when undoing a merge, the master and loser records are all restored to their previous state before merging. Any field changes made to the master record upon merge are undone as well. |
| Classes added | If you are not using the Plauti Restore permission set, add the following classes to the applicable User and Admin profiles: - prGenericStorageRepository - prSettingsMutex - prInAppNotification - prInAppNotificationController - prInAppNotificationRepository - prInAppNotificationScheduler - prInAppNotificationService |
| Other items added | If you are not using the Plauti Restore permission set, add access to the following Object to the applicable User and Admin profiles: - PRGenericStoragec |
First Release, October 6, 2025
| Release | Winter '26 Maintenance release, First Release (0.4.0.0) |
| Release date | September 22, 2025 (Sandbox) / October 6, 2025 (Production) |
| New | - Welcome to the first edition of Plauti Restore! Undo Merges and other field and record changes with the new Plauti Restore solution. Keep track of changes: merges, inserts, updates and deletions, on Objects and Fields you define. Restore changes including related data to revert accidental modifications. Restore from the main Changes overview, or from a custom record tab. Read more here, or watch the video. |