32
21 January 2016 Version 0.6 T4S HP TRIM to Salesforce Integration From FuseIT Salesforce Install Documentation
21 January 2016
Version 0.6
T4S HP TRIM to Salesforce Integration
From FuseIT
Salesforce Install Documentation
AL10
Page 2 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n 1. FuseIT Contact Details
Fuse Information Technologies Ltd
7 Forests Road
Stoke, Nelson
New Zealand 7011
+64 3 547 8200
+64 3 547 8209
AL10
Page 3 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
2. Confidentiality
This document contains confidential and proprietary information of Fuse Information
Technologies Limited (“FuseIT”). This document was prepared for the requesting parties
(“Customer”) for the sole purpose of evaluating the products and services proposed. It is
submitted to you in confidence, on the condition that you and your representatives have, by
receiving it, agreed not to reproduce or copy it, in whole or in part, or to furnish such
information to others, or to make any other use of it except for the evaluation purposes stated
above, and to return it to Fuse Information Technologies upon request. The previous
statement shall not apply to the extent that such statement violates any law requiring such
information to be made available to the public. In the event this document results in a
contract, you may retain this document for use, including making any necessary copies
related to the products and services covered by such contract. The offerings and prices
presented in this document, excluding any leasing quotes or rates, shall remain valid for a
period of 120 days from the document date unless Fuse Information Technologies authorises
an extension.
AL10
Page 4 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n 3. Terms and Conditions
This document is subject to FuseIT’s standard terms and conditions which are available on
request. FuseIT reserves the right to vary the terms of this document in response to changes to
the specifications or information made available by the Customer. Submission of this document
by FuseIT in no way conveys any right, title, interest or licence in any intellectual property rights
(including but not limited to patents, copyrights, trade secrets or trademarks) contained herein.
All rights are reserved.
FuseIT does not assume liability for any errors or omissions in the content of this document or
any referenced or associated third party document, including, but not limited to, typographical
errors, inaccuracies or out-dated information. This document and all information within it are
provided on an "as is" basis without any warranties of any kind, express or implied. Any
communication required or permitted in terms of this document shall be valid and effective only if
submitted in writing.
All contracts with FuseIT will be governed by New Zealand Law and be subject to the exclusive
jurisdiction of the New Zealand courts.
AL10
Page 5 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
Contents
1. FuseIT Contact Details ................................................................................. 2
2. Confidentiality .............................................................................................. 3
3. Terms and Conditions .................................................................................. 4
4. Introduction ................................................................................................. 7
5. Overview ..................................................................................................... 8
6. Salesforce Interface ................................................................................... 10
7. Prerequisites ............................................................................................. 12
8. Salesforce Package Setup ......................................................................... 13
List of Figures
Figure 1 – T4S Bi-directional Exchange of Documents ............................................... 8
Figure 2 – T4S System Overview ............................................................................... 9
Figure 3 – TRIM Documents Shown in an Opportunity Record .................................. 10
Figure 4 – TRIM Documents Associated with the Opportunity Record ....................... 10
Figure 5 – TRIM Documents Detail .......................................................................... 11
Figure 6 – TRIM Record Details ............................................................................... 11
Figure 7 – T4S Tabs ................................................................................................ 13
Figure 8 – Organisation Profile ................................................................................ 13
Figure 9 – Certificates ............................................................................................. 14
Figure 10 – Remote Site Setup ................................................................................ 14
Figure 11 – Outbound Messages ............................................................................. 15
Figure 12 – Data Exporter ....................................................................................... 16
Figure 13 – Cloned Outbound Messages ................................................................. 16
Figure 14 – Data Exporter Workflow Actions ............................................................ 16
Figure 15 – Selecting Actions .................................................................................. 17
Figure 16 – Workflow Rules ..................................................................................... 17
Figure 17 – TRIM Configuration ............................................................................... 18
Figure 18 – TRIM Default User ................................................................................ 19
Figure 19 – Example Object Setting ......................................................................... 20
Figure 20 – Edit Layout ........................................................................................... 22
Figure 21 – Layouts ................................................................................................ 23
AL10
Page 6 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n Figure 22 – TRIM Object Functionality ..................................................................... 23
Figure 23 – Button or Link Customisation ................................................................. 24
Figure 24 – DataExporter Detail .............................................................................. 24
Figure 25 – TRIM Latest Part Link ........................................................................... 25
Figure 26 – TRIM Record View Pane ....................................................................... 26
Figure 27 – Salesforce Container Lookup ................................................................ 26
Figure 28 – TRIM Record Types for Sub-Containers ................................................ 28
Figure 29 – TRIM Record Types Detail .................................................................... 28
Figure 30 – TRIM Record Structure ......................................................................... 29
Figure 31 – TRIM Record Organisation .................................................................... 30
Figure 32 – TRIM Account Example ......................................................................... 30
List of Tables
Table 1 – Prerequisites ........................................................................................... 12
AL10
Page 7 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
4. Introduction
The T4S connector is an enterprise connec tor that empowers Salesforce with robust record keeping features. T4S is a composite application comprising a Salesforce package along with software installed on a Windows based network server hosting T4S software.
In building T4S, and other products in their range, FuseIT have combined the following strengths:
FuseIT, leading Sitecore Technology Partner, Salesforce ISV Consulting Partner, HP IMAP Partner and Microsoft Certified Partner with enterprise experience and expertise in these technologies and;
Salesforce, leaders in CRM and cloud computing. FuseIT is a Salesforce ISV Consulting Partner with involvement in a number of Australia’s largest Government Salesforce implementation at the Department of Business and Innovation in Victoria and;
TRIM (HPE Records Manager/Content Manager) , a document and records management system software. With tight desktop integration and the ability to scale across large, distributed environments, TRIM lets you capture, manage, access and make more secure your enterprise information, from electronic to physical records and from creation to ultimate disposal and;
Sitecore CMS, the enterprise web content management software featuring online marketing tools and;
Microsoft .NET, an integral part of many applications running on Windows and provides common functionality for those applications to run. FuseIT has been a Microsoft Certified Partner for over 15 years gaining huge experience across the range of .NET technologies
This document accompanies the document, “T4S_Server_Install_Document.pdf” that outlines how to install the T4S components onto a local Microsoft T4S server provisioned on your local network.
AL10
Page 8 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n 5. Overview
5.1. High Level
T4S is a solution that enables documents to be exchanged between Salesforce and HPE Records Manager/Content Manager (called TRIM hereafter). The application is Salesforce centric in that most of the functionality is surfaced in Salesforce.
Figure 1 – T4S Bi-directional Exchange of Documents
T4S is a powerful product with many features:
Onshore record retention solution.
Documents can reside only in TRIM (referenced in Salesforce).
Documents can reside in both TRIM and Salesforce (configurable).
TRIM document search and view from Salesforce.
Save, update, delete or download TRIM documents from Salesforce.
Upload documents from Salesforce to context aware containers in TRIM.
Save Salesforce records to TRIM as PDF documents.
Save Salesforce emails or email attachments to TRIM as documents.
Action saves to TRIM by
o Button click or
o Scheduled task or
o Salesforce Workflow
Add direct links to TRIM documents in Salesforce.
Show documents in selected TRIM containers in Salesforce.
View all documents in a container from a predefined search.
Save Salesforce data exports to TRIM or a local server using scheduled tasks.
Control access with Salesforce roles and TRIM permissions.
AL10
Page 9 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
Two way SSL connection between Salesforce and the T4S server.
Almost zero impact on TRIM (uses TRIM web services only)
Configurable for multiple TRIM instances
Mobile ready
T4S also offers a number of potential expansion options:
• Federation of Salesforce record data (plus attachments and documents) to other databases like SQL Server, Oracle, and PostGRES
• Expose Salesforce data in a local website for disaster availability and recovery
• Data mine Salesforce data using existing industry tools like SSIS.
T4S requires the provisioning of a network T4S server, either physical or a VM, running Microsoft Server 2008 or similar. This server will host G4S and supporting the T4S ancillary software.
Figure 2 – T4S System Overview
As detailed in this document, a T4S Salesforce package is also required to be installed in the connected Salesforce instance.
T4S uses SOAP web services to communicate with both Salesforce.com and TRIM. Both connections are SSL secured. T4S uses the Salesforce Partner API which is advantageous as custom objects and fields are readily available. The connection to Salesforce uses two-way SSL and is certificate strengthened.
T4S uses the TRIM Web Services API. From mid-2016, a new release will be available to support RESTful services for use with HPE Records Manager 8.3 and above.
AL10
Page 10 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n 6. Salesforce Interface
A Salesforce instance or Org is required for T4S. The Salesforce Edition must be Enterprise or Unlimited.
T4S provides “Trim Documents” buttons that can be added to Salesforce objects requiring related TRIM documents (Figure 3). The buttons provided are for the default Salesforce objects such as Account, Contact etc. ready to be added to the page layouts. Custom objects can duplicate the existing buttons and be added to your custom object layouts.
The following image shows how the button appears in the Opportunity record.
+
Figure 3 – TRIM Documents Shown in an Opportunity Record
Clicking on the Trim Documents button opens a Trim Documents page showing all the existing documents in TRIM and those scheduled to be pushed to TRIM that are related to the parent Object (in this case an Opportunity) .
Figure 4 – TRIM Documents Associated with the Opportunity Record
Users can click on the Attachment link (left column) to open a Salesforce page that contains information about the document (see Figure 5). Clicking on the “Trim Name” link will open a new Visualforce page with the information about the TRIM record (see Figure 6). From here
AL10
Page 11 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
the User can modify the TRIM record details, change or upload a new file, download the TRIM Server version, or delete the Trim Record.
Figure 5 – TRIM Documents Detail
Figure 6 – TRIM Record Details
AL10
Page 12 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n 7. Prerequisites
The following table indicates what is required before T4S can be successfu lly implemented in a Salesforce instance and network environment.
Prerequisites
Required – Salesforce
Action: Acquire Salesforce Enterprise or Unlimited. One user is required to be enabled for API access. FuseIT recommend user is dedicated for T4S access.
Required – License for G4S
Action: A site wide license for G4S is required.
Required – Install and configure T4S
Action: Purchase SSL Certificate (Salesforce approved).
Action: Use local resources or FuseIT to install T4S on the network that has access to the TRIM server and configure to the Salesforce instance.
Table 1 – Prerequisites
AL10
Page 13 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
8. Salesforce Package Setup
The following details how to install the T4S package into Salesforce.
8.1. Tab Setup
Install the latest T4S package from FuseIT. Add the Trim, Trim Records and DataExporters Tabs to your tabs list by clicking the “+” sign and choosing “Customize My Tabs” or set the available tabs via “Setup” “App Setup” “Create” “Apps” and edit the available Tabs that are displayed . Note: Only Trim Records Tab should be made available for general Users.
Figure 7 – T4S Tabs
Note: The Trim & DataExporters tabs are for admin Users only, regular Salesforce Users will only need the Trim Records tab.
8.2. Two-way SSL Certificate Setup
Note: If the org is a Sandbox or Developer Org it helps to have the “Company Profile” “Company Information” named in a useful manner before the next step, so the certificate can be identified once installed.
Figure 8 – Organisation Profile
Create a new Salesforce Certificate by going to “Setup” “Administration Setup” “Certificate and Key Management” “Create Self-Signed Certificate”
AL10
Page 14 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n
Figure 9 – Certificates
Save the certificate.
Download the certificate to the T4S Server for installation (See T4S_Server_Install_Document.pdf)
8.3. Remote Site Setup
Add the T4S endpo int to the “Security Controls” “Remote Site Settings” “New Remote Site”
Figure 10 – Remote Site Setup
AL10
Page 15 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
8.4. Workflow and Outbound Message Setup
Navigate to “App Setup” “Create” “Workflow & Approvals” “Outbound Messages”.
Figure 11 – Outbound Messages
You will see two existing managed Outbound Messages. Click on each one and “Clone” each message so that the end point URL points to your T4S Server address and specify a new name i.e. Change “your.domain.com” to your domain or IP address where T4S is located.
AL10
Page 16 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n
Figure 12 – Data Exporter
AL10
Page 17 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
Figure 13 – Cloned Outbound Messages
Navigate to “Workflow Rules” and click on “Data Exporter Synchronization Rule” and edit the “Workflow Actions”. “Add Workflow Action” “Select Existing Action” from the drop down list.
Figure 14 – Data Exporter Workflow Actions
Select the new cloned Outbound message and Save.
AL10
Page 18 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n
Figure 15 – Selecting Actions
Repeat for the "Trim Record Synchronization Rule" Workflow Rule, selecting the new cloned TRIM Synchronization Message.
Figure 16 – Workflow Rules
8.5. TRIM Server Object Setup
Navigate back to the Trim Tab, and create a “New” Trim object
AL10
Page 19 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
Figure 17 – TRIM Configuration
The following descriptions are provided:
Enable Scheduling
o This will use run the "Trim Record Synchronization Rule" on a scheduled
bases to send the Outbound Message to T4S that will cause all the
“Scheduled” TRIM records in the Salesforce Org to be synchronized with the
TRIM Server.
TRIM Default Container URI
o The Container that will be used by default for saving new TRIM records to
TRIM.
(See Additional Info for finding the URI of the Container you wish to use)
Client Certificate Name
o The Name given to the Client Certificate created earlier in the Setup process.
o This certificate allows two-way SSL communication with the T4S Server.
Handle Deletion.
o Options available when Salesforce Attachments are deleted within
Salesforce.
Delete Nothing: If an Attachment related to a TRIM record is deleted
in Salesforce then do not take any action to the Salesforce TRIM
record or the Record on the TRIM Server.
Delete Salesforce: This will delete the related Salesforce TRIM record
associated with the Attachment, but will not touch the Record on the
TRIM Server.
Delete Salesforce and TRIM: This will mark the Salesforce TRIM
record as “delete”, upon the next synchronization with the TRIM
Server the Record in TRIM will be deleted and the Salesforce TRIM
record will be deleted.
Custom Links
o This is the link to the “Scheduler” page that allows you to set a schedule for
how often you wish T4S to synchronize with Salesforce.
o Enable Scheduling must be checked for scheduled synchronization.
TRIM IP Address
o This is the internal IP address that T4S Server uses to connect to your TRIM
Server web service.
AL10
Page 20 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n
o As this is the address between T4S and TRIM, the IP address does not need to
be added to Salesforce Remote Sites settings.
T4S IP Address
o This is the address for Salesforce to connect to the T4S web service.
o The address must be added to the Salesforce Remote Site settings as described
previously.
o The T4S web service must have a CA Signed Certificate allowing SSL
connection without a certificate warning for Salesforce to connect.
Record Link IP Address
o T4S has a built in web page that allows Users to view TRIM Records directly
from Salersforce. If you already have a secure URL that Users can access TRIM
Records with, then you can enter the URL here so T4S will use it instead of the
default.
Record Link New Text
o Some secure URL’s that allow Users to view TRIM Records require the TRIM
RecordNumber to be formatted before it can be used.
Enter the character that should be used in the URL and it will replace the
Record Link Old Text character(s)
Record Link Old Text
o This is the character within the RecordNumber that should be replaced by the
Record Link New Text char so that the Record Link IP Address is well formed.
Login Credentials
o Button allowing default TRIM Credentials stored for connectio n to the TRIM
Server when synchronization occurs.
o These credentials are encrypted and stored using Salesforce best practices.
8.6. TRIM Credentials
Click on the “Login Credentials” button on the new and enter a default TRIM Login credentials to run the “Scheduled” TRIM record synchronization.
Any Salesforce user that does not enter their “own” TRIM Credentials into their “Trim Records” page will run all their TRIM interactions using this “default” login.
Figure 18 – TRIM Default User
AL10
Page 21 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
8.7. TRIM Settings Setup
Create a new TRIM Setting for each object type you wish to automate.
Figure 19 – Example Object Setting
The following descriptions are provided:
TRIM Setting Name
o A name that relates to the Salesforce standard or custom object the TRIM
Setting is for.
TRIM Server
o The Server the Setting is for.
sObject Name
o The Salesforce object name such as Contact, Opportunity or your custom
object name including the “__c”
o The sObject Prefix will be automatically filled in once the page is saved.
TRIM sObject Container Uri
o This is the Container where TRIM records for the Salesforce object will be
saved to by default.
o If “Auto Create Sub Container” is checked, then each Salesforce object of
this type will be saved into its own Container below this URI
o If “Auto Create Sub Container” is not checked, then each Salesforce object
of this type will have all the TRIM records bundled into the single Container.
AL10
Page 22 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n
Sub Container Record Type Name
o The TRIM Server Record Type name for creating Sub Containers below the URI
given above.
o Note: You will need to make sure TRIM is configured to allow Record Types
specified within “Trim Records” custom object “Record Type” pick list to be
created with the TRIM “Sub Container Record Type Name” specified here.
(See Configuring TRIM Server to use Sub-Containers Example)
Auto Add Attachment
o When enabled any attachment added to the Salesforce object will automatically
create a Trim Record and be set for “Scheduled” synchronizatio n with TRIM
Enable Sub Container
o A custom Visualforce page can be added to any standard or custom object
which displays all the TRIM Records for the associated object. This Visualforce
page will also enable the creation of the Sub Container for the Salesfo rce object
if one does not already exist.
o Note: “Auto Add Attachment” will fail if “Enable Sub Container” is checked, but
the Salesforce object the Attachment is being added to does not yet have a Sub
Container created on the Server.
o See Additional Info for more details on Creating Sub Containers.
Auto Delete Attachment After Creation
o If enabled then any Attachment that s added to the Salesforce object and a
associated TRIM record created, will have the original attachment deleted upon
successful synchronization with TRIM i.e. only TRIM will have the binary record
and it will no longer exist in Salesforce.
Container Specification Property Set
o The related Container Specification Property Set that contains a group of
Specification Properties used when TRIM Containers are created for this Trim
Setting.
o See Container Specification Property Set
Record Specification Property Set
o The related Record Specification Property Set that container a group of TRIM
Specification Properties used when creating TRIM Records for this Trim Setting.
o See Record Specification Property Set.
8.7.1. Container Specification Property Set
When TRIM Containers are created, it is possible to use TRIM Specification Property Sets to specify the meta data the container will be saved with.
T4S uses default Specification Properties when creating Containers, but you are able to override the defaults and add your own TRIM properties instead.
A default Specification Property Set has been created when T4S was installed, you can add additional properties to this set, or create a whole new set as needed.
T4S keeps track of the created containers in Salesforce by inserting the sObject Salesforce ID into the Containers External ID field.
AL10
Page 23 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
8.7.2. Record Specification Property Set
Similar to the Container Specification Property Set, the Record Specification Property Set is a way of including custom or additional properties when a TRIM Record is created of updated.
The Specification Property can use dynamic values as well as set values.
To enable dynamic data you can create an additional Salesforce text or formula field on the Fuseit_t4s__Trim_Record__c object that calculates or pulls additional data.
Within the Specification Property you can set the Name of the property to the name of Specification Property to be used e.g. recTitle (which will override the default Attachment Name T4S would insert), and in the value field enter the name of the custom field created, including the “__c” of the field name.
When T4S comes across a value that matches a custom field, the field valued will be used.
8.8. Trim Record Setup
8.8.1. Standard Objects
By default there are pre-configured buttons that can be added to standard Salesforce object that allow TRIM records to be created. As an example navigate to “Accounts” with in Salesforce and select an existing Account.
Select “Edit Layout”
Figure 20 – Edit Layout
Select “Buttons” and drag “Trim Documents” and “Trim Snapshot” buttons to the Custom Buttons section of the layout, and save.
AL10
Page 24 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n
Figure 21 – Layouts
Repeat for each object you wish to add TRIM record User functionality to. TRIM documents button takes the User to a page displaying all the current TRIM records for the associated object.
Trim Snapshot creates a PDF t ime stamped snapshot of the current object layout so that it can be saved as a record within TRIM (see Additional Info about setting up TRIM Snapshot for custom objects).
Clicking on the “Trim Documents” button will take you to a Visualforce page for that object.
Figure 22 – TRIM Object Functionality
New TRIM Record
o Allows you to upload a new Attachment or select an existing attachment for
synchronization with TRIM Server
Refresh
o Refreshes the view to update the status of any synchronization action.
Login Credentials
o Allows the logged on Salesforce User to enter their own TRIM Server
credentials for searching and synchronizing with TRIM Server.
Synchronize All
o Will force manual synchronization of all Trim Records associated wit h this
Salesforce object.
Back
o Will return the user to the previous page.
AL10
Page 25 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
8.8.2. Custom Objects
To add TRIM record functionality to your custom objects, navigate to “Setup” “App Setup” “Create” “Objects” and select your custom object. Scroll down to “Custom Buttons and Links” and create “New”.
Duplicate the default “Trim Documents” button changing the custom syntax code to use your custom object name e.g. Replace <customObject> with your custom object name including the “__c”:
apex/fuseit_t4s__TrimAttachmentsSection?parentId={!<customObject>.Id}&parentTitle={!<customObject>.Name}
Figure 23 – Button or Link Customisation
8.9. Data Exporter Setup
Enable Data Export for your Organization by going to “Setup” “Administration Setup” “Data Export” and “Export Now” or “Schedule” a periodic export of you Salesforce Data.
Once the Exported data is available, navigate to the DataExporters Tab and create New.
AL10
Page 26 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n
Figure 24 – DataExporter Detail
DataExporter Name
o A name to identify this Exporter.
Enable Scheduling
o Activate the DataExporter
Path
o A path relative to the T4S Server that T4S is able to save the Salesforce Data
files to
Custom Links
o Visualforce DataExporter scheduler page that will create a “Scheduled Job” to
run the DataExporter on a scheduled basis.
8.10. Additional Info
8.10.1. Finding the Default URI
You can use the TRIM Web Client by finding the Container or Record and clicking on the “Latest Part” link within the Properties pane.
AL10
Page 27 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
Figure 25 – TRIM Latest Part Link
Use TRIM Desktop Client by right clicking on the Record View Pane, and adding the custom field “Unique Identifier” to the list of displayed fields.
Figure 26 – TRIM Record View Pane
AL10
Page 28 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n
Once Salesforce and T4S have been setup, you can use the Container Search feature to easily find any Container URI
Figure 27 – Salesforce Container Lookup
8.10.2. Creating Sub Containers
The T4S package comes with two example Visualforce pages that enab le Sub Containers to be created, and list related Records on the TRIM Server.
TrimContainerRecordsViewAccount.page
o Visualforce page that can be added out of the box to the Account Layout.
o Uses APEX “TrimContianerRecordsViewController.cls ” class to extend
StandardController.
o Notifies User viewing an Account if a Sub Container does not already exist for
the record.
(If “Enable Sub Container” checked within a “Trim Setting” for Accounts.)
o Allows User to create Sub Container for that Account.
o Displays all TRIM Records within the Sub Container regardless of any
Salesforce relationship. i.e. if any TRIM Record are added to this Sub Container
by any other means including T4S then this Visualforce page will display and
link to the TRIM Server Record.
TrimContainerRecordsViewContact.page
o Visualforce page that can be added out of the box to the Contact Layout.
o Uses APEX “TrimRecordsViewController.cls” class to extend
StandardController.
o Displays all TRIM Records on the TRIM Server with the Record External ID set
to the Salesforce 18 char sObject ID of the Contact being viewed. i.e. if any
TRIM Record is added to TRIM regardless of the Container it is placed in, and
AL10
Page 29 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
its external ID is that of the Salesforce sObject ID then this Visualforce page
will display and link to the TRIM Server Record.
To extend and create your own Visualforce page views for any other Standard or custom object, copy one of the example pages and name it accordingly.
Change the APEX standardContoller attribute to the object you wish the page to appe ar on. e.g. <apex:page standardController="Lead" extensions="TrimRecordsViewController"> or the name of your custom object.
Decide which extension APEX class you wish to use.
extensions="TrimContianerRecordsViewController ” to display all Records within a
Container.
extensions="TrimRecordsViewController” to display all Records with the External ID
set to the Salesforce ID
8.11. Configuring TRIM Server to use Sub-Containers Example
Log into TRIM desktop as a User with Privileges to create /edit Record Types.
Figure 28 – TRIM Record Types for Sub-Containers
Create a duplicate File Folder Record Type setting the “Container Level” to something like 4 so that it can be created underneath an existing Container, and Record Types such as “Document” can be created within it.
AL10
Page 30 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n
Figure 29 – TRIM Record Types Detail
This can be used to create Containers for all Salesforce objects of a certain type, such as Accounts or Leads etc.
Create another “File Folder” Record Type that each Salesforce Object can have to store all the associated Records within.
The “Container Level” should allow it to be created within the “Salesforce Object Type” Record Type.
Figure 30 – TRIM Record Structure
Create Containers within TRIM for your various Salesforce Objects using the “Salesforce Object Type” Record Type, e.g. Accounts, Leads, Custom objects etc.
AL10
Page 31 of 32
Sa
les
forc
e In
sta
ll Do
cu
me
nta
tion
Note the URI for each Container created (refer to “Finding Default URI” to see how to add “Unique Identifier” Field to the Properties Record View Pane)
Figure 31 – TRIM Record Organisation
Within “Trim Settings” put the name used for the TRIM Record Type used to create individual Sub Containers, e.g. “Salesforce Object” into the “Sub Cont ainer Record Type Name” field, and the URI for the parent Container for that particular Salesforce object.
Figure 32 – TRIM Account Example
8.12. Auto creation of Sub Containers.
There are two ways of automatically creating sub containers for your Salesforce objects if “Enable Sub Container” has been checked, and the “Sub Container Record Type Name” have been configured correctly within the TRIM Server.
AL10
Page 32 of 32
Sa
les
forc
e I
ns
tall
Do
cu
me
nta
tio
n 8.12.1. Bulk Creation
For existing Salesforce data you will see a grid displayed below the newly saved Setting. By clicking on the Action check box for each record you wish a container to be created for, and then submitting the action, will fire of a bulk Sub Container web service call to T4S to create containers for this particular setting.
8.12.2. Manual Creation
For all new Salesforce data or records that were not created by the above bulk creation, the Visualforce page “TrimContainerRecordsView<objectName> .page” or “TrimContainerRecordsView<objectName> .page” as out lined in 8.10.2 “Creating Sub Containers” section.
These pages will display a “Create” button that will create the sub container in TRIM if one has not already been created or found.
8.13. TRIM Snapshot Setup
To create a PDF Snapshot for a Custom Salesforce sObject, copy one of the existing TRIM Snapshot Visualforce pages e.g. TrimPDFAccount.page.
The name of the new Visualforce page must start with “TrimPDF<object name> page. Within the new Visualforce page, set the standardController to the Salesforce object that you want to use e.g. <apex:page readOnly="true" standardController="CustomObjectName" RenderAs="PDF">
Create a custom button copying an existing “Trim Snapshot” button, and change the syntax to use your custom object name e.g. Replace <customObject> with your custom object name including the “__c”:
/apex/fuseit_t4s__TrimPDFGenerator?parentId={!<customObject>.Id}&parentTitle={!<customObject>.Name}
