Timeline for What's the best practice for providing this functionality?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 29, 2015 at 21:12 | comment | added | Charles Koppelman | Can you make the title here more informative? | |
| Jun 29, 2015 at 20:47 | answer | added | sfdcfox♦ | timeline score: 0 | |
| Jun 29, 2015 at 19:29 | comment | added | Mark Swanson | Yeah, basically I want to make it easy for the user to be able to use my app with salesforce. The only interaction is creating a new case. Don't need to read them or anything else. I thought just using the API would be simple for people, but the setup process is very complex for an average user. I'll look into packages more and see if that's what I need. Thanks guys. | |
| Jun 29, 2015 at 19:26 | comment | added | crmprogdev | Ahh, my apologies. I misunderstood your question. As Mark just posted, this is exactly what Dev Orgs are for. I thought you were asking how to replicate this type of set-up (via other Dev Orgs) to production orgs. Yes, a Dev Org is what you'd use to create a Managed Package and would be the way to distribute it to others. | |
| Jun 29, 2015 at 19:24 | comment | added | Mark Pond | So, you want to create an app that the paying Salesforce subscriber can install in their own org... this is exactly what the packaging (managed/unmanaged; paid/free) process is designed to deliver. | |
| Jun 29, 2015 at 19:18 | comment | added | Mark Swanson | I'm just using the dev org to create the code that'll be running on the (paid) instance. Is there a better way to do this? I was under the impression that using a dev org was how you were supposed to develop your application and then move to a real instance after it's created. To stay up and up with the ToS do I need to turn this into a package of some kind? | |
| Jun 29, 2015 at 19:06 | review | First posts | |||
| Jun 29, 2015 at 20:36 | |||||
| Jun 29, 2015 at 19:01 | history | asked | Mark Swanson | CC BY-SA 3.0 |