Migrate Legacy Policies to the Enhanced Transaction Security Framework (Previously Released Critical Update)
Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions where Event Monitoring is enabled.
When: After we retire the legacy framework in the Summer ’20 release, the legacy policies will be permanently disabled and you won’t be able to update them. Your legacy policies continue to work correctly until the Summer ’20 release.
Who: Event Monitoring is available to customers who purchased Salesforce Shield or Event Monitoring add-on subscriptions.
How: To determine if your security policies are using the legacy framework, check their associated Apex classes. Legacy policies implement the TxnSecurity.PolicyCondition interface.
To migrate a legacy policy, create one in the new enhanced framework that mimics the old behavior. Although a legacy policy can’t run in the new framework, it’s still visible, so you can examine its logic to reproduce it in the new policy.
If you like using a point-and-click tool, Condition Builder provides most of the functionality to create a policy in the new framework. If you prefer to code or require more functionality than Condition Builder provides, implement the Apex class with the new TxnSecurity.EventCondition interface.
We welcome feedback about the migration and any issues that you encounter so that we can improve the transition for all Event Monitoring customers. You can provide feedback and suggestions for this feature in the Salesforce Official: Shield group in the Trailblazer Community.