UNIVERSITE DE BOURGOGNE UFR Sciences et Techniques Dpartement

UNIVERSITE DE BOURGOGNE UFR Sciences et Techniques Département d’Informatique UNIVERSITÉ ANTONINE Faculté d’ingénieurs en Informatique, Multimédia, Réseaux et Télécom. WORK PLACEMENT PRESENTATION by Elie Matta Development on Cloud-Based CRM Synchronization and migration from a web application to a CRM solution Friday, 15 th of July 2011 1 LEBANON-FRANCE © 2011

1. Introduction Outline A. Context of the internship B. Objectives 2. Analysis and design A. Background research B. Workflow C. Database architecture D. UML diagrams 3. Development and verification A. Stored procedures and implementation B. Datamaps and simulation C. Results D. Verification 4. Conclusion 2

Outline 1. Introduction A. Context B. Objectives 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results 4. Conclusion 1. Introduction A. Context of the internship 1. PRIVACY APPLIED The tech division of PRIVACY APPLIED: 1. Leader in e-catalogue & B 2 B solutions[1] PRIVACY APPLIED 2. Offers solutions for data interchanges 3. Certified by GS 1 standards 2. Functional requirements PRIVACY APPLIED Web Application 1. PRIVACY APPLIED 2. PRIVACY APPLIED 3. PRIVACY APPLIED Reduce duplication Data analysis Cloud-based CRM[2] 1. Structured data 2. Report management 3. High customization 3

Outline 1. Introduction A. Context B. Objectives 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results 4. Conclusion 1. Introduction B. Objectives 1. Synchronization between SFDC and PRIVACY APPLIED : i. Clients ― Information (id, Name, etc. ) ― Details (Number of Offers, Turnovers, etc. ) ii. Users ― Details (Name, id, email, etc. ) ― Relation with clients 2. Invoice management in SFDC for clients: i. Type of invoices ii. Automated calculations → Time Sheet: Daily Tasks and Accomplishments 4

Outline 1. Introduction A. Context B. Objectives 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results 4. Conclusion 2. Analysis and Design A. Background research Apatar Open Source Data Integration & ETL[3], an open source data integration : 1. Better synchronization than the native data loader in SFDC 2. Connectivity to MS SQL 2005 and more… 3. Native support of salesforce. com custom objects and custom fields. 4. Easy customization 5. Platform-independent 6. Takes into consideration the SFDC requirements for implementation [4] 5

Outline 1. Introduction A. Context B. Objectives 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results 4. Conclusion 2. Analysis and Design Windows Task Scheduler Java Batch Backup File Original File Work. Flow Stored Procedures Objects Task Scheduler Pages Web. Services API Classes 6

Outline 1. Introduction A. Context B. Objectives 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results 2. Analysis and Design 1. Database Architecture Analyzed PRIVACY APPLIED database: ― Industrials data: Name, id, etc. ― Languages and currencies ― Telecommunication: Telephone, Email, etc. ― Data transmission: Request for Offers, etc. ― Activity types: Send/receive between the distributors ― Product information: id, size, etc. ― Product packaging: Group divisions, etc. 4. Conclusion 7

Outline 1. Introduction A. Context B. Objectives 2. Analysis and Design 2. UML diagrams 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results PRIVACY APPLIED 4. Conclusion 8

Outline 1. Introduction A. Context B. Objectives 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results 4. Conclusion 3. Development and Verification 1. Stored procedures 1. EQ_Get. Info 2. EQ_Get. Info. Par. Annee 3. EQ_Get. Vend 2. Project implementation PRIVACY APPLIED Property files Batch files to be triggered Packages to implement UML diagrams External libraries for eq. Library 9

Outline 1. Introduction A. Context B. Objectives 3. Development and Verification Simulation for runner. Help. bat : 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results PRIVACY APPLIED 4. Conclusion 10

Outline 1. Introduction A. Context B. Objectives 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results 4. Conclusion 3. Development and Verification 3. Salesforce. com CRM Customer Relationship Management based on cloud computing Custom objects Custom fields for multiple information Custom pages for representation 11

Outline 1. Introduction A. Context B. Objectives 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results 3. Development and Verification 4. Apatar datamap for synchronizing activities: Clients existing in SFDC XML to Sync. Join on ID Upsert activities data 4. Conclusion 12

Outline 1. Introduction A. Context B. Objectives 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and Verification 1. Simulation for synchronizing activities PRIVACY APPLIED 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results 4. Conclusion Synchronization successful for 1500 activity in 1 min 40 seconds using Web. Services API sending SOAP messages 13

Outline 1. Introduction A. Context B. Objectives 3. Development and Verification 2. Invoice management in Salesforce. com CRM 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Apatar datamap C. Simulation D. Results PRIVACY APPLIED 4. Conclusion 14

Outline 1. Introduction A. Context B. Objectives 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results 3. Development and Verification 3. Verifying results in Salesforce. com CRM Custom Tabs Client details using custom fields Activities list using Invoice management using PRIVACY APPLIED Relateled lookup. APPLIED field PRIVACY APPLIED 4. Conclusion 15

Outline 1. Introduction A. Context B. Objectives 2. Analysis and design A. Background research B. Workflow C. Database D. UML 3. Development and verification A. Implementation B. Datamaps C. Simulation D. Results 4. Conclusion 1. Analyzed the functional requirements 2. Executed and validated the entire workflow life-cycle 3. Developed “in the cloud” using Apex, the #1 on-demand programming language [5] 4. Fulfilled all the objectives Future work 1. Migrate to Professional Edition 2. Use opportunities, modules, googlemaps, … 3. Benefit from all aspects of cloud computing 16

References [1] PRIVACY APPLIED, company, PRIVACY APPLIED [2] Salesforce. com Client Relationship Managmenet, www. salesforce. com [3] Apatar Open Source Data Integration & ETL, www. apatar. com/ [4] Salesforce, Implementation Considerations, www. salesforce. com/us/developer/docs/api/Content/implementa tion_considerations. htm#topic-title_request_metering [5] Apex Code: The World's First On-Demand Programming Language , Salesforce, wiki. developerforce. com/index. php/Apex_Code: _The_World's_Fi rst_On-Demand_Programming_Language 17

Thank you for your attention Feel free to ask any question 18