Breaking change in Type.forName methods

Overview

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.

Resources

Frequent

Incidence

How common is this issue?
20%7%
arrow down12%
lower

Exposure

How long do organizations remain exposed before fixing the problem?
2 years2 months
arrow down93%
shorter
BenchmarkWith Clayton

Frameworks

EasyiconAutomatediconEfficiencyiconOperational Logicicon