Skip to main content

Determine the Salesforce Edition for Your App

How does Enterprise Edition differ from Professional Edition?

  • Enterprise Edition has features that aren't available in Professional Edition
  • Professional Edition is only sold to Accountants, Dentists, and Lawyers
  • Enterprise Edition supports more users than Professional Edition
  • Professional Edition has higher limits than Enterprise Edition

Which list correctly orders editions from smallest to largest?

  • Enterprise Edition, Professional Edition, Group Edition, Performance Edition
  • Professional Edition, Group Edition, Enterprise Edition, Performance Edition
  • Group Edition, Professional Edition, Enterprise Edition, Performance Edition
  • Professional Edition, Group Edition, Performance Edition, Enterprise Edition

You’re building an ISVforce app that reuses Account, Contact, Lead, and Opportunity objects to vet vendors who resell products for your customers. You use Record Types to ensure that the fields you add don’t interfere with the customers existing use of those objects. What's the lowest edition that you can target?

  • Group Edition
  • Enterprise Edition
  • Performance Edition
  • Professional Edition

For an ISVforce app, what determines the features you should use in your solution?

  • The type of user licenses you're embedding in your application
  • The size of the customer you're targeting and the industry they are from
  • The complexity of your application and the amount of resources it uses
  • The customer’s edition, user licenses, and feature and permission set licenses
  • You want your customers to buy user licenses directly from Salesforce

When should you decide which editions your app supports?

  • After you develop your app, but before you sell it to customers
  • Before you design your app and before you build your app
  • After you’ve designed your app, but before you begin building it
  • Before you determine your target audience and before you design your app


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 ) {