Apex Code Development You need to sign in to do that
Don't have an account?
Keith987 Do "Force.com Embedded Edition" licenses allow Apex source code to be deployed/executed?
Threads like Package install fail: missing feature apex class discuss editions that do and do not allow Apex source code to run. (Apex code in a managed package is treated somewhat differently.)
Can anyone point me to a data sheet that describes this capability for "Force.com Embedded Edition" licenses?
Thanks,
Keith
Apex code outside of the package is technically supported for OEM licenses, provided that it is deployed and tested as in normal Force.com developments, i.e. if you write apex code in a trial org (this is how normally you would deliver an OEM app for your customers to try it) it will need to be redeployed as per Apex documentation:
"Apex triggers are available in the Trial Edition of Salesforce; however, they are disabled when you convert to any other edition. If your newly-signed-up organization includes Apex, you must deploy your code to your organization using one of the deployment methods." - http://www.salesforce.com/us/developer/docs/apexcode/index_Left.htm#StartTopic=Content/apex_intro_get_dev_account.htm?SearchType=Stem .
Any other edition mentioned above includes the embedded edition.
All Answers
Hi Keith,
please find the Force.com OEM license data sheet here:
http://www.salesforce.com/assets/pdf/datasheets/DS_Forcedotcom-OEM.pdf .
OEM definitely supports Apex code because this is what ISVs use to create custom apps on Force.com .
OEM edition apps are distributed in managed packages and can leverage Trialforce to give a trial experience to the ISV's customers.
Find more info in : http://sites.force.com/partners/PP2Page?p=P_ISVPartnerProgram or in the Partner Portal you can access if you are a registered Partner.
It is the unmanaged Apex source code I am asking about i.e. code that is providing customization of the code that is in the managed package.
Apex code outside of the package is technically supported for OEM licenses, provided that it is deployed and tested as in normal Force.com developments, i.e. if you write apex code in a trial org (this is how normally you would deliver an OEM app for your customers to try it) it will need to be redeployed as per Apex documentation:
"Apex triggers are available in the Trial Edition of Salesforce; however, they are disabled when you convert to any other edition. If your newly-signed-up organization includes Apex, you must deploy your code to your organization using one of the deployment methods." - http://www.salesforce.com/us/developer/docs/apexcode/index_Left.htm#StartTopic=Content/apex_intro_get_dev_account.htm?SearchType=Stem .
Any other edition mentioned above includes the embedded edition.
I can confirm that the Apex (unmanaged) source code does work using the "Force.com Embedded Edition".
The uncertainty was generated by our lack of understanding that the conversion from trial licenses to the "Force.com Embedded Edition" licenses would inactivate the Apex source code and turn off the code editing features. This left the application broken for our customer (who was testing at the time).
The lesson learned is to plan for some downtime when the licenses are applied while the code is re-deployed.