> For the complete documentation index, see [llms.txt](https://learn.capstorm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.capstorm.com/copystorm-restore/reference/advanced-tab.md). # Advanced Tab The Advanced Tab supports control of what Salesforce triggers, validation rules, flows, workflows, and restricted picklists are temporarily disabled during a restore. Note than any item disabled by CopyStorm/Restore will automatically be re-enabled when a restore completes or is cancelled. Why are these features necessary? Let’s look at a few examples: * There is a Salesforce trigger that initiates notifications for Opportunities larger than $50,000. During a restore running this trigger would be a bad idea. * Validation rules have changed over time and much historical data will not pass the current rules. Disable the rules during a restore. Control of the following item types is supported: * [Triggers](#configuration) * [Validation Rules](#validation-rules) * [Process Builder/Flows](#process-builder-flows) * [Workflows](#workflow-rules) * [Restricted Picklists](#restricted-picklists) * [Duplicate Detection Rules](#duplicate-detection-rules) * [Required Fields](#required-fields) * [Lookup Filters](#lookup-filters) ## Configuration * Configure the scope of automation management to include Rules and Workflows from Managed Packages. * Configure the timing of automation re-enablement. ![](https://2924009365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5FyPmqVkPxhj2oT8fbgB%2Fuploads%2Fgit-blob-a3f3b22212e540e181ff72adb7de30d074ccb607%2Fa370c4d1-AdvancedTab_Configuration.jpg?alt=media) ## Triggers Disabling triggers during a restore is a common necessity. For example, if an Opportunity trigger sends an email on large opportunity creation you will want to avoid this when restoring to a sandbox. Another common problem is triggers which are not designed to handle large blocks of records and when they receive a large block they exceed the Apex statement limit per transaction. When a trigger is added using the Edit Trigger Selection button, CopyStorm/Restore will disable the trigger at the beginning of the restore process and re-enable it after the restore completes or is cancelled. Note that on a sandbox the disablement/enablement of triggers is relatively fast, but on a production environment changing the enablement status of a trigger will cause unit tests to run. ![](https://2924009365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5FyPmqVkPxhj2oT8fbgB%2Fuploads%2Fgit-blob-91edfc2ff39cf3813a62f7dce1cb17744a2baa97%2F072e7453-AdvancedTab_Triggers_P1.jpg?alt=media) ![](https://2924009365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5FyPmqVkPxhj2oT8fbgB%2Fuploads%2Fgit-blob-13cc3402a8485cb87bc4400cba08f6314ce3c183%2F6190a8c8-AdvancedTab_TriggersDialog.jpg?alt=media) ## Validation Rules Disabling validation rules during a restore is a common process because older data will often not pass the current validation rules. In most cases, letting CopyStorm/Restore manage validation rule disablement/enablement is sufficient. When this option is enabled: * CopyStorm/Restore disables active validation rules for a table just before data is written to the table. * Once updates/inserts to a table are complete, CopyStorm/Restore re-enables the validation rules it disabled in the previous step. If updates to one table cause updates in another table (for example: an OpportunityLineItem change can cause an update to the Opportunity table) then it may be necessary to explicitly choose validation rules to disable. If a rule is explicitly selected then the rule will be disabled at the beginning of the restore process and re-enabled when the restore process completes or is cancelled. If automatic management is enabled and a validation rule appears in the explicit list then the automatic management system will ignore the rule. ![](https://2924009365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5FyPmqVkPxhj2oT8fbgB%2Fuploads%2Fgit-blob-6522e10ad5df8c7b0ec74f7e94da28653ac4ea4b%2F688f8af9-AdvancedTab_ValidationRules_P2.jpg?alt=media) ## Process Builder/Flows Disabling ProcessBuilder/Flows during a restore is a common necessity to avoid processing. For example, if an Opportunity flow sends an email on large opportunity creation you will want to avoid this when restoring to a sandbox. When a Flow is added using the *Edit Flow Selection* button, CopyStorm/Restore will disable the Flow at the beginning of the restore process and re-enable it after the restore completes or is cancelled. When a Flow is selected, the current version of the Flow is displayed. When CopyStorm/Restore disables the flow as part of the restore process, it will query Salesforce for the current active version – and disable the active version (and re-enable the disabled version when the restore is finished). ![](https://2924009365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5FyPmqVkPxhj2oT8fbgB%2Fuploads%2Fgit-blob-7908f9a98a28c2cad0f16eb4d246a816d5f88332%2F498509e3-AdvancedTab_ProcessBuilderFlows.jpg?alt=media) ## Workflow Rules Disabling workflow rules during a restore is a common process to avoid a process that normally happens when a user enters/modifies a record via the GUI. In most cases, letting CopyStorm/Restore manage workflow rule disablement/enablement is sufficient. When this option is enabled: * CopyStorm/Restore disables active workflow rules for a table just before data is written to the table. * Once updates/inserts to a table are complete, CopyStorm/Restore re-enables the workflow rules it disabled in the previous step. If automatic management is enabled and a workflow rule appears in the explicit list then the automatic management system will ignore the rule. ![](https://2924009365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5FyPmqVkPxhj2oT8fbgB%2Fuploads%2Fgit-blob-d79f68f9af768bed24bd4f7fdf0aef066d12f07a%2F970b70fd-AdvancedTab_WorkflowRules.jpg?alt=media) ## Restricted Picklists Disabling restricted picklists during a restore is a common process to avoid encountering errors with older records whose values do not meet the criteria of the current picklist definition. In most cases, letting CopyStorm/Restore manage restricted picklist disablement/enablement is sufficient. When this option is enabled: * CopyStorm/Restore disables active restricted picklists for a table just before data is written to the table. * Once updates/inserts to a table are complete, CopyStorm/Restore re-enables the restricted picklists it disabled in the previous step. If automatic management is enabled and a restricted picklist appears in the explicit list then the automatic management system will ignore the rule. Note that this element will not disabled a Global Picklist (a picklist defined outside of the confines of a specific table). ![](https://2924009365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5FyPmqVkPxhj2oT8fbgB%2Fuploads%2Fgit-blob-fc165b9f4f0a14168d3fbd42cb7a8b3d95aea33b%2Fc7f5130d-AdvancedTab_RestrictedPicklist.jpg?alt=media) ## Duplicate Detection Rules Disabling Duplicate Detection rules during a restore is a common practice needed to restore older data whose values do not meet current duplicate rule criteria. In most cases, letting CopyStorm/Restore managed duplicate detection rule disablement/enablement is sufficient. When this option is enabled: * CopyStorm/Restore disables active Duplicate Detection rules for a table just before data is written to the table. * Once updates/inserts to a table are complete, CopyStorm re-enables disabled Duplicate Detection rules. ![](https://2924009365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5FyPmqVkPxhj2oT8fbgB%2Fuploads%2Fgit-blob-8775bf8886368b0aa2590699e2ef83d6250fd3a2%2Fc85f30b0-AdvancedTab_DuplicateDetection.jpg?alt=media) ## Required Fields Disabling Required Field rules during a restore is a common practice needed to restore older data that may not have a value for a new field or a field that was not historically required. In most cases, letting CopyStorm/Restore managed required field disablement/enablement is sufficient. When this option is enabled: * CopyStorm/Restore disables the “Required” option for a field just before data is written to the field’s table. * Once updates/inserts to a table are complete, CopyStorm re-enables disabled “Required” options. ![](https://2924009365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5FyPmqVkPxhj2oT8fbgB%2Fuploads%2Fgit-blob-5389f0c207f7c00af9084a5c901c28cafb84ceb4%2Fd33a7e05-AdvancedTab_RequiredFields.jpg?alt=media) ## Lookup Filters Disabling Lookup Filters during a restore is a common practice needed to restore older data that may not have reference fields that match current Lookup Filter validations. In most cases, letting CopyStorm/Restore managed lookup filter disablement/enablement is sufficient. When this option is enabled: * CopyStorm/Restore disables the Lookup Filter rules for a field just before data is written to the field’s table. * Once updates/inserts to a table are complete, CopyStorm re-enables disabled Lookup Filter options. ![](https://2924009365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5FyPmqVkPxhj2oT8fbgB%2Fuploads%2Fgit-blob-5b3e32b7fb0c6d0b7469b704a6b7f39efba14823%2F277af7b0-AdvancedTab_LookupFilters.jpg?alt=media)