Apex Code Development You need to sign in to do that
Don't have an account?
jj-198 Visual Force Pages Vs API
Hi,
We are trying to put together a join registration form for our business that will have the information for the customer stored in Salesforce. The process the customer goes through is quite extensive and 9 times out of 10 would need to log into the registration form at a later date to complete it.
We are looking at implementing this in one of two ways, the first is to do this in a Force.com site that would load the customer details and save everything in an account/opportunity object, the downside we see with this is the restrictions with the design side of it. The alternative is to write the application in ASP.NET and save/load the details through the Salesforce API, concerned about the time it takes to save through the API. In the past we have developed in both so this is not an issue.
What are peoples thoughts? Which is the better more robust solution a Force.com site or writing the Salesforce API?
Thank you in advance for your advice,
-Jason
I would go with a Force.com site. That way your encapsulating your solution entirely in Salesforce.
Anytime you have to integrate through the API you are losing some of the benefits of Salesforce as a cloud platform and adding some complexity to your architecture. By that I mean you are talking about maintaining a seperate infrastructure and codebase which you would have to somehow manage. Of course the flipside of that is you get more control over your application and how its built out.
I have seen some really cool Force.com sites though, so I'm not sure how limited you would actually be. Although sounds like your form is pretty heavy so who knows?
Good luck.