This presentation is used in the first tutorial in "Simplifying the Callouts in Salesforce" tutorial series. In this tutorial, we're going to install HTTPCalloutFramework and will perform a callout to static API.
GitHub:- https://github.com/rahulmalhotra/HTTPCalloutFramework
Blog:- https://www.sfdcstop.com/2020/04/introduction-and-installation-of.html
YouTube:- https://youtu.be/ReElUyxCnHE
2. Current Scenario
1. There are a lot of trigger frameworks for simplifying creation of triggers but there are
very less frameworks for simplifying the callouts in Salesforce
2. Performing a callout from salesforce involves a lot of work
3. Creation of test classes is a difficult task as we need to create a mock test class for
each API
4. If the endpoint or any of the metadata changes. As developers, we need to dive back in
the code in order to update the current implementation
5. We need a generic implementation/framework that can be used for different callouts.
3. Introducing HTTPCalloutFramework
● HTTPCalloutFramework is a lightweight framework for simplifying Apex HTTP Callouts
in salesforce.
● It’s Configurable :- All the data related to callout is stored in a custom metadata
named HTTPCalloutConfiguration so that you don’t have to make changes in the
code again and again
● Generic Mock and Multi-Mock Classes :- It consist of a generic mock class named
HTTPCalloutServiceMock and a multi-mock class named
HTTPCalloutServiceMultiMock in case you have multiple callouts in single transaction
● Supports both Synchronous and Asynchronous Callouts
4. It’s Free and Open Source
● https://github.com/rahulmalhotra/HTTPCalloutFramework
● https://www.sfdcstop.com/2019/12/httpcalloutframework-light-weight.html
