Friday, December 30, 2016

ISV App Strategy

App Type

  1. ISVforce App
    • app that extend Sales or Service Cloud
    • can be sell only to existing Salesforce customer.
    • if we use some Salesforce licence dependencies feature, need to make sure the user also have licence from Salesforce.
    • our customer have to purchase the license from Salesforce
    • Licence type mostly Sales and Service cloud
  2. Force.com Embedded app (OEM Embedded app)
    • app that does not rely on Sales cloud or Service cloud functionality.
    • can be sell to existing customer or customer who does not use Salesforce at all.
    • have access to App Cloud platform.Although they have access to certain Sales and Service cloud object such Leads,Opportunities they can't surface those to customer.
    • by contract,Salesforce does not give permission to rebuild Sales or Service Cloud functionality within OEM Embedded app.
    • the licence is embedded in application for new customer and existing customer but existing customer can choose to assign their ISV app licence rather than using embedded user licence.
    • Licence type Force.com,Customer Community (optional) and Customer Community Plus(optional)
Both ISV application licences provided by partner.

Why would you want to build an ISVforce app instead of an OEM Embedded app?
The app displays data in Opportunity and Lead objects.


Why would you want to build an OEM Embedded app instead of an ISVforce app?
Your target customers may not already have Salesforce.


What kind of Salesforce licenses must be included in a OEM Embedded app?
Force.com


In your special partner DE org, you’ve created an app that you are ready to distribute. Displaying data from which object in your solution would prevent you from being able to use the OEM Embedded app type?
Case . We still can use Account and Contact in OEM Embedded app type.


Trailhead :Select an App Type

No comments:

Post a Comment