forceworkbench

The Workbench instance at workbench.developerforce.com accesses your Salesforce data via OAuth (i.e. Remote Access). From Salesforce Help, to revoke a previously granted remote application, such as Workbench, do the following: In Salesforce, click <Your Name> | Setup | My Personal Information |

he||o all when you first login ynu need to allow WB to access your data on SF. How to block this?

Anyone try deploying to Heroku? Any problems?

This is a relatively minor release for Workbench, but in keeping up with the latest Salesforce API 24.0, this updates all the WSDLs and API clients, adds limited support for running Workbench on Heroku ([link]), and includes minor bug fixes. Support for running on Heroku includes:

I'm happy to announce that the Workbench Tools browser extension is now available for Google Chrome! Like Workbench Tools for Firefox, this Google Chrome browser extension give you one-click access to login from Salesforce to Workbench. After you have your Workbench instance setup, download Workbench Tools

Finally getting with the times, Workbench is now using Git for source control management! Workbench was the last of my projects still on SVN, so it was about time to switch everything over. I played with the idea of using GitHub, where I have been ... [More] putting new projects (https:// github.com/rbrainard), but I really didn't want to lose Google Code's [Less]

This version of Workbench is primarily a version upgrade for support of API 23.0 with updated SOAP, REST, and CometD clients. There are also a couple bug fixes to handle expected API errors to reduce log noise. It is available for download at: [link]

There shouldn't be anything special about EU1, but can you let me know if there's any error message you see? Also, at what stage in the login does it fail? Does it get through all the OAuth stuff where it asked for username and approval? One thing to check is make sure you are using API 22.0 with EU1 since it's still on Summer '11.

Hi Ryan, many thanks for providing such a tool!! I really like working with it and I'm doing so for some of our customers on NA1 org. Right now, we have a new customer with his Org on the EU1 servers and I cannot connect to these. Am I doing something wrong?? Many thanks - Julius

The main benefits I see: - Simplified authentication. The SessionHeader could automatically be constructed using the active session in Workbench. - API version in endpoint would be controlled by the Workbench setting. - Additional headers (e.g. DebuggingHeader) could be added and be controlled by Settings. Just like the Apex Execute feature.