Bill,
My apologies for the long response periodicity. The URL SControl works but only kinda. Unless I misunderstand, you're proposing that we push everything we want to the webservice via a http get. I guess this would work if I pushed just the pertinent info like the Id of the table to the webservice but then there's also the problem of the response. How can I get SFDC to respond to that? It seems like your solution might be better suited to having an aspx handle the get request and maybe in the URL S Control, open a separate window to allow the human to handle the response from the webservice integration.
Thanks for the response as it got me researching workflows and outbound messaging in SFDC and that's how we ended up implementing the integration. We wrote a Outbound Messaging handler and queued the OB msgs to the webservice as appropriate.
I used this site for reference.
http://wiki.apexdevnet.com
Main Topics
Browse All Topics
by: Bill-HansonPosted on 2008-05-06 at 12:51:56ID: 21510423
Well, you can't use AJAX due to cross-server security issues (unless you disable security, which is a major pain and does not always work). :(
What we have done in the past is to create a simple URL s-control that points to a web service and passes arguments (session id, user id, etc...) via url parameters.
Another alternative is to host a page on your own server, then display the page in an iframe in an s-control. That way, your page can use your web service without dealing with the AJAX security issues.