...
Limitations
As of June 2016, it was not possible to list members of the computer generated group "All Internal Users". In our test environment this group is used for giving user permissions in Salesforce, but it is not possible to check if a given user is part of this group - to set accurate security permissions. It is possible to check if a user is internal - just not if it's an actual member of this group.
There are several security override possibilities in Salesforce. Permissions can for example be given to different Profiles (Standard User or custom profiles etc.) or to User Roles (can also be custom). Objects can also be set to inherit security from other objects (contacts from accounts) or in user hierarchy. Therefore, Salesforce Security must be tested, using settings from the environment where it will be installed, and maybe some changes must be done to the connector before it can be deployed.
...
No refiners are defined in the connector. They must be set up for each installation independently. Under Show Navigator in ViaWorks all the item types and document owners in Salesforce are listed. There the user can specify which items and owners to search for.
Preview
There are is no preview of documents due to the restrictions in Salesforce API usage within 24 hours.
...
After installing the connector using the MSI package the Salesforce Fetch Service can be started. When the fetch service is running please open the ViaWorks Management Console to set up an connection.a connection. If an exe file is used for installing the connector, the Salesforce Fetch Service will start automatically.
Salesforce API
Salesforce objects and the API can be tested in the developer console in the application or in the workbench: https://workbench.developerforce.com/login.php
API Documentation: https://developer.salesforce.com/docs/atlas.en-us.192.0.api.meta/api/sforce_api_quickstart_intro.htm
...