Skip to main content

Lightning Experience

Note: All credit goes to Salesforce, I am just a developer who enjoy playing trailhead and try to make note to myself.
Which one I should use?Lightning Experience or Salesforce Classic?
Lightning Experience might be right for some or all of your org if:
  • Your sales team does business-to-business sales using accounts, contacts, leads, opportunities, custom objects, and the other sales features supported in the new user interface.
  • You want to pilot the new user interface with a group of sales reps.
  • You’re looking to reboot your Salesforce implementation. This is a great opportunity to introduce new features because you’re doing change management anyway.
Salesforce Classic might be right for you if:
  • Your sales team makes regular use of features that aren’t yet available in Lightning Experience, such as quotes, forecasting, or territory management.
  • You primarily use customer service tools or other non-sales features.
  • You want a single experience for your sales and service teams.
Some of features that might not work in Lightning Experience :
  • Custom Java script button.It can be replaced by point and click tools, Process builder, Visual Workflow and code driven approaches.
  • Some of Appexchange.Check out on the Lightning Ready certificate to ensure the apps is working on Lightning Experience.
  • Custom tab because tab is replaced by collapsible navigation menu at the left side.
  • Visualforce and apex.It works but it requires revision.

Setup User for Lightning Experince:
  • By default, the “Lightning Experience User” permission is automatically enabled for all users with a standard Salesforce profile.
  • If we have Standard User that should not get access to Lightning Experience move it to Custom Profile.
  • If we have Custom Profile user that should access to Lightning Experience, create Permission Set that includes 'Lightning Experience User'.
  • All above not applicable for Group Edition because Custom Profiles are not available .We can’t remove the “Lightning Experience User” permission from org’s standard profiles, and custom profiles aren’t available. So it’s “all or nothing” if we want to turn on Lightning Experience in Group Edition—all our users will be enabled to use the new interface. But we can control who is immediately switched into the new interface and who remains in the classic interface until they’re ready to switch themselves.
Trail Head Link Lightning Experience Basics


Popular posts from this blog

Search Solution Basics

When is it a good time to create a customized search solution? You're developing an external knowledge base for user support. You're in the mood for a fun Friday night. The sales reps just started using the Sales Cloud in Lightning Experience. You want to put your company branding in the search bar. What differentiates SOSL from SOQL? Syntax SOSL searches the search index instead of the org database. SOSL searches more efficiently when you don't know in which object the data resides. All of the above. SOSL works with: REST only SOAP only REST, SOAP, and Apex SOQL only What does a search for a single object look like in SOSL? FIND {cloud} RETURNING Account FIND in ACCOUNT RETURNING "cloud" FIND "cloud" in ACCOUNT FIND (cloud) RIGHT NOW! What does a search for multiple objects look like in SOSL? FIND {sneakers} RETURNING ALL ARTICLES FIND {sneakers} in ALL OBJECTS FIND {sneakers} RETURNING Product2, Content

Process Builder is not fired when field update is called from Approval Process

Scenario In Final Approvals section ; in Approval Process we have field update to update Status field. In Process Builder , we have some action that need to be done when Status field is updated in Approval Process.However this process builder is not fired. Solution To handle this, in Field Update in Approval Process , check Re-evaluated Workflow Rules after Field Change as picture below. What happen if field updated from Approval Process. Workflow - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Process Builder - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Trigger - will fire if conditions are matched This is explained in article here  . Field Updates That Re-evaluate Workflow Rules If  Re-evaluate Workflow Rules After Field Change  is enabled for a field update action, Salesforce  re-evaluates all workflow rules on the object if the field update results in a change to the value of the fi

Tips and Tricks : Test class for Invocable method

Issue : I got 100% coverage in my sandbox but when run validation for deployment it returns 0% coverage It turn out that in my sandbox, I am depending on Process Builder to Invocable Apex class, as long I manipulate test data that fire Process Builder it will call Invocable class. This is not useful when deploying it to Production although it gets deployed together with Process Builder. The correct way is to direct call Invocable method inside test class itself. Example of class : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 global class MyCustomObject_StatusUpdate_Util { @InvocableMethod ( label = ' Update Quote Status ' ) public static void updateQuote ( Request [] requests ) { Set < Id > setOppId = new Set < Id >(); List < SBQQ__Quote__c > listQuoteToUpdate = new List < SBQQ__Quote__c >(); for ( Request request : requests ) {