-
Why future methods must be static in Salesforce?
Why future methods must be static in Salesforce?
-
2 Replies
-
Future methods can be accessed from any class and not depend on any class instance hence it is declared as Static.
-
Because Future methods can be accessed from any class and not depend on any class instance.
Log In to reply.
Popular Salesforce Blogs
Future of Salesforce: Top 6 Predictions
Salesforce is one of the top 10 software skills trending this year. It was the first software of its kind and one of the most…
Why Salesforce Nonprofit Partners Are Essential for Your Organization’s Success
Salesforce offers a wide range of tools for sales, marketing, customer service, and analytics in one integrated system. Nonprofits use this powerful and customizable platform…
Salesforce Telephony and VoIP Integration: A Beginner’s Guide
You’re likely using Salesforce’s CRM to manage your communications with leads and customers online—but not all communication occurs through digital methods. If your sales reps…
Popular Salesforce Videos
The Decorator Pattern in Salesforce | Design Patterns | Salesforce
It attempts to solve the issue where you need temporary fields for processing (typically in Visualforce/LWC/Aura) but does not need to add these fields to…
Salesforce Apex Trigger Best Practices | Learn Salesforce Series By Algoworks
In this video, the following points will be covered - 1. One Trigger Per Object 2. Logic-less Triggers 3. Context-Specific Handler Methods 4. Code Bulkification…
Experience the Most Flexible, Easiest, and Securest Way to Integrate Salesforce and Jira
Integrate standard and custom Salesforce objects with Jira to strengthen cross-functional collaboration and deliver a top-notch customer experience. Fast-Track Your Journey to Attaining Customer Centricity…
