@Brandon Pritchard‚ We use it as well, and it 'just works'. As with any connection I'd recommend creating a specific, unique user for the integration so that you can track and attribute activity. In our case we use it for several purposes. One is to read information from Campaigns and mirror those (as projects) in Workfront 'on creation'. Then when a user makes a request they can link their request to the Salesforce Campaign, thus pulling in data required to process the request without having to re-enter data already on the Campaign. A second use case sees us watch one instance of Salesforce for certain Campaigns being created, then 'mirror' these campaigns in a second Salesforce instance (transforming and standardising some data in the process). Again simple to do. The only issues we see are the occasional errors which are thrown by the connection around the time when there are updates / releases to Salesforce, but that's it.
