Why and How we need to remove retired functionalities from a Salesforce Org
Salesforce Orgs - which are existing for more than 5 years, it is very common that some functionalities become obsolete after a certain period of time. Let us see why and how we need to remove these retired functionalities and related components. Why we need to Remove retired functionalities 1. Better Salesforce Governor Limits Like you know, Salesforce is having many limits with respect to the number of fields, the number of objects, code storage, validation rules, formula fields, etc. per Org. When we remove/delete unwanted components from an Org, it gives us additional space for new functionalities 2. Improve Performance There might be associated back end logic which is still getting executed on a record save, even if that feature is not in use. It will consume execution time, SOQL/DML limits of your current transaction. So removing this logic will help with better transaction performance 3. Avoid Unexpected Exceptions Obsolete backend functionalities can cause unexpected tran