Trigger handler management during data migration
Key Takeaway
In an environment that's live with active users, run data loads as an integration user with the "Skip Life Sciences Trigger Handlers" permission, because the bypass applies only to that user. Turning handlers off in the "Admin Console" affects all users, so it suits environments that aren't live yet.
Life Sciences Cloud uses trigger handlers to keep data consistent as records change. During a data migration, leaving every handler on can slow loads or hit governor limits. As the consultant, you decide which handlers to bypass or disable during the load. You also decide which jobs to run after the load to do the handlers' work in bulk.
What trigger handlers do
Trigger handlers maintain data sanity, which means they keep data consistent. For example, some handlers sync fields on healthcare provider records. Other handlers lock visits after they're submitted.
During a data migration, keeping all handlers enabled can slow performance or hit governor limits. So before you decide what to turn off, understand the purpose of each handler.