Comments on: Email AutoComplete (using jQuery)

By: Scott Hemmeter

Scott Hemmeter — Tue, 21 Feb 2012 22:17:27 +0000

@teejay, the sidebar is the trick to getting the entire bit of code executed at all. If the sidebar is not executed, you can manually execute it in Firebug to make sure it works. Then its a matter of finding a place to put code so that it executes in the console. I’ve never really used the console so I am not sure where to put that.

By: teejay

teejay — Tue, 21 Feb 2012 20:42:42 +0000

I had already modified the code to work on some different fields, using firebug to find the id of the field. However when the email edit page is shown in the cloud console it seems to be wrapped in an iframe which prevents firebug from finding the id for the field. Also the javascript in the sidebar probably doesnt work in the cloud console as the url in the addressbar never seems to change. In fact with the cloud console I’m asking myself if the javascript in the sidebar still works at all, as there is no option to display the sidebar. …

By: Scott Hemmeter

Scott Hemmeter — Tue, 21 Feb 2012 16:25:30 +0000

@teejay, there are a few hardcoded areas in the code. You’ll need to look into the equivalents in the console. In the sidebar code, it has an IF statement checking on the URL so it only runs on the right pages. You’d need to include the URL of the console into that mix. In the main JavaScript, you’ll need to do more elems.push statements to include the IDs of the fields you want auto-complete on so that code actually applies autoComplete to those.

The solution I did is pretty hardcoded to the current pages and needs to be modified if Salesforce changes the UI or you want it on new pages.

By: teejay

teejay — Tue, 21 Feb 2012 15:58:12 +0000

This is great stuff! I got this working on my org, however it won’t work when using the new customer service console! Any ideas how to get it working?

By: Scott Hemmeter

Scott Hemmeter — Mon, 28 Nov 2011 15:40:23 +0000

I updated the code in the post on 11/28 to add a small bit of code to the autocomplete’s “focus” event. Without this, the value in the email field gets overwritten when the items are navigated with the keyboard.

By: Force Feed 11-21-2011 | Force Architects: Delivered Innovation Blog

Force Feed 11-21-2011 | Force Architects: Delivered Innovation Blog — Mon, 21 Nov 2011 18:19:36 +0000

[...] Email AutoComplete (using jQuery) @arrowpointe Q&A for using Email to Case Premium email application. [...]

By: Scott Hemmeter

Scott Hemmeter — Sat, 19 Nov 2011 19:10:38 +0000

@andrew yes, the solution is pretty hardcoded, but easy to manage for a Dev if they choose to. Is Salesforce considering stopping script injection like this? If so, what would stop a browser extension or greasemonkey script from doing the same thing?

By: Andrew Waite

Andrew Waite — Sat, 19 Nov 2011 18:50:04 +0000

Please keep in mind this solution is subject to breakage whenever there is a change to the standard salesforce UI, this partner’s UI implementation or the ability to inject script.

By: Scott Hemmeter

Scott Hemmeter — Fri, 18 Nov 2011 22:43:38 +0000

@Daniel, in this situation I am trying to add auto-complete onto someone else’s work. In one case, it’s the standard Salesforce pages. In another it’s an AppExchange app that is managed and whose page is locked down. This solution is acting more like a greasemonkey script where it modifies someone else’s app pages.

By: Daniel Hoechst

Daniel Hoechst — Fri, 18 Nov 2011 21:54:12 +0000

That’s some nice JavaScript trickery! Definitely tucking this away for future reference. I’m glad my post on autocomplete helped and thanks for the mention. Does JavaScript remoting not work in this situation because of the managed package? On the one hand, it is nice to have it all in JavaScript, but then you can’t write tests to make sure everything works from release to release.

I’ve also found that with my blog posts with pure JavaScript, people have a real hard time debugging problems since there is no compile at page save to catch problems.

By: Jeremy Ross

Jeremy Ross — Fri, 18 Nov 2011 18:59:08 +0000

The AJAX toolkit creates the global variable “sforce” and that’s what everyone uses. I think this is only an issue if different versions of the script are loaded; They all use the same global variable name.

I’m also not sure you’re creating your own instance of jQuery. When you use noConflict(), you’ll still be using the same jQuery instance that any scripts that came before you used. If something comes along later and reloads jQuery with a new tag, it will get its own instance, I think. The fact that you’ve used noConflict() is what really matters here.