Migrate Legacy Policies to the Enhanced Transaction Security Framework

Let's first review ways that the enhanced transaction security framework improves your experience of creating a policy and how the policies are so much better.

• With the enhanced transaction security framework, you can create policies that execute actions on any standard or custom object. In the legacy framework, you’re limited to a few standard objects. For example, the legacy Data Export policy type supports actions only on standard report types. Enhanced policies based on ReportEvent support all standard and custom report types. (However, this benefit has the consequence that enhanced policies execute more often than legacy ones.See Differences Between the Legacy and Enhanced Apex Interfaces).
• Enhanced policies are based on publicly documented Salesforce objects. As a result, you can quickly view the available conditions by scanning the event object’s fields in the API documentation, such as for ApiEvent.
• The enhanced framework includes Condition Builder, a declarative point-and-click tool that requires no Apex coding. If you prefer to code, or need more complex logic, the enhanced Apex interface is more intuitive and easy to use than the legacy one.

Legacy policies are incompatible with the enhanced transaction security framework. And because the legacy framework is being retired, we encourage you to migrate your policies as soon as possible.

Follow these high-level steps to migrate your policy.

1. Choose the Real-Time Event Monitoring event for your enhanced policy.
2. Choose the fields of the event object that you use as policy conditions.
3. Decide whether to use Condition Builder or Apex to create your enhanced policy.
4. If you’re using Apex, read how the legacy interface differs from the enhanced interface.
5. Create your enhanced policy, but don't enable it yet.
6. Test your enhanced policy.
7. When your enhanced policy is ready, disable the legacy policy and enable the enhanced policy. You can’t enable two policies on the same event at the same time.
8. If your enhanced policy isn’t working as you expect, troubleshoot the issues.

This guide uses the Lead Data Export policy as the running example. This example is a legacy policy that was provided for all customers in the Salesforce UI in orgs created before the Spring '20 release. Orgs created after the Spring ‘20 release no longer include these policies. Check out the Follow Along with the Lead Data Export Example sections, which highlight parts of the example to explain the accompanying conceptual information.