Presentation is loading. Please wait.

Presentation is loading. Please wait.

HPE Content manager TO SALEFORCE INTEGRATIONs

Similar presentations


Presentation on theme: "HPE Content manager TO SALEFORCE INTEGRATIONs"— Presentation transcript:

1 HPE Content manager TO SALEFORCE INTEGRATIONs

2 SITECORE TECHNOLOGY PARTNER Salesforce CONSULTING PARTER
Since 1992 Around 50 enterprise customers SITECORE TECHNOLOGY PARTNER Salesforce CONSULTING PARTER HPE BUSINESS PARTNER

3 S4S SooT M4S S2T T4S Connector Suite Content Manager
We have many enterprise connectors between different technologies. Note that our G4S and S4S connectors are very similar but S4S has Sitecore specific features. Our other key Sitecore connector is called SooT which extends Sitecore with the secure document handling. It does this by integration with HPE Records Manager, also known as TRIM Sitecore and TRIM, and ASP.NET applications are all built on Microsoft stacks We also have M4S that works well with S4S and integrates Sitecore to MongoDB. We will see more on that soon But for now, lets look at why we need to integrate at all T4S

4 Selection of Customers
Our customers are from across the globe and in many verticals. They include Fortune 500 companies like American Express and United Health Group.

5 Salesforce to HPE CM Integration

6 HPE Content Manager TRIM, CM, or RM (Records Manager)
Electronic document and records management system Helps business meet document governance and regulatory compliance obligations Server based Gold standard for many verticals Public sector Healthcare Energy and utilities Banking and finance

7 S2T Overview Native Salesforce application
Empowers Salesforce with robust record keeping features Salesforce  CM Push attachments and chatter documents Push Salesforce records to CM as PDF documents Includes update and delete functionality Configurable for multiple CM instances Mobile ready

8 REST or SOAP with SSL protection (HTTPS). No data at rest
S2T Building Blocks Salesforce REST or SOAP with SSL protection (HTTPS). No data at rest CM Workgroup Servers Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Clients Locations Web Services Records Actions

9 Saving Documents to TRIM
CM Salesforce Workgroup Servers Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Clients Locations Web Services Records Actions Push individual documents to CM

10 S2T System Requirements
S2T runs on any web browser supported by Salesforce Connects to CM web services (REST or SOAP) Works with TRIM 7.02 and later Earlier versions may require customization Companies need to expose a port so Salesforce can access their CM web services

11 HPE CM for Salesforce

12 T4S Overview Save record attachments and chatter documents
Salesforce  CM Save record attachments and chatter documents Save records as PDF documents Save data exports to a nominated server or to CM Salesforce  CM View CM records and metadata via a link in Salesforce Multiple search options including predefined searches Expose records in a CM container for viewing

13 T4S Overview CM Salesforce CRM Real time or scheduled event
Workgroup Servers Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Clients Locations Records Bi-directional Actions

14 T4S Physical Components
Record Management Integration Server T4S Physical Components .NET to Salesforce Integration RMI Server CM Salesforce CRM Workgroup Servers Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Web Services Clients G4S Locations Web Services Records Actions

15 T4S Synchronization RMI Server CM Salesforce CRM G4S Workgroup Servers
Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Web Services Clients G4S Locations Web Services Partner API Records Actions G4S pushes attachments to CM Outbound message starts G4S G4S requests attachments Push using a scheduled task Push to CM manually or

16 T4S has multiple configurations
Save options Delete options Container linking Record linking Salesforce backup options Federate Salesforce data to other systems Push data to Salesforce from other systems

17 T4S Save Options CM Salesforce CRM
Option 1: T4S copies document to CM and leaves a copy in Salesforce Workgroup Servers Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Clients Locations Records Actions Customer uploads document to Salesforce

18 T4S Save Options CM Salesforce CRM
T4S adds an access link in Salesforce T4S Save Options CM Salesforce CRM Option 2: T4S copies document to CM and deletes copy in Salesforce Workgroup Servers Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Clients Data Residency for Salesforce documents Locations Records Actions Customer uploads document to Salesforce

19 T4S Delete Options CM Salesforce CRM
Delete Option 1: Delete in Salesforce, delete in CM Workgroup Servers Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Clients Locations Records Actions

20 T4S Delete Options CM Salesforce CRM
Delete Option 2: Delete in Salesforce, keep in CM Workgroup Servers Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Clients Locations Records Actions

21 Saving a Salesforce Record as a PDF
Customer clicks CM snapshot button CM Salesforce CRM PDF can be located in mapped container Workgroup Servers Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Clients Locations Records Actions Customer saves a Salesforce record to CM as a PDF

22 T4S Record Links CM Salesforce CRM Access link is added in Salesforce
Customer uses T4S search to find the CM record CM Salesforce CRM Customer locates record Workgroup Servers Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Clients Locations Records Actions Customer links a CM record to a Salesforce object

23 T4S Container Links CM Salesforce CRM
Filtered search shows access links to records in a mapped CM container CM Salesforce CRM Records only reside in CM Workgroup Servers Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Clients Locations Records Actions Customer views CM records in a Salesforce object

24 Automate Salesforce Data Exports
Salesforce backup solution Option to persist Salesforce Data Exports to SQL Server Use industry tools to interrogate, map or data mine Expose the data via web services Transparently federate data to other systems Expose data using an Intranet or Extranet website Expose the data via a Sitecore web portal

25 Processing Salesforce Data Exports
RMI Server CM Salesforce CRM Workgroup Servers Contacts Web Services Data Export Accounts Clients Contacts.csv Accounts.csv Opportunities.csv Documents.csv Leads.csv Products.csv Campaigns.csv Custom Objects.csv Cases.csv etc in zip files Opportunities G4S Documents Locations Web Services Leads Records Products Campaigns Actions Cases Custom Objects Data Export initiated by scheduled task G4S requests attachments Data Export is now local

26 T4S Deployment Options RMI Server CM Salesforce CRM G4S
Accounts Contacts Opportunities Documents Leads Products Campaigns Cases Custom Objects Salesforce CRM Workgroup Servers Clients Locations Records Actions

27 T4S Deployment Options Local Salesforce

28 T4S Deployment Options Local Azure Salesforce

29 T4S Deployment Options Azure Salesforce

30 T4S Deployment Options Azure Private Cloud Salesforce

31 T4S Deployment Options Private Cloud Salesforce

32 T4S Deployment Options Local Private Cloud Salesforce

33 T4S Deployment Options Local Private Cloud Salesforce

34 T4S Deployment Options Local Azure Private Cloud Salesforce

35 T4S Many to Many Options Local Azure Private Cloud Salesforce

36 T4S Many to Many Options Local Azure Private Cloud Salesforce

37 T4S Many to Many Options Local Azure Private Cloud Salesforce

38 T4S Many to Many Options Local Network Azure Amazon Private Cloud
Salesforce CRM

39 Extended Salesforce Localisation
RMI Server Salesforce CRM Contacts Accounts Opportunities Documents Leads Products Campaigns Custom Objects Cases Contacts Web Services Data Export Accounts Federated to other systems Contacts.csv Accounts.csv Opportunities.csv Documents.csv Leads.csv Products.csv Campaigns.csv Custom Objects.csv Cases.csv etc in zip files Opportunities G4S Documents Leads Products Campaigns Cases PostGRES Oracle SQL Server Custom Objects Data Export initiated by scheduled task

40 CM Server Settings

41 sObject Settings Page

42 CM Synchronization Automation Scheduler

43 My T4S Records

44 Record Details Page

45 Container Search

46 Object View of Associated Records in CM

47 Salesforce CM Records for a Salesforce Object

48 Upload or Select a Local Document and Push to CM

49 Add Chatter File

50 Create a Linked Record Page

51 Search CM Records to Link To

52 DataExporter Page and Download Scheduler

53 S2T Pricing (on Salesforce seats)

54 T4S Pricing (on CM seats)

55 Product Pricing G4S USD Application Server based $4800
Business Rewards Product Pricing G4S USD Application Server based $4800 Web Many domains $8000 S4S Basic 1 domain $16000 Extended Many domains $20000 Enterprise Many Sitecore locations $42000 Enterprise Multi Many Salesforce Orgs $42000 S4S with EXM EXM $30000 Enterprise EXM Many Sitecore locations $60000 Enterprise EXM Multi Many Salesforce Orgs $60000 Others M4S Add $6000 Maintenance and Support 20% p.a.

56 Key Contacts www.fuseit.com terry@fuseit.com - Terry Humphris
- William Boyd


Download ppt "HPE Content manager TO SALEFORCE INTEGRATIONs"

Similar presentations


Ads by Google