The Karis group implemented SalesForce document management with mail merge and print features using APIs

About The Karis group

The Karis group provides patient advocacy services to individuals who have exhausted their medical benefits and are now receiving care on a self-pay basis. Our team mediates directly between patients and providers, allowing patients to focus on their health while we focus on solutions for their bills.

Our negotiations generate large numbers of documents and to streamline our processes, we built a custom SalesForce.com solution that generates custom merge templates from our data and sends those documents out via a number of routes including faxing and e-signature.

Requirements Scenario

In the original incarnation of the solution, a server-side copy of Microsoft Word was scripted through COM automation to open a file, merge data and then, either print or save the document. COM automation is not thread-safe when multiple teams members access the application at the same time, so the chances are that Word would freeze and the web application would be in an unrecoverable state until a full server reboots.

Our requirements for the new solution were:

We also had a couple nice to have requirements including:

Solution Implementation

Before we found Aspose, we spent a fair amount of time struggling with RTF documents as a possible alternative to using Word documents. After that effort became bogged down, we took another look at Aspose and took advantage of the free trial. Within hours, we had the library integrated and documents being produced and printed without issue.

During Aspose.Words for .NET integration, we made extensive use of the mail merge features as well as the print system. The online documentation made the entire process very simple and our code ended up substantially easier to maintain and understand, compared to the COM automation solution we had in place before.

Benefits

The old system was less stable but after the integration of Aspose.Words for .NET, we haven’t had any downtime and our documents looked similar as they appeared in Microsoft Word. Our system became more maintainable than it was before and we became less concerned about our ability to handle new documents as they were created.

Conclusion

If we had not found Aspose.Words for .NET, our solution could not have become as robust and easy to maintain as it is now. We were hesitant at first due to price, but we already have covered it up with increased productivity on the development side and decreased downtime for our users. Any developers, who are interested to programmatically work with Word documents we strongly recommend them to first try using Aspose.Words for .NET.

Screenshots

Dialog to Print, Preview, Download file
Image 1:- Screen to select the document for Print, Preview, Download or Fax

The user can select to merge a template from a bill and then chooses from a number of pre-built documents and can choose to immediately send that to a printer, view it in HTML, download it for local editing, fax it via RightFax or email it via EchoSign.

Resultant Word document preview
Image 2:- Resultant MS Word document preview

The completed document has all the relevant data from our SalesForce.com database in it and is ready for immediate release to a provider or patient.