Introduction of Visualforce in Salesforce
About Visualforce locally on the Lightning stage. The Visualforce structure incorporates a tag-based markup language, like HTML, and a lot of server-side "standard controllers" that make essential database activities, for example, questions and spares, easy to perform.
In the Visualforce markup language, each Visualforce tag compares to a coarse or fine-grained user interface segment, for example, an area of a page, a related rundown, or a field. The conduct of Visualforce parts can either be constrained by a similar rationale that is utilized in standard Salesforce pages, or engineers can connect their own rationale with a controller class written in Apex.
Visualforce Page Designers can utilize Visualforce to make a Visualforce page definition. A page definition comprises of two essential components:
Don’t forget to check out: Salesforce Visualforce Vs Salesforce Lightning Component
Visualforce markup
Visualforce Markup Visualforce markup comprises of Visualforce labels, HTML, JavaScript, or some other Web-empowered code inserted inside a solitary <apex:page> tag. The markup characterizes the UI parts that ought to be remembered for the page and the manner in which they ought to show up.
Visualforce Controllers A Visualforce controller is a lot of guidelines that indicate what happens when a client cooperates with the parts determined in related Visualforce markup, for example, when a client clicks a catch or connection. Controllers additionally give access to the information that ought to be shown on a page and can change part conduct.
A designer can either utilize a standard controller gave by the Lightning stage, or include custom controller rationale with a class written in Apex:
A standard controller comprises of similar usefulness and rationale that is utilized for a standard Salesforce page. For instance, in the event that you utilize the standard Accounts controller, clicking a Save button in a Visualforce page brings about a similar conduct as clicking Save on a standard Account alter the page.
On the off chance that you utilize a standard controller on a page and the client doesn't approach the item, the page will show a lacking benefits blunder message. You can maintain a strategic distance from this by checking the client's openness for an item and showing segments suitably.
A standard rundown controller empowers you to make Visualforce pages that can show or follow up on a lot of records. Instances of existing Salesforce pages that work with a lot of records incorporate rundown pages, related records, and mass activity pages.
A custom controller is a class written in Apex that actualizes the entirety of a page's rationale, without utilizing a standard controller. On the off chance that you utilize a custom controller, you can characterize new route components or practices, yet you should likewise reimplement any usefulness that was at that point given in a standard controller.
Like other Apex classes, custom controllers execute completely in framework mode, in which the and field-level authorizations of the present client are disregarded. You can determine whether a client can execute strategies in a custom controller dependent on the client's profile.
A controller augmentation is a class written in Apex that adds to or supersedes conduct in a standard or custom controller. Augmentations permit you to use the usefulness of another controller while including your own custom rationale.
Since standard controllers execute in client mode, in which the authorizations, field-level security, and sharing principles of the present client are upheld, expanding a standard controller permits you to construct a Visualforce page that regards client consents. In spite of the fact that the augmentation class executes in framework mode, the standard controller executes in client mode. Likewise, with custom controllers, you can determine whether a client can execute techniques in a controller expansion dependent on the client's profile.
Uses of Visualforce Pages:
Engineers can utilize Visualforce pages in:
- Abrogate standard catches, for example, the New catch for accounts, or the Edit button for contacts
- Abrogate tab diagram pages, for example, the Accounts tab landing page
- Characterize custom tabs
- Install segments in detail page formats
- Make dashboard segments or custom assistance pages
- Redo, broaden, or incorporate the sidebars in the Salesforce support (custom comfort segments)
- Include route menu things and activities in the Salesforce portable application