Content Manager for Salesforce (T4S)

Content Manager and T4S

T4S is a high volume connector that provides the ability to push Salesforce attachment and chatter documents to CM and open CM documents in Salesforce. The connector installs into Salesforce and uses FuseIT's proven G4S technology that is installed on a Microsoft network server (or VM) in your domain. Because this solution uses standard Cweb services it has no impact on the Cinstallation.

T4S Technical

T4S is a managed package and a .NET application running on IIS that uses outbound messages and web services to pass individual or multiple documents to and from CM

What are the T4S features?

  • Onshore record retention (data residency) solution.
  • Native application.
  • Push attachments and chatter documents to Cby button click.
  • Queue multiple documents to be pushed to Cby scheduled task.
  • Documents can reside only in C(referenced in Salesforce).
  • Documents can reside in both Cand Salesforce (configurable).
  • CM document search and view from Salesforce.
  • Save, update, delete or download Cdocuments from Salesforce.
  • Upload documents from Salesforce to mapped containers in CM.
  • Save Salesforce records to Cas PDF documents.
  • Save Salesforce emails or email attachments to CM as documents.
  • Add direct links to Cdocuments in Salesforce.
  • Show documents in selected Ccontainers in Salesforce.
  • View all documents in a container from a predefined search.
  • Save Data Exports to Cor local servers using scheduled tasks.
  • Control access with Salesforce roles and Cpermissions.
  • Two-way SSL connection between Salesforce and the T4S server.

A key feature of T4S allows Data Exports to be automatically pulled from Salesforce and inserted into a local folder on the nominated Microsoft server. This off-site data protection helps organizations meet their record keeping and risk management obligations.

For more information please download the T4S brochure.

Data Privacy

T4S is easily configured to ensure sensitive documents are never stored in Salesforce. T4S maps Salesforce records to CM containers and holds a reference to them in Salesforce. The following example shows how a contact record attachment is never stored in the cloud.

  1. A user attaches a sensitive document to a Salesforce contact record.
  2. T4S functionality calls T4S Web Services.
  3. T4S Web Service methods pass the request to the G4S component.
  4. G4S requests the document from Salesforce and moves it to CM.
  5. The document resides in a mapped location in CM but still referenced in Salesforce for accessibility.

T4S is very flexible in the way it maps records to CM with a number of configurable storage options.

CM and Data Privacy
Join our next S4S webinar!

See S4S working in Sitecore 9.

Registration is now open for
20 March 2019

Time in Nelson, New Zealand

Our Saturday is Friday in the US

Ready to join the integration revolution?
Get started and enjoy the benefits sooner