Visualforce page tag – apex:commandButton

apex:commandButton

apex:commandButton, this is used to define a button that is rendered as an  HTML input element with the type attribute set to submit, reset, or image, depending upon the commandButton tag’s specified value. The button executes an action defined by a controller, and then either refreshes the current page, or navigates to a different page based on the pageReference variable that is returned by the action. And apex:commandButton must always be a child of apex:form tag. 




Example:

<apex:page standardController=”Account”>

    <apex:form >

        <apex:pageBlock title=”Account Details”>           

            <apex:pageBlockSection title=”My Content Section” columns=”2″>

                <apex:inputField value=”{!account.name}”/>

                <apex:inputField value=”{!account.AccountNumber}”/>

                <apex:inputField value=”{!account.type}”/>

                <apex:inputField value=”{!account.accountNumber}”/>

            </apex:pageBlockSection>                       

            <apex:pageBlockButtons >

                <apex:commandButton action=”{!save}” value=”Save”/>

            </apex:pageBlockButtons>

        </apex:pageBlock>

    </apex:form>

</apex:page>

apex:commandButton

attributes:

accesskey, action, alt, dir, disabled, id, image, immediate, lang, onblur, onclick, oncomplete, ondblclick, onfocus, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rendered, reRender, status, style, styleClass, tabindex, timeout, title, value.

To know more about commandButton refer this URL, https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_compref_commandButton.htm




Visualforce page tag – apex:pageBlockButtons

apex:pageBlockButtons

apex:pageBlockButtons, this tag is used to define a set of buttons that are styled like standard Salesforce buttons. This tag must be a child component of on apex:pageBlock tag.




Example:

<apex:page standardController=”Account”>

    <apex:form >

        <apex:pageBlock title=”Account Details”>           

            <apex:pageBlockSection title=”My Content Section” columns=”2″>

                <apex:inputField value=”{!account.name}”/>

                <apex:inputField value=”{!account.AccountNumber}”/>

                <apex:inputField value=”{!account.type}”/>

                <apex:inputField value=”{!account.accountNumber}”/>

            </apex:pageBlockSection>                       

            <apex:pageBlockButtons >

                <apex:commandButton action=”{!save}” value=”Save”/>

            </apex:pageBlockButtons>

        </apex:pageBlock>

    </apex:form>

</apex:page>  

Result of the above visualforce page.

apex:pageBlockButtons

apex:pageBlockButtons attributes:

dir, id, lang, location, onclick, ondblclick, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rendered, style, styleClass, title.

To know more about apex:pageBlockButtons, refer this URL https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_compref_pageBlockButtons.htm




visualforce page tag – apex:pageBlockSectionItem

apex:pageBlockSectionItem

apex:pageBlockSectionItem is used to define a single piece of data in an page block section that takes up one column in a row. Page block section item tag can include up to two child components. If no content is specified, the column is rendered as an empty space.




Example:

<apex:page standardController=”Account”>

    <apex:form >

        <apex:pageBlock title=”Update Accounts”>           

            <apex:pageBlockSection title=”Account Details” columns=”2″>

                <apex:pageBlockSectionItem >

                    <apex:outputLabel value=”Account Name”/>

                    <apex:inputText value=”{!account.name}”/>

                </apex:pageBlockSectionItem> 

                <apex:pageBlockSectionItem >

                    <apex:outputLabel value=”Account Number” />

                    <apex:inputText value=”{!account.AccountNumber}” />

                </apex:pageBlockSectionItem> 

                <apex:pageBlockSectionItem >

                    <apex:outputLabel value=”Account Type” />

                    <apex:inputText value=”{!account.type}” />

                </apex:pageBlockSectionItem> 

                <apex:pageBlockSectionItem >

                    <apex:outputLabel value=”Account Number”/>

                    <apex:inputText value=”{!account.accountNumber}”/>

                </apex:pageBlockSectionItem>

            </apex:pageBlockSection>

            <apex:pageBlockButtons >

                <apex:commandButton action=”{!save}” value=”Save”/>

            </apex:pageBlockButtons>

        </apex:pageBlock>

    </apex:form>

</apex:page>

Result of the above visualforce page code:

apex:pageBlockSectionItem

pageBlockSectionItem attributes:

dataStyle, dataStyleClass, dataTitle, dir, helpText, id, labelStyle, labelStyleClass, labelTitle, lang, onDataclick, onDatadblclick, onDatakeydown, onDatakeypress, onDatakeyup, onDatamousedown, onDatamousemove, onDatamouseout, onDatamouseover, onDatamouseup, onLabelclick, onLabeldblclick, onLabelkeydown, onLabelkeypress, onLabelkeyup,onLabelmousedown, onLabelmousemove, onLabelmouseout, onLabelmouseover, onLabelmouseup, rendered.

To know more about apex:pageBlockSectionItem refer this URL https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_compref_pageBlockSectionItem.htm




Visualforce page Tag – apex:pageBlockSection

apex:pageBlockSection

apex:pageBlockSection represents a section of data with in an apex pageBlock . It is like a section in a standard Salesforce page layout. This component consists of one or more columns, each of which spans two cells, one is for a field label and the other one is for its value.




Example:

<apex:page standardController=”Account”>

    <apex:form >

        <apex:pageBlock title=”Account Details”>           

            <apex:pageBlockSection title=”My Content Section” columns=”2″>

                <apex:inputField value=”{!account.name}”/>

                <apex:inputField value=”{!account.AccountNumber}”/>

                <apex:inputField value=”{!account.type}”/>

                <apex:inputField value=”{!account.accountNumber}”/>

            </apex:pageBlockSection>                       

            <apex:pageBlockButtons >

                <apex:commandButton action=”{!save}” value=”Save”/>

            </apex:pageBlockButtons>

        </apex:pageBlock>

    </apex:form>

</apex:page>

Here is the result of above page code:

apex:pageBlockSection

apex:pageBlock attributes:

PageBlockSection attributes: collapsible, columns, dir, id, lang, onclick, ondblclick, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rendered, showHeader, title.

Facets: body, header

Refer this URL for more details https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_compref_pageBlockSection.htm




Visualforce Tag – apex:pageBlock

apex:pageBlock

apex:pageblock represents an area of a page that uses styling similar to looks and feel of a Salesforce details page without any default content.




Example:

<apex:page standardController=”Account”>

    <apex:form >

        <apex:pageBlock title=”Account Details”>           

            <apex:pageBlockSection title=”My Content Section” columns=”2″>

                <apex:inputField value=”{!account.name}”/>

                <apex:inputField value=”{!account.AccountNumber}”/>

                <apex:inputField value=”{!account.type}”/>

                <apex:inputField value=”{!account.accountNumber}”/>

            </apex:pageBlockSection>                       

            <apex:pageBlockButtons >

                <apex:commandButton action=”{!save}” value=”Save”/>

            </apex:pageBlockButtons>

        </apex:pageBlock>

    </apex:form>

</apex:page>

here is the output of above page.

apex:PageBlock

apex:pageBlock attributes:

dir, helpTitle, helpUrl, id, lang, mode, onclick, ondblclick, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, rendered, tabStyle, title. 

Facets: footer, header

Refer this URL for more details about https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_compref_pageBlock.htm




Visualforce page tag – apex:form

apex:form

apex:form, it is a section of visualforce page that allows users to enter input and then submit it with command button or link.




It is a best practice to use only one apex:form tag in a page or custom component.  

Example:

<apex:page standardController=”Account”>   

    <h1>Update Account Details</h1>   

    <apex:form>   

        <apex:inputField value=”{! Account.Name }”/>       

        <apex:commandButton action=”{! save }” value=”Save” />   

    </apex:form>   

</apex:page> 

apex:form attributes:

accept, acceptcharset, dir, enctype, forceSSL, id, lang, onClick, ondblclick, onkeydown, onkeypress,  onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, onreset, onsubmit, prependId, rendered, style, styleClass, target, title.

Refer this for more details https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_compref_form.htm




Visulforce page tag – apex:page

apex:page

This tag represents a single visualforce page. Any visualforce page should be wrapped inside a single page component tag. 




<apex:page>

//Your visualforce page content.

</apex:page> 

Eample:

<apex:page>

<H1>Welcome to Salesforce tutorial<H1>

<p>This tutorial is useful for to understand Salesforce basics</p>

</apex:page>

apex:page attributes:

Action, apiversion, applyBodyTag, applyHtmlTag, cache, contentType, controller, deferLastCommandUntiReady,  doctype, expires, extensions, id, label, language, lightningStylesheets, manifest, name, pageStyle, readOnly, recordSetName, recordSetVar, renderAs, rendered, setup, showChat, showHeader, showQuickActionVfHeader, sidebar, standardController, standardStylesheets, tabStyle, title, wizard.

Refer this for more details:https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_compref_page.htm





Lead Conversion – New efficient Lead conversion window

Lead Conversion : New efficient Lead conversion window

How the new Lead conversion process save time?



The new lead conversion process in lightning experience matched leads with contacts and accounts already in Salesforce. And Sales Reps can create a new opportunity or can select one already in the works.

We can quickly perform below action using new Lead Conversion window:

  • Create account, contact and opportunity from the lead data with a click.
  • We can choose record types while creating account, contact and opportunity.
  • View the details of matched records.
  • Search for the more records to relate the new lead.
  • Update the values provided from the lead for each new record.
  • Relate the lead to existing account, contact and opportunity records matched to the lead using your duplicate management rules.
  • Create fallow up tasks.
Lead Conversion Process New Lightning
Lead Conversion Process New Lightning





Differences between CRM, PRM

What are the differences between CRM, PRM




CRM

  • CRM stands for Customer Relationship Management.
  • CRM application are built for direct sales.
  • CRM applications help your internal teams manage interactions with potential and current customers.
  • CRM applications compile data from every department, store it on a centralized customer record, and drive customer retention and future sales.

PRM

  • PRM stands for Partner Relationship Management.
  • PRM applications are built for indirect Sales.
  • It is about maintaining healthy relationship with the partners and ensuring that the trust between company and the partner remains intact.
  • Partner relationship management solutions only focuses on the product and its Sales to ensure long term profits.





Important productivity features of Salesforce Inbox

What are the important productivity features of Salesforce Inbox?




Salesforce Inbox Importance: Sales Reps most often interact with prospects over email communication. And, most of the companies use CRM to track customers and deals information. So, reps usually spend more time on the CRM tool to enter data. If reps have capability to sync data from emails to CRM, they can focus on closing deals instead of entering data manually.

Salesforce CRM proving below features to save reps time to enter data in the tool.

  • Quick create of Salesforce inbox allows reps to add opportunities & contacts to Salesforce without leaving email Inbox.
  • Salesforce Einstein Activity Capture allows Sync emails and calendar events to Salesforce and associate them with the right records automatically.
  • By using Mobile and desktop apps reps can sell smarter anywhere with the full power of Salesforce in outlook, Gmail, and reps mobile email box.

It allows reps to insert customer meeting based on availability and track when email is opened.