Consts

The Constants Framework provides a structured approach for managing constants in the Apex.

Example

Account acc = new Account(
    Name = 'My Account',
    Type = Consts.ACCOUNT.TYPE.PROSPECT,
    Rating = Consts.ACCOUNT.RATING.HOT
);

System.debug(Consts.ACCOUNT.TYPE.PROSPECT); //'Prospect'
System.debug(Consts.ACCOUNT.RATING.HOT); //'Hit'

System.debug(Consts.CONTACT.API_NAME); //'Contact'
System.debug(Consts.CONTACT.LEAD_SOURCE.WEB); //'Web'

System.debug(Consts.OPPORTUNITY.TYPE.EXISTING_CUSTOMER_DOWNGRADE); //'Existing Customer - Downgrade'

How it works?

The framework employs the concept of singletons to create concrete classes. Each class is initialized once during the transaction, reducing heap size usage.

Getters and setters are used to lazily initialize the classes. For example, accessing Consts.Account.TYPE.PROSPECT will only create an instance of the AccountConsts class without creating ContactConsts.

The code architecture follows the Open/Closed and Single Responsibility Principle principles. This design ensures the code is easily extensible, and each class is responsible for a specific set of constants.

How to use it?

Create a concrete consts class

• Define an INSTANCE variable to hold the class instance (singleton).
• Create inner classes to organize the constant values.

public class ContactConsts {
    public static final ContactConsts INSTANCE = new ContactConsts();

    public final String API_NAME = Contact.sObjectType.getDescribe().getName();

    public final Status STATUS = new Status();

    public class Status {
        public final String IN_APPROVAL_PROCESS = 'In Approval Process';
        public final String ACTIVATED = 'Activated';
        public final String DRAFT = 'Draft';
    }
}

Add a concrete consts class to Consts

public class Consts {

    public static final ContactConsts CONTACT {
        get {
            return ContactConsts.INSTANCE;
        }
    }
}