Allow for the Salesforce version used to be changed

[jottley]

We current are limited to use the hard coded API version (v26.0). New objects (and functionality) are added with new API versions. There is also the possibility that objects and functionality can be removed with a new API version. An implementer might want to limit their use to an older API version. We are limited by the hard coded version that hasn't been updated but moving to a new API version may turn off things that are needed.

We have a couple of options:

• We can release new versions which each new Salesforce release with an updated hard-coded version.
  • This ensures that new objects and functionality are available.
  • When do we release a new version? When a preview version of Salesforce's next release is available? When Salesforce's new version is released?
  • Those who need older versions would need to use a previous version or fork the code to support a version that we have released a version for.
  • ISVs like Alfresco that use this who's customers may build integrations against Alfresco, Salesforce and use their embedded release would be limited to the functionality support by that release or risk breaking functionality in use of Alfresco's connector.
• We decided on a default API version and add the ability for developers to modify the version used
  • We would need to decide on if
    • The API should be changeable per call?
    • The API should be set when initiating a connection?
    • The API should be set when the factory is initiated?