# March 2026 Release Notes ## GRAX Product Updates ### March 2026 March was a strong month for data fidelity and transparency. We shipped meaningful improvements to how GRAX captures and displays rich content, gave you more control over archive operations with related records, and launched an audit log so you can see exactly what's happening in your org. We also continued investing in sandbox seeding reliability and data lake flexibility. *** ### Backup & Restore #### Images in Rich Text Fields Are Now Backed Up and Displayed **What Changed:** GRAX now backs up images embedded in Salesforce Rich Text Fields — including inline images referenced from records and displays those images correctly when you view records in the GRAX Console. **Why This Matters:** Previously, rich text content in GRAX could appear with broken or missing images. Now what you see in GRAX matches what's in Salesforce. This applies automatically to your existing and future backups with no configuration required. *** ### Archive #### Archive Now Lets You Include Related Child Records **What Changed:** When setting up an archive job, you can now choose to include all related lookup child records automatically, or select specific child objects manually from a relationship tree. **Why This Matters:** Archiving a parent record without its children could leave orphaned records in Salesforce or result in incomplete data sets. This new control lets you archive related data cleanly in a single operation, reducing follow-up cleanup and improving data integrity across your org. *** ### Search #### Content Documents with Backed-Up Assets Are Related to Parents **What Changed:** GRAX search identifies Content Documents that have associated backed-up assets as non-orphaned records. **Why This Matters:** These documents were previously appearing as "orphans" in search results, which could be misleading and affect how you managed your archived data. Search results now reflect the actual state of your data more accurately. *** ### User Interface #### Recurring Activity List Now Loads All Pages **What Changed:** The recurring activities list now supports infinite scroll, allowing you to page through all of your recurring backup or archive jobs without hitting a cutoff. **Why This Matters:** If you manage a large number of recurring jobs, you were previously limited to viewing only the first page. You can now scroll through the full list without any workarounds. *** #### Clearer Behavior When GRAX Is Disconnected from Salesforce **What Changed:** When GRAX is in a disconnected state, backup-related pages are now appropriately limited, and object search in the header is disabled to reflect that live data isn't accessible. **Why This Matters:** Previously, disconnected mode could leave some pages in an ambiguous or partially broken state. The UI now clearly reflects what's available. This reducing confusion about what's happening and why certain actions aren't available. *** ### Sandbox Seeding #### Seed Jobs Now Include Optional Parent Records **What Changed:** When GRAX builds a seed graph, it now includes optional (non-required) parent relationships. For example, a Product linked to an Asset, so those parent records are created or updated as needed in the target org. **Why This Matters:** Seeds that involved optional parent references could produce incomplete data sets in the target sandbox, requiring manual follow-up. Seeds are now more complete by default. *** #### Sandbox Seeding Batch Limits Now Apply to Search-Based Jobs **What Changed:** When creating a seed job from a saved search, you can now set a record limit directly in the seed configuration. This is consistent with how limits work for query-based and search run-based seeds. **Why This Matters:** This gives you more predictable control over seed scope and prevents unexpectedly large seed operations when seeding from broad search results. *** #### Custom Anonymization Rules Now Available for Sandbox Seeding Jobs **What Changed:** You can now configure custom anonymization rules when building a seed job, giving you control over how specific fields are masked or transformed when data is seeded into a sandbox. **Why This Matters:** Data privacy requirements vary by org and team. Custom anonymization lets you tailor seed data to meet your specific policies without relying solely on default masking behavior. *** ### Security & Audit #### Audit Log Now Available in the Console **What Changed:** GRAX now maintains an audit log of mutating actions; including changes to backup, archive, and data lake configurations and surfaces that log directly in the console. Contact us for access to this feature. **Why This Matters:** For teams with compliance or governance requirements, this gives you a clear record of who changed what and when. You no longer need to rely on external tools or logs to track configuration changes within GRAX. *** ### How to Get the Most from These Updates **Check your archive configurations for related child records.** The new lookup children option is not applied retroactively to existing jobs. Review your recurring archive jobs and consider whether adding related children would make your archive sets more complete. **Review the audit log if you're managing a shared GRAX environment.** Navigate to the new audit log section in the console to establish a baseline of recent activity before your next compliance review. **Re-run sandbox seeding jobs if optional parent records were missing.** If you've seeded sandboxes and noticed related records were absent in the target org, the seed graph improvement means a fresh run should now capture those parent records automatically. *** ### Questions or Feedback? Reach out to your GRAX support contact or customer success team with any questions about these updates. *** *March 2026*