Extending Workflow Solutions using SmartIntegrator (SI) Muthu Arumugham, Vice President, Technology Bryan Eshelbrenner, Product Manager
Agenda Time Topic Presenter 3:45 SmartIntegrator Overview Muthu Arumugham 3:55 Real Solutions: Ebix CRM Bryan Eshelbrenner 4:10 Real Solutions: M Financial Curt Rynties 4:25 Real Solutions: First Heartland Capital (FHC) Scott Hoff 4:40 Brainstorm/Q&A Muthu Arumugham
SmartIntegrator in a nutshell SI is a well defined interface to communicate with SmartOffice Exposes underlying relational data in object model Handles the Object to Relational (O-R) Mapping Reuses the business objects of SmartOffice In essence, it is the published and preferred Data Access Layer to SmartOffice! SmartIntegrator (SI) is a proven tool to enhance SmartOffice Ebix uses SI extensively for dozens of out of box integrations Continues to pour considerable R&D $$$ to enhance SI Many of our customers use SI M Financial, MetLife, First Heartland Capital, HSBC, NFP, etc.
Where can I Use SI? SmartOffice UI and Workflows Simplify, Replace, Build a new one Building custom UIs for large advisor to satisfy their unique requirements Launch applications from within SmartOffice and passing contexts Needs Analysis, Illustrations, Fill-able Forms, Web based policy admin systems, Deep Link integrations between systems Context centric application launch Contact, Household, Advisor, Policy, Accounts, Positions Data processing Export/Import, Background/Foreground, Just in time update
How can we help you? Training Onsite or in Pasadena Consulting Development Do it yourself (DIY) Hire Ebix Hire 3 rd party
Ebix CRM Solutions Demo
Real Solutions Demo: Ebix CRM Investigo: Bulk data feed to SmartOffice LaserApp: linking windows app to SmartOffice MGP: linking Web App to SmartOffice Albridge AppLink deep link/sso Google Maps some cool integration, concepts
M Financial Solutions Demo
M Lightning Dashboard Reports Policy Comparison Tool Real Solutions Demo: M Financial
First Heartland Capital (FHC) Solutions Demo
Phone Call Log
Phone Call Log The Challenge Standard SmartOffice Work Flow Requires Too Many Screens to Log a Phone Call Screens take time to load and slow down staff Staff cannot Take Notes On The Activity While the Timer is Running
SmartOffice Work Flow Create Activity Note Load Time: 1.890 Enter Data and hit Save and Close
SmartOffice Work Flow Confirm that I want to Proceed since I created the activity in the past Select the appropriate phone number and hit dial.
SmartOffice Work Flow The Timer Starts but I have No Where to Take Notes I Open Up a Copy of Notepad and Type My Phone Call Notes.
After finishing the call, I copy and paste my notes from notepad into the Outcome Notes. SmartOffice Work Flow
Staff go to a Single Page to Log Phone Calls Phone Call Log
The user types part of the name to get a drop down menu. Phone Call Log
Phone Call Log The Phone Number is then displayed for the user They can then enter notes as they are created
Phone Call Log The activity is created in SmartOffice and marked done. It is then available in the Activity Log for all to see
Ticketing System
The Need for a Ticketing System A growing company means a growing number of agents and staff to support. A growing technical team, requires a more efficient means for collaboration, organization and prioritization.
Requirements for Ticketing System Requirements The system should be open source (read free ) System should integrate with SmartOffice System should allow for multiple users System should allow for prioritization using by the severity of an issue
Why SmartIntegrator? While there are many open source solutions available, we would have to dig into their code and write the SmartOffice Integration
Why Not Use Standard SmartOffice? Tech Support Staff feels program is too bulky and that too much time is wasted waiting on screen loads. Solution needs to be fast and not give the impression that is slowing down the team.
Why not Use a SmartOffice Ticketing Solution? 1. At the time we didn t know one existed 2. Once developed, a home grown ticketing system does not produce any ongoing expense or subscription fees 3. Workflow can be optimized for our team s needs
Our Ticketing System
Building The Ticketing System Tickets We created an Activity Type of Ticket Activities are linked to existing users in SmartOffice Authentication We leverage our existing SmartOffice Logins to authenticate into the system
Building The Ticketing System Licenses Needed Since we are operating off of core functionality, no additional modules are needed.
The Interface Programming Languages Used SmartIntegrator Terms PHP Used to send and receive SmartIntegrator XML Javascript Used to Parse XML and Generate content on the fly Heavy leveraging on the jquery library Interface Control generated with jquery UI (User Interface)
Our Ticketing System Indicates Number of Tickets Activity Notes Subject of Ticket Contact Name Contact Phone Primary Number
Our Ticketing System Indicates Number of Tickets Activity Notes Subject of Ticket Contact Name Contact Phone Primary Number
Secure & Automated Data Transmittal
Secure & Automated Data Transmittal Background Information One of our industry partners works with multiple BGAs All of the other BGA Partners are operating in agency works. Partner wants the pending case information in their database Partner is not satisfied with SmartOffice Advisor View
Brainstorming Phase Leverage SmartOffices ability to automatically send dynamic reports Problem: We had to choose between PDF or CSV format PDF files are not easily machine readable While CSV files are flat and machine readable the partner did not want them because many fields might contain commas and break the script. Example: Hoff, Scott Would be parsed as two separate columns
Brainstorming Phase Create the entire export with SmartIntegrator Downside: Requires a working knowledge of the SmartOffice Data Objects Loss of Dynamic Report s quick development Time
Brainstorming Phase Leverage SmartOffices ability to automatically send dynamic reports Problem: We had to choose between PDF or CSV format PDF files are not easily machine readable While CSV files are flat and machine readable the partner did not want them because many fields might contain commas and break the script. Example: Hoff, Scott Would be parsed as two separate columns
Our Solution Use dynamic reports to create the report Call the Report from SmartIntegrator and send it as machine readable XML
The Work Flow Script is run Daily at 10:00 P.M.
Brainstorm Topics 1. How do you explain and sell SI to your internal customers? 2. What development challenges have you faced that are unique to SI? 3. If you were not constrained with development resources what would you do with SI? 4. What would you add next to the SI toolset? 5. SmartOffice Developer Community (SDC) Are we ready for innovations from freelance world. What are your security concerns? 6. How can Ebix help you Training, Sample Codes, Brainstorm sessions, SDC
Extending Workflow Solutions using SmartIntegrator (SI) Muthu Arumugham, Vice President, Technology Bryan Eshelbrenner, Product Manager