function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
paul-lmipaul-lmi 

when is the twitter appexchange package going to be updated/fixed?

i was wondering if/when the twitter appex package will be updated.  there are currently a few big flaws in the impleentation that prevent larger orgs from using it.

 

1. the wrapper class is not properly implemented/visible, so you can't actually use it to automate.

2. the queries against Contact and Lead are not optional, and orgs with large tables for these objects have to suffer with wait time for queries to run.  we don't want twitter accounts as contacts, and we don't want to use this for leads either.

3. you have to manually pull tweets.  this is not intuitive for companies already using more robust platforms like co-tweet or tweetdeck.  the expectation is near-real-time, not, when i get around to manually pulling results.  one way around this would be a VF page that auto-polls once every few minutes, so the agent monitoring traffic can just leave it open.

 

if SF isn't planning on updating in the short term, we'd appreciate it if the code was open-sourced on Code Share like the Facebook code was. 

Rasmus MenckeRasmus Mencke

Paul, 

 

We are working on a new version of the Salesforce for Twitter app, the key areas we are focusing on for V2 is some of the areas you highlight below

 

1. Architectural improvements, which includes performance enhancements

2. Productivity enhancements - automate pulling in tweets this will be possible with the spring '10 release where scheduled Apex is now available, automatically link new leads to campaigns, roll-up tweets on Accounts and more features

3. New features - which will be announced at the launch of the new version

 

 

TudelaTudela

We have just implemented Salesforce for Twitter only to find that the scheduler does not seem to work. Although it does run as scheduled, it does not import any tweets (possibly timing out). As a result we are left with having to manually hit the Get More Tweets button throughout the day, which is clearly not a practical solution.

 

1. Is there a solution to this problem? (i.e. how to make the scheduler work)

 

Another issue we have found is that cases created with the Get More Tweets button are not run through the case assignment rules, but instead assigned to the user hitting the button. It would be much better for us if these cases we run through the assignment rules, at the very least that should happen for cases created by the scheduler (assuming that can be made to work).

 

2. How can we send these cases through the auto-assignment rules?

 

3. Is there a target date for when v2 of Salesforce for Twitter will be available?

 

Thanks,

 

Martin

 

paul-lmipaul-lmi

apex scheduler completely skips http callouts/webservices.  i opened a ticket on this, as it's a completely uncovered piece that 's improperly documented, and the document points to two appex partners for scheduling consist of one app that is overkill/not related, and another that isn't even listed anymore.

paul-lmipaul-lmi

was told that it's going to be updated in a few weeks.  also, if your org has very large Lead and/or Contact objects (more than say 50K rows of data), you should open a Case with support to have the Twitter Username fields on these two objects set up with custom indexing, so that you don't take a performance hit on Test class running (when you deploy code, for instance), and also don't have to sit there for minutes at a time while updating conversations with the Get New button.

TudelaTudela

Thanks for the update!

 

Martin