Trigger Conext

Custom Controller & Controller Extension

A custom controller is an Apex class that implements all of the logic for a page without leveraging a standard controller. Use custom controllers when you want your Visualforce page to run entirely in system mode, which does not enforce the permissions and field-level security of the current user.

A controller extension is an Apex class that extends the functionality of a standard or custom controller. Use controller extensions when:
You want to leverage the built-in functionality of a standard controller but override one or more actions, such as edit, view, save, or delete.
You want to add new actions.
You want to build a Visualforce page that respects user permissions. Although a controller extension class executes in system mode, if a controller extension extends a standard controller, the logic from the standard controller does not execute in system mode. Instead, it **executes in user mode
**, in which permissions, field-level security, and sharing rules of the current user apply.

Custom Exception:

To create your custom exception class, extend the built-in Exception class and make sure your class name ends with the word Exception.

Success message

For Create a Record, Update a Record, and Log a Call action types, you can create a custom message that displays when the action executes successfully.

success message

Interface

Interface methods have no access modifiers. They are always global. ... This is the default, and means that the method or variable is accessible only within the Apex class in which it is defined. If you do not specify an access modifier, the method or variable is private .

StandardController

You can instantiate a StandardController in the following way:
ApexPages.StandardController sc = new ApexPages.StandardController(sObject);

StandardController Methods

The following are methods for StandardController. All are instance methods.

• addFields(fieldNames)
  When a Visualforce page is loaded, the fields accessible to the page are based on the fields referenced in the Visualforce mark up. This method adds a reference to each field specified in fieldNames so that the controller can explicitly access those fields as well.
• cancel()
  Returns the PageReference of the cancel page.
• delete()
  Deletes record and returns the PageReference of the delete page.
• edit()
  Returns the PageReference of the standard edit page.
• getId()
  Returns the ID of the record that is currently in context, based on the value of the id query string parameter in the Visualforce page URL.
• getRecord()
  Returns the record that is currently in context, based on the value of the id query string parameter in the Visualforce page URL.
• reset()
  Forces the controller to reacquire access to newly referenced fields. Any changes made to the record prior to this method call are discarded.
• save()
  Saves changes and returns the updated PageReference.
• view()
  Returns the PageReference object of the standard detail page.

Overriding Buttons, Links, and Tabs with Visualforce

You can override the behavior of standard buttons—like New, View, or Edit—in Salesforce Classic, Lightning Experience, and mobile independently. You can also override the tab home page that displays when a user clicks a standard, custom, or external object tab.

To override a standard button or a tab home page:

1. Click Edit next to the button or tab home page you want to override.
2. Pick Visualforce page as an override type.
   Select the Visualforce page you want to run when users click the button or tab.
3. When overriding buttons with a Visualforce page, you must use the standard controller for the object on which the button appears.
   • Use a controller extension when you need to add extra functionality to Visualforce page that you are using as an override.
4. Save

Setter Method

Setter methods pass user-specified values from page markup to a controller. Any setter methods in a controller are automatically executed before any action methods.
While a getter method is always required to access values from a controller, it’s not always necessary to include a setter method to pass values into a controller. If a Visualforce component is bound to an sObject that is stored in a controller, the sObject's fields are automatically set if changed by the user, as long as the sObject is saved or updated by a corresponding action method.