In Apex there is a provision to send email through Apex class. So similarly is there any provision which enables to send a sms? To expand my question more, I have a situation where I want to send a sms to the user whenever he submits the application form giving him the application number and other information via sms.
There is nothing built into the platform for this - your best bet would be to integrate with an existing online provider.
SMS Global have several exposed APIs, including one super simple POST based service, and you can also create your own POST service for responses if required. I've played with this one before and it took an hour or two to get a two-way setup operational.
Related
I am trying to trigger an apex class on every inbound text message received for messaging session in omni channel tab. But I am not able to find any object that can be used to attach a trigger on it. Have searched online as well, but in most of the guides they use third party services like twilio, Mercury etc. Can someone help me to implement this without any third-party service?
You should try agent work or pending service routing objects I think
I will work on a new project related to salesforce. Actually what we want to do is to have a salesforce API that contains our database and this API will accept connections from our clients. Once we establish the connection the user will have the access to our database too. Since I dont know anything about salesforce right now, I just wanted to ask you if you have some ideas on how to do that ? Is there any existing API doing that ? or We need to implement our new API for salesforce ?
Salesforce provides several APIs out of the box that can be used to access the data stored in your Organization.
Have a look at the REST API, Enterprise API and the Partner API. See Which API Should I Use?.
If none of those suit your needs you can use Apex to create your own REST or SOAP based services.
I am developing a Silverlight application that is supposed to send an email to a particular SharePoint user. I need two things:
I need to get the email address associated with the SharePoint user
BUT MUCH MORE IMPORTANTLY, I need to be able to send the actual email.
Since there is no System.Net.Mail class for Silverlight, it appears that I am condemned to create my own web service that is going to be in charge of sending emails. I am trying to avoid this, and I was wondering if there is a way to send an email to the SharePoint user using SharePoint's Silverlight Client Object Model? Thanks for clarification!
You could have a webpage that the user hits (possibly silently) rather than a web service, but at some point you're going to need to send a request that gets you to the server because this isn't an operation that can be done via the client.
I have developed a dating website built on top of the Google App Engine, to which I would like to add instant messaging, and possibly/probably audio and video conferencing.
Given that the users on the website do not want to share their personal details or real contact information, I am handling all of the login information and sessions without assuming that the clients have (or even want) a google account ID or any other login that is associated with their real identity.
I would like to hear suggestions on how I could go about adding instant messaging to my website given that I cannot just directly access Google Talk or some other existing service.
Would it make sense to use XMPP for this, and if so will Google Talk or any other XMPP service provider allow me to register new user accounts without manual intervention (ie. after a user is registered on my site, automatically register them with the XMPP provider)? Or, if not, perhaps I can use a single google ID with Google Talk with a different resource identifier for each user (me#google.com/user1, me#google.com/user2, etc...), and send messages between the different resources? Could this work, and/or would having thousands of simultaneous connections to a single account get me banned from Google Talk?
Perhaps some kind of AJAX based solution might make more sense given the fact that users are already registered on my website, but are not registered for an XMPP service?
Any suggestions about how I might approach this problem would be greatly appreciated.
Kind Regards
-Alexander
Text chat is the easier problem. You can do either with or without XMPP. Without XMPP, you'll be building a Facebook chat type client on your pages that sends messages from each user to the app, and the app then shows then on the recipient's screen.(The client can be polling, or use comet when it comes out). Check out olark to see how this works.
Once you build code to use the app as a switchboard that routes the correct message to the correct person (anonymously, maybe), you can port this easily to XMPP if you require. Both parties add you.dating.site#appspotchat.com to their buddy lists, and you send all messages from girl#site.com to guy#site.com and vice-versa. (assuming a heterogeneous site.)
Audio and video, I have no clue how to do without sharing details between the parties :-/
I have googled a bit for how I should handle security in a web service application when the application is basically the data repository for a Silverlight application, but have gotten inconclusive results.
The Silverlight application is not supposed to have its own user authentication, since it will be reachable only through a web application that the user have already authenticated to get into.
As such, I was thinking I could simply add a parameter to the SL application that is a cookie-type value, with a certain lifetime, linked to the user in the database. The SL application would then have to pass this value alongside other parameters to the web services. Since the web service is hopefully going to be a generic web service endpoint, few methods, adding an extra parameter at this level will not be a problem.
But, am I supposed to roll this system on my own? It sounds to me as this isn't exactly new features that nobody has considered before, so what are my options?
First of all use SSL for the service. Otherwise users will be able to capture all the parameters passed to the service. It's still possible to see it in case of https but it will be a little bit more difficult.
Also, consider using Message Inspector for adding custom headers to the messages which you will validate on the server. This way you will not need to add extra parameters.