1. LEBANON-FRANCE © 2011LEBANON-FRANCE © 2011 1 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

2. 1.Introduction 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

3. A. Context of the internship 1.PRIVACY APPLIED 2.Functional requirements 3 The tech division of PRIVACY APPLIED : 1.Leader in e-catalogue & B2B solutions[1] 2.Offers solutions for data interchanges 3.Certified by GS1 standards Reduce duplication Data analysis Web Application 1. PRIVACY APPLIED 2.PRIVACY APPLIED 3.PRIVACY APPLIED Cloud-based CRM[2] 1. Structured data 2. Report management 3. High customization 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 PRIVACY APPLIED

4. 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 4 → Time Sheet: Daily Tasks and Accomplishments 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

5. A.Background research 5 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] 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

6. WorkFlow WorkFlow Java Batch 6 Stored Procedures Pages Windows Task Scheduler Backup File Original File Task Scheduler WebServices API Objects Classes 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

7. 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. 7 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

8. 2.UML diagrams 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 PRIVACY APPLIED

9. 1.Stored procedures 2.Project implementation 9 1. EQ_GetInfo 2. EQ_GetInfoParAnnee 3. EQ_GetVend Packages to implement UML diagrams Property files External libraries for eqLibrary Batch files to be triggered 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 PRIVACY APPLIED

10. 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 Simulation for runnerHelp.bat : PRIVACY APPLIED

11. 3. Salesforce.com CRM 11 Customer Relationship Management based on cloud computing  Custom objects  Custom fields for multiple information  Custom pages for representation 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

12. 12 4. Apatar datamap for synchronizing activities: Clients existing in SFDC XML to Sync. Join on ID Upsert activities data 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

13. 1. Simulation for synchronizing activities 13 Synchronization successful for 1500 activity in 1 min 40 seconds using WebServices API sending SOAP messages 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 PRIVACY APPLIED

14. 14 2. Invoice management in Salesforce.com CRM 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.Apatar datamap C.Simulation D.Results 4.Conclusion PRIVACY APPLIED

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 3. Verifying results in Salesforce.com CRM 15 Custom Tabs Client details using custom fields Activities list using Invoice management using Relateled lookup field PRIVACY APPLIED

16. 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 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

17. [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

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