The docs appear clear as mud on this. I'm building a custom CRM and need a way to get the phone number (caller ID) of the current incoming call. The workstation has the Five9 application installed and the Desktop Toolkit. Now what do I do in the web browser to get that information? My idea was that I'd have a search form and one could click a button called "Search by Caller ID". The web browser would then connect somehow to Five9, get the current phone number of the current call, and send it back to the web server to show records that matched that phone number.
Related
I build an application that among other things send link (SMS) to users.
When user opens the link (asp.net page) she fills a form and send it to server.
In order to make the user submit the form once I need a unique identifier for her cellphone.
Any idea regarding this will be appreciated.
Original post:
This web application sends out emails which contain a link to a URL.
Correction-Clarification 9/17/2014:
An .EXE running as a scheduled task on a server (in "support" of the web app and connecting to same database) sends out emails which contain a link to a URL.
The nature of the email content is essentially a "reminder"; the link when clicked is essentially an acknowledgement signaling "done".
Resumption of original post follows:
Clicking the link in the email does 2 things at the target .ASPX page:
the page logic updates a database and sends another email to the same user
the page finishes by displaying a "success" message in the browser
Would it be bad design to eliminate the success message sent by the browser?
I'm thinking the opening of the web page just to announce "success" is not needed. If the target URL were replaced with something with no user interface (e.g. HTTPHandler, webservice) then I'm thinking the email sent back to the same user confirming "success" would be adequate.
Yet, part of that approach "feels awkward", I guess because normally clicking on links in emails causes web pages to open. Given these requirements, would this be bad design to eliminate the browser?
UPDATE - 10-17-2014:
see: Submit to HttpHandler results in RequestType GET instead of POST
update below
Actually, it's bad design to have a state change occur based on a GET request. A number of email systems (and virus scanning software) will follow the link in order to determine whether it should be quarantined or not.
Never mind that a GET request causing a change in state is pretty much against how the web is supposed to work anyway.
What should happen is they click the link, then the mail program opens the browser. You then show a page asking them to confirm the action by clicking a button. That buttons makes a POST request which you then act on.
Finally, I'm not entirely sure how you would eliminate the browser anyway. The mail program detects that it's a link and opens the browser once the user clicks on it. This is no different than how things like opening word documents or zip files. The email program just asks the OS what program is supposed to handle the action and passes it off to that program.
With your update, I think there's a much cleaner way. However this is dependent on the capabilities of the email client that'll be receiving the messages. Should be good for the vast majority of them.
In the body of the email, instead of sending a link, include an HTML form that contains a button which performs a postback to your server. See this ( link ) for samples of how some other companies have done it.
This way the action is a single step instead of two AND you aren't doing things the Wrong Way(tm).
Users need to fill out an access request and once they are done and hit the submit, it emails the request to their supervisor.
Is it possible to email the entire form(with the user data and also to be filled fields by supervisor) in an email so that the supervisor can select accept and the change would be reflected in a SQL database from Outlook itself?
Emailing the form can be done. Writing an Outlook add-in can also be done. But you'll save yourself a lot of time if you just write an "approval" page in your web app and send a link to this page in the email to the supervisor. You can put any information you want in the email, of course.
ETA: But to actually suggest a solution: you could send an email that included a hyperlink, that included identifying information in the query string, and use that as a way of signalling to a web page or web service that the request should be approved. You'd have to work out something with security and authentication, of course, so that not just anybody could call that page and approve the request.
I am currently using the Facebook Javascript SDK and the Facebook C# SDK (soley for retrieving user graph objects).
Everything so far is going great except for the following scenario:
User logs into Facebook
User opens a new browser window and visits my
site
Using the Javascript SDK, I can use the FB.getLoginStatus method to determine if they are connected or not (which they are in this scenario as I have previously authorized my site/app for the facebook login).
However, I need to be able to detect upon the homepage of my site loading for the first time, ideally server-side, if we are in this 'connected' state, and if so, render some different content to screen (logged in vs not logged in).
I can't currently see a server-side method in the Facebook C# SDK that enables me to do the equivalent of FB.getLoginStatus (clientside).
I should point out that any subsequent changes to the users loginstatus is handled via subscribing to the auth.authResponseChange event and all is working fine there, but its the first time page load when the user first hits the site that's the problem.
There isn't a way to do this on the server with any Facebook SDK. You must detect the user's status with the Facebook Javascript SDK. The reason for this is because this information is stored in cookies that are either only readable by facebook.com or that are on you domain, but were set by Facebook and should not be parsed by your app.
You can parse the cookies on your domain if you like, but it isn't recommended because Facebook considers those cookies to be an internal implementation detail and does not guarantee their contents. They could change at any time and break your app.
I would want to deploy an InfoPath (2007) form to users who at the time of filling the form, may not have internet access, then after filling it out, they can go to an internet cafe, connect their laptops to the internet and submit the form to a public web service. I don't want to deploy to SharePoint, I would just want to send the form directly to the user, something close to what you can do with an Adobe PDF form. Is this possible?
Thanks in advance.
I have done something similar before with Infopath 2003 a couple of years ago. I used submission via email though. The advantages of using the email is that it will sit in the outbox of outlook.
all our forms were emailed to a specific email address with a windows service that polled the inbox of the recieving mailbox to extract the form and continue with the workflow. found this was easier path to take than trying to submit to a public webservice. one was almost submit and forget (apart from opening email). Your scenario requires that the user fill out a form during the day and then remembering to submit when they are next connected to the internet is just asking for trouble, IMO.
People will tend to forget that they have to reopen the form and submit it next time they are online whereas if you submit it via email then the only thing they need to do is open and read their email at the end of the day.
I all comes down to user behaviour. if your users are willing to go through the processes that you are thinking about, then yes it is possible to do what you are suggesting.