Salesforce has changed the behaviour of the Type.forName Method. Using an invalid namespace while calling the Type.forName() method now returns null. Previously, Apex allowed you to specify an invalid namespace such as Type.forName('InvalidNamespace', 'OuterClass.InnerClass') or use an outer class as a namespace such as Type.forName('OuterClass', 'InnerClass') with indeterminate results.
Business Impact
Decreased operational efficiency, increased potential for human error, delayed time-to-market, and decreased employee satisfaction.
Is your Salesforce solution affected by Breaking change in Type.forName methods?
Clayton detects anti-patterns and offers automated fix advice to kickstart your Well-Architected journey.