[shariq]

Hi,

Basic Difference - 

Workflow is automated process that fired an action based on Evaluation criteria and rule criteria. We can access a workflow across the object. Trigger is a piece of code that executes before or after a record is inserted or updated.

Hope this helps.

[shariq]

Hi,

Master Detail is a required field and validation can set some rules that which master should be attached to detail.

This is one of the use I am thinking right now.

Hope this helps.

[shariq]

Hi,

Main reason - 

The emails fired from auto response rules are attached as Email Messages to respective Case or Lead objects which are useful for tracking purposes, whereas Workflows cannot be tracked.

Hope this helps.

[shariq]

Hi,

Auto-number fields can be external IDs. Salesforce.com might be the source of record without explicitly using salesforce.com ID values, which may be case insensitive depending on the other application, which can cause unwanted complications. Using an auto-number field avoids case-sensitive ID values that might otherwise confuse systems not designed to handle such ID values, like Excel (which is, by default, case sensitive).

Hope this helps.

[shariq]

Hi,

When dealing with Web to Lead, when you are setting up your Web to Lead form, you can set the value of the field 'Lead Source' to a specific value. (In fact, you can have this field be a hidden field so no one evens sees it.)

 

Then, you can set up a Lead Assignment Rule which says if the Lead Source field is equal to 'Web', then have the Lead go to the Lead-Open Queue.

Hope this helps.

[shariq]

Hi,

Could you explain more what yoou want to know and send me the requirement.

Thanks.

[shariq]

Hi,

Yes, there can be, just change the number or type of parameters as depend upon your logic.

Hope this helps.

[shariq]

Hi,

As after delete works when record is removed from database and addError works on that record(any custom validation) so when record is removed, there will be no use of addError functionality.

 

 

Hope this helps.

[shariq]

Hi,

There are two points -

• To renew governer limits of salesforce.
• To synchronize the run of batches and scheduler.

Hope this helps.

[shariq]

Hi,

SOAP defines a standard communication protocol (set of rules) specification for XML-based message exchange. SOAP uses different transport protocols, such as HTTP and SMTP.

Hope this helps.

[shariq]

Hi,

NOTE - When you configure the case page layout for your community, specify that some fields are required. Adding required fields to the layout ensures that customers don’t accidentally submit cases with empty fields.

Hope this helps.

[shariq]

Hi,

Case Queues management - Help you manage your support workload and differentiate cases based on support levels. With queues, you can ensure that cases are resolved quickly even if a specific user is on vacation. By creating queues for different support levels, such as Gold Service and Silver Service, cases are automatically prioritized. You can put cases in different queues, either manually or automatically via a case assignment rule as cases are generated from the Web or created manually. Make support agents members of case queues.

Hope this helps.

[shariq]

Hi,

Since Salesforce runs on multi-tenancy environment and in order to have same performance to the database,it has imposed some run time limits called governor limits. There are many types of Salesforce Governor limits like Pre transactionlimits, Force.com platfform apex limits, static apex limits and many otherlimits.

Hope this helps.

[shariq]

Hi,

Try this -

private Date setStringToDateFormat(String myDate) {
String[] myDateOnly = myDate.split(' ');
String[] strDate = myDateOnly[0].split('/');
Integer myIntDate = integer.valueOf(strDate[1]);
Integer myIntMonth = integer.valueOf(strDate[0]);
Integer myIntYear = integer.valueOf(strDate[2]);
Date d = Date.newInstance(myIntYear, myIntMonth, myIntDate);
return d;
}

Hope this helps.

[shariq]

Hi,

Things to remember for doing above -

Make different transaction for callout and DML.

Performing a DML operation on a record and a callout cannot be made in the same transaction.

Hope this helps.

[shariq]

Hi,

Try this -

<apex:pageBlock id="xxxpb1">

<apex:pageBlockSection>
                    
<apex:actionRegion >               

  <apex:inputField id="xxxif1" value="{!Object.picklistfieldapiname1}" required="true" >

     <apex:actionSupport event="onchange" rerender="xxxpb1" />
  </apex:inputField>

</apex:actionRegion>
                 
</apex:pageBlockSection>
               
<apex:pageBlockSection id="xxxpbs1" rendered="true">

 <apex:inputField id="xxxif2" value="{!Object.Fieldtobedisplayed1}" rendered="{!IF(Object.picklistfieldapiname1 ='picklist value 1' || lead.Buyer_Type__c ='picklist value 2' ,true,false)}"/>

</apex:pageBlockSection>

<apex:pageBlockSection id="xxxpbs2" rendered="true">

  <apex:inputField id="xxxif3" value="{!Object.Fieldtobedisplayed2}" rendered="{!IF(Object.picklistfieldapiname1 ='picklist value 3' || lead.Buyer_Type__c ='picklist value 4' ,true,false)}"/>  
                                                                     
</apex:pageBlockSection>

</apex:PageBlock>

In the above code block, fields are displayed on VF page only if the rendering criteria is met.

Hope this helps.

[shariq]

Hi,

Please go through the example.

Example:

global virtual class PropertyVisibility {
   // X is private for read and public for write
   public integer X { private get; set; }
   // Y can be globally read but only written within a class
   global integer Y { get; public set; }
   // Z can be read within the class but only subclasses can set it
   public integer Z { get; protected set; }
}

Hope this helps.

[shariq]

Hi,

The Lightning Experience Configuration Converter recreates your org’s JavaScript buttons as Lightning components, quick actions, or other solutions — all without touching your original buttons. Before committing to any changes, you can preview the new component code or declarative steps and verify that the alternatives work as expected.

This tool currently converts some (but not all) JavaScript buttons that implement “url-hacks.” (If you’re not familiar with the term, a “url-hack” is how the community refers to a URL that sets predefined values.) This is the most common use case for JavaScript buttons. The Configuration Converter recreates these buttons as either quick actions, Lightning component actions, or custom buttons or links, based on what the JavaScript code is doing. JavaScript buttons can have varying degrees of complexity. Currently, the tool supports simpler “url-hack” implementations.

Hope this helps.

[shariq]

Hi,

Developer org allows 10 single email messaging in single transaction, if you try to do it more then it will throw an above error.

Hope this helps.

[shariq]

Hi,

List Email Limitations

The following limitations apply to list emails.

• List emails can contain up to 32,000 characters.
• You can manually select up to 200 contacts or leads from a contact or lead list view.
• You can send up to the daily list email limit by entering the list view name in the Recipients field. Or, click Send List Email from a Contact list view, Lead list view, or Campaign record without selecting any individual records.
• List emails count against an org’s daily list email send limit, which is typically 5,000 emails per day. This limit doesn't include individual emails you send.

Hope this helps.

[shariq]

Hi,

Create a Custom Renderer
The framework’s rendering service takes in-memory component state and creates and manages the DOM elements owned by the component. If you want to modify DOM elements created by the framework for a component, you can modify the DOM elements in the component’s renderer. Otherwise, the framework will override your changes when the component is rerendered.
The DOM is the language-independent model for representing and interacting with objects in HTML and XML documents. The framework automatically renders your components so you don’t have to know anything more about rendering unless you need to customize the default rendering behavior for a component.

Base Component Rendering
The base component in the framework is aura:component. Every component extends this base component.

The renderer for aura:component is in componentRenderer.js. This renderer has base implementations for the four phases of the rendering and rerendering cycles:

render()
rerender()
afterRender()
unrender()
The framework calls these functions as part of the rendering and rerendering lifecycles and we will learn more about them soon. You can override the base rendering functions in a custom renderer.

Hope this helps.

[shariq]

Hi,

$Resource
The $Resource global value provider lets you reference images, style sheets, and JavaScript code you’ve uploaded in static resources.
Using $Resource lets you reference assets by name, without worrying about the gory details of URLs or file paths. You can use $Resource in Lightning components markup and within JavaScript controller and helper code.

<aura:component>
<!-- Stand-alone static resources -->

<!-- Asset from an archive static resource -->


</aura:component>

Hopes this helps.

[shariq]

Hi,

Custom Metadata Types (CustomObject)
Represents the metadata associated with a custom metadata type.

To create custom metadata types, you must have the “Author Apex” permission. Apex code can create, read, and update (but not delete) custom metadata records, as long as the metadata is subscriber-controlled and visible from within the code's namespace. You can edit records in memory but not upsert or delete them. Apex code can deploy custom metadata records, but not via a DML operation. Moreover, DML operations aren’t allowed on custom metadata in the Partner or Enterprise APIs. Customers who install a managed custom metadata type can’t add new custom fields to it. With unpackaged metadata, both developer-controlled and subscriber-controlled access behave the same: like subscriber-controlled access.

Hope this helps.

[shariq]

Hi,

Example - 

public static void dynamicUpsert(List<SObject> records)
{
Schema.SObjectType sObjectType = records.getSObjectType();
if (sObjectType != null)
{
String listType = 'List<' + sObjectType + '>';
List<SObject> castRecords = (List<SObject>)Type.forName(listType).newInstance();
castRecords.addAll(records);
upsert castRecords;
}
}

Hope this helps.

[shariq]

Hi,

This what I found online let me know if this is correct.

For example:
<lightning:recordEditForm recordId=""
                                          objectApiName="Case">
                     <lightning:inputField fieldName="Subject" />
                    <lightning:inputField fieldName="Type" />
                    <lightning:inputField fieldName="Case_Sub_Type__c" />
                   
                 </lightning:recordEditForm>

Hope this helps.