Technical FAQs

Where we came from

In July 2015, Accusoft’s SaaS Applications team was tasked with integrating the recently acquired edocr application with our existing Prizm Share community for publishing and sharing documents. While this integration offers numerous challenges with data migration, feature parity, and cohesive branding, we are going to focus on the architectural changes that resulted from the project.

Both projects were initially built as LAMP applications—edocr on Drupal 5 and Prizm Share being built in-house by a fledgling apps development team. Throughout their independent evolutions, they each had the expected increase in features and correlated increase in code base size and technical debt. The decision to merge the two products under a single brand and code base meant choosing a target platform.

Initially, we considered two options:

Migrate Prizm Share data to the existing edocr platform

With edocr being the dominant service for traffic between the two, it made more sense to merge on that base when looked at from a customer-centric perspective. However, edocr was running on a very dated Drupal 5 and in need of an approach that could be supported well into the future. Along these lines, we also considered adopting the Drupal platform and then going through the upgrade process from 5 to the current release, 8. Tests of these upgrades did not have good results, however, as numerous plugins and custom modules in edocr were not available or supported in the latest version.

Migrate edocr data to the existing Prizm Share platform 

With the edocr application being based on the very outdated Drupal 5 platform, the primary contender was to move the application to our existing PHP Prizm Share code base and extend the features that we didn’t currently support in order to serve the existing customers of both products. The problem with this was that the code for Prizm Share was already starting to show signs of rigidity based on a lack of foresight on the initial architecture decisions. New features were increasingly difficult to work in with the existing framework and the team had been looking to move to something more modular.

Our Decision

What the team eventually decided on, however, was a complete overhaul of the whole system, targeting the existing feature sets of both products along with a specific list of MVP requirements for our new consumer document platform.

To ensure flexibility in the future and to keep a positive connotation on the word legacy, we decided to adopt a microservice architecture built on a lightweight application framework we developed in Node. This would handle configuration and dependency management for each of our services. By separating out our functionality into independently managed components and updating our build and deployment system to deploy as docker containers, the team was able to reduce friction with code changes, improve code testability, and drastically reduce the time from commit to production.

Read on in the coming weeks for details on our migration, including failures, successes, and lessons learned.

KnowledgeLake had long utilized an in-house viewing solution that allowed customers to view documents within the platform. Although this legacy viewer had gone through many iterations over the years, it was deployed as part of an on-prem solution. When KnowledgeLake transitioned its on-premise products to a cloud-based solution, they decided to evaluate Accusoft’s PrizmDoc as an alternative to their in-house viewing solution.

Long resistant to technological change, the insurance industry has made great strides over the last decade to implement innovative InsurTech solutions that upend longstanding market practices. As insurance providers explore new strategies for attracting a new generation of customers, they continue to rely heavily upon InsurTech developers to build the solutions that help them expand their customer base.

The Insurance Industry’s “Protection Gap”

Today’s insurance companies are offering more products and services than ever before, and yet at the same time, most people are carrying less insurance they need to protect themselves from risk. This “protection gap” is at least partially the result of large amounts of friction when it comes to purchasing insurance. People are either choosing to not buy insurance products, or they don’t know what options are available to them.

Part of this problem is the result of outdated models many organizations use to sell insurance. There’s an old adage that insurance is something that is “sold” rather than something that is “bought.” In this model, customers are expected to interact with an insurance agent who actively sells them a particular coverage.

Unfortunately, this model is becoming less and less effective in an increasingly digitized world, especially when it comes to younger generations of customers who expect the same level of frictionless convenience from insurers that they now get from many financial services (especially those powered by FinTech solutions).

What Is Embedded Insurance?

One potential solution to this challenge is a new strategy known as embedded insurance. This approach first identifies purchases or situations where insurance is required or would present clear added value. Some examples could include the purchase of an automobile, a vacation package, or even a potentially hazardous activity like skiing. An appropriately risk-adjusted insurance package is then offered to customers at the point of sale, or “embedded” within the customer experience.

There are tremendous advantages to this strategy. In the first place, it allows insurers to offer their products to customers who need them most at the precise point when they need them. Rather than having to go through the laborious process of contacting an insurance agent to get a quote for a new automotive policy after someone buys a new car, they can simply update their plan or add insurance services at the same time they’re purchasing the car itself. Customers are less likely to put off getting insurance (and then often forgetting to do so later), and the insurance provider has an opportunity to offer services to the people most likely to purchase them. For the provider, it’s a much more efficient approach than relying on outdated cold calling techniques to sell policies that may or may not meet the current needs of a customer.

Technical Challenges of Embedded Insurance

In order to embed insurance offerings effectively, however, providers first need to overcome a few technology challenges. From improved data capture tools that allow them to conduct faster, more customized underwriting to integrations that connect their applications to partner ecosystems, a new generation of InsurTech solutions will be needed to remake insurance business models.

Better Data Capture

Having accurate information is essential to insurance underwriting. This is even more important when it comes to embedded insurance because rates need to be calculated quickly so they can be provided along with other purchases. In many cases, form information may need to be processed quickly to obtain key data on the customer and the details of their purchase. When InsurTech applications are equipped with automated forms processing tools, they can quickly extract key information and use it to make faster, more data-driven decisions.

Versatile Viewing Capabilities

Whether an InsurTech application stands on its own or is integrated into another service offering, customers will often need to view information about their policy options in order to make an informed decision. On the firm’s end, insurance agents may need to review application details or bring up other resources to review when finalizing rates. By building viewing capabilities into their InsurTech applications with integrations like an HTML5 viewer, developers can ensure that their customers will never be caught depending upon external platforms for document viewing or sharing.

Expanded Contract Automation

Many insurance policies still require some form of contract, even if digital signature technology allows these forms to exist entirely in electronic format. Having the ability to rapidly assemble a contract as part of an embedded insurance solution can further enhance the streamlined customer experience. InsurTech developers can integrate automated document assembly tools to rapidly build contracts from pre-existing templates and quickly fill in the necessary details or add additional clauses.

Accusoft InsurTech Solutions for Embedded Insurance

Accusoft’s collection of SDK and API integrations give InsurTech developers the tools they need to enhance the flexibility of their applications. Our software solutions provide proven, market-ready viewing and processing features so development teams can keep their focus on refining their platform’s innovative core functionality. Whether it’s the versatile forms processing features of FormSuite, the powerful HTML5 viewing capabilities of PrizmDoc Viewer, or the automated document assembly tools of PrizmDoc Editor, Accusoft integrations can help InsurTech developers get their applications to market faster and explore the possibilities of embedded insurance.

We’ve been working hard to design software integrations that meet the needs of the insurance industry and InsurTech developers. Download our InsurTech solutions fact sheet to see how our constantly evolving family of SDKs and APIs can improve your application’s capabilities and performance.

Here at Accusoft, we’re always looking for new ways of connecting people with progress to improve productivity and drive innovation. It’s why we put so much work into our standards-based APIs and SDKs. We understand that developers need mature integrations that are ready to enhance their applications from day one and will be supported by extensive, accurate documentation. From the onset of 2020, we had a strategy in place to help us focus on making it easier for our customers to solve their business problems.

And then, well, 2020 happened…

As this challenging year finally comes to a close, we wanted to take a look back at how we adapted to stay focused on our enduring mission to deliver better products and services to our customers.

2020 Customer Advisory Board Meetings

Since most of our products are delivered through APIs and SDKs, we often encounter situations where our customers and partners independently purchase, download, and extend applications with minimal interaction. Historically, this made it difficult to gain insight into how our clients utilized many of our solutions and what features they would like to see from them in the future.

That’s why we hosted our first Board of Connectors (BoC) meeting in 2019 to bring customers and product managers together in an ongoing dialogue about business needs and product strategy. These meetings also had the benefit of allowing our customers to build relationships with our internal teams, provide feedback on product features, share their business challenges, and discuss key development trends impacting their respective industries.

We had the good fortune to hold our first BoC meeting in-person before the COVID-19 pandemic forced us to adopt rigorous social distance and work-from-home protocols for the safety of our employees and customers. Our second meeting took place in virtual format later in the year, which allowed us to learn first-hand how our customers were dealing with pandemic pressures and how we could adjust our product strategies to meet their rapidly shifting needs.

An Eventful 2020 for PrizmDoc Viewer

One of the principal beneficiaries of these meetings was our popular PrizmDoc Viewer solution. As a best-in-class HTML5 viewer, PrizmDoc Viewer was already a powerful and versatile viewing integration capable of enhancing a variety of applications. But if there’s one thing we’ve learned over the years, it’s that there’s always room for improvement.

That’s why we made it a point of emphasis to implement the top five requests we heard at the first BoC meeting of 2020. Despite all the disruption of COVID-19, we’re incredibly pleased that we were able to deliver on every one of these requests. We also rolled out a host of new product features and continued to optimize PrizmDoc Viewer for improved performance.

Here’s a quick rundown of the five big PrizmDoc Viewer upgrades of 2020:

v.13.11: February 2020 

For the first release of the year, we focused on improving performance when viewing large raster images. We also wanted to make PrizmDoc Viewer easier to install and upgrade.

What we did:

• Improved the PrizmDoc Viewer Raster Conversion Service to significantly reduce memory consumption and reduce the time it takes to generate raster tiles when viewing large image files.
• In addition to our traditional installers for Windows and Linux, we released new PrizmDoc Server and PrizmDoc Application Services (PAS) Docker images for production deployments, making the setting up of the PrizmDoc Viewer backend dramatically easier.
• Released a new .NET SDK for PrizmDoc Server – for .NET developers doing backend document processing with PrizmDoc Server this wrapper around the PrizmDoc Server REST APIs makes it easy to use PrizmDoc Server functionality in .NET.
• Upgraded the PrizmDoc Server installer to allow for in-place upgrades so users no longer need to uninstall the previous version before installing the newest version.

v.13.12: April 2020 

For the second release of the year, we expanded our use of Docker technology to make PrizmDoc Viewer easier to evaluate. We also worked to improve the performance and stability of PrizmDoc Server.

What we did:

• Released a new evaluation Docker image that provides a demo web application to explore the viewer and its features, and start a complete PrizmDoc Viewer backend to begin using for local development.
• Updated online help with a new look and feel for easier navigation. Added a new getting started topic for streamlined evaluation, and initial integration topic for an easy transition after evaluation. 
• Improved performance and stability of PrizmDoc Server when viewing complex PDF documents.

v.13.13: June 2020 

This release saw the rollout of a new redaction feature along with myriad performance improvements.

What we did:

• Provided support for multiple redaction reasons via our client API so users can apply more than one reason, selected from a customizable list, to any redaction reason. Reasons appear on top of the black box of redacted content and can be burned into a downloadable PDF along with the rest of the redacted content. Developers can also import a pre-built set of redaction reasons from an existing JSON file for streamlined end-user application.
• Improved conversion times and memory consumption when viewing multi-page DWF documents.
• Improved performance when retrieving revision data and scrolling through results when comparing two versions of a Word document.

v.13.14: September 2020

The fall release saw new support for viewing email attachments, more redaction features, and continued improvements to the upgrade process.

What we did:

• Added support for opening email attachments in the same viewer window where the original email is being viewed. Improved the client UI to show email attachments in a compact dropdown menu.
• Added server-side support for multiple redaction reasons using the Redaction Creators API.
• Released the ability to draft redactions without obscuring the content, allowing users to produce PDF documents with transparent redactions that display the document content underneath the redaction rectangles.
• Added the ability to retain configuration setting when upgrading PrizmDoc Server and PAS.

v.13.1: December 2020

The final update of 2020 focused primarily on reducing resource strain, but also saw the release of new sample code and added new Java Virtual Machine (JVM) controls.

What we did:

• Optimized log entries for the PrizmDoc PDF processing service to dramatically reduce log file size and storage needs.
• Enhanced PrizmDoc service health detection to automatically return to healthy status as soon as a failed backend service returns to normal operation, eliminating a potential need to restart PrizmDoc Server.
• Released two new Angular samples on GitHub: a .NET backend sample and a Java backend sample.
• Added new parameters in central configuration that provide controls for JVM settings when starting PrizmDoc Server Java-based services.

What’s Next for 2021?

Following our virtual BoC meeting in Q3, our product teams have been hard at work developing new features for the upcoming year that will continue to meet the diverse use case needs of our clients’ applications. We want to build on our successes in 2020 when it comes to engaging our customers and using their direct feedback to make beneficial and lasting improvements to our family of SDK and API solutions.

If you’re currently using our products and would like to participate in one of our upcoming BoC meetings for 2021 to submit feedback or learn about future releases, contact us today! We’re looking forward to working with you in the new year!

Few organizations will view the final weeks of 2020 as a bittersweet moment. In addition to the staggering human toll inflicted by the COVID-19 pandemic, entire industries saw longstanding business models upended, forcing companies to completely rethink their relationships with employees, vendors, and customers. The financial services industry was no exception, and 2020 saw FinTech becoming more important than ever as firms rushed to embrace digital transformation in response to the ongoing crisis. Many of these trends appear poised to continue well into 2021 and beyond. 

FinTech Defined

FinTech is short for “financial technology,” but the term itself is applied quite broadly throughout the financial services industry. It can be used to refer to a new generation of non-traditional startup companies focused on building digital tools that allow people to manage their finances in new ways that disrupt established industry practices. The term is also sometimes used to describe the technology itself, however, especially since established financial organizations are investing heavily in innovative applications and services of their own.

FinTech Trends for 2021

Although 2020 is sure to be remembered as a year of unprecedented disruption, 2021 might well come to be known as a year of remarkable adaptation and transformation. Now that organizations have developed innovative digital strategies to navigate a more volatile economic landscape, they must now take up the challenge of putting those plans into practice.

FinTech developers need to keep an eye on these trends as they build new applications and services in order to provide the functionality and performance demanded by the financial industry. Many established firms will be taking a long look at their infrastructure and technology solutions to assess whether or not their current systems are up to the challenge of digital transformation. If their existing platforms fall short, they will need to either seek out new FinTech products with more robust feature sets or explore options for integrating new capabilities into their legacy software.

Top 5 FinTech Trends to Watch in 2021

1. Customer-Centric Applications

The proliferation of FinTech solutions has brought customers to the forefront of every financial organization’s thoughts. Where the financial industry once designed processes and applications to suit their own needs, today they must focus on delivering a high-quality customer experience if they want to remain competitive in a crowded marketplace. The process often begins with reducing friction wherever possible to help end-users get the products and services they need faster. With customers increasingly interacting with the financial industry across multiple channels, FinTech developers must build solutions that strengthen those connections and expand their potential.

Eliminating manual processes, cutting down on external software dependencies, and automating routine tasks will continue to be a major point of emphasis for FinTech applications. Customers no longer have the patience to repeatedly fill out lengthy forms or go through the frustrating process of downloading, printing, signing, and scanning documents. By building document viewing, file conversion, and data capture capabilities into their applications, FinTech developers can provide firms with a unified digital solution that addresses multiple needs and streamlines their customer experience.

2. Digital-First Collaboration

According to an IDG study on the enduring business impacts of the COVID 19 pandemic, about 40% of employees are expected to be working remotely on a semi-permanent basis as of January 2021. That means financial organizations will continue to need digital tools in place to provide secure access to files and facilitate collaboration. Physical documents must first be converted into a variety of digital formats with high levels of accuracy and then made available to remote users without compromising data integrity or creating confusion over version history. 

Without a dedicated solution on hand for viewing, editing, and managing documents, users are forced to resort to a variety of ad hoc workarounds and third party software solutions that can quickly compromise data security and increase the likelihood of errors. By integrating those features into their FinTech applications, developers can help firms keep all of their documents and files safely within a secure infrastructure while still making them available through easy-to-use web-based API tools.

3. Big Data Management

Financial organizations continue to collect huge amounts of data in the course of their business. Some of this data is unstructured and must be processed using powerful analytics tools to identify important trends and potential risks that can help firms make better strategic decisions. But they also gather a great deal of structured data as well, typically from structured forms like loan applications, tax documents, and bank statements. Managing all of this information more efficiently will be an important goal for 2021 because having good data insights is essential for identifying opportunities, optimizing products and services, and automating essential services.

FinTech developers can help improve data processing by building applications capable of extracting information quickly and accurately. Financial data algorithms are quite good at identifying different types of data and sorting it into the proper place for analysis, but they’re often slowed down by documents that are damaged or difficult to read. Thanks to software integrations that provide robust image cleanup, document alignment, and form recognition tools, FinTech applications can ensure that firms are starting with the cleanest possible source data when extracting information for processing.

4. Pandemic Proofing

Although there are several promising COVID-19 vaccines on the horizon, challenges with supply and distribution will keep most companies operating under the same social distancing and remote workplace guidelines they put in place in 2020 for much of the year. Even if restrictions are lifted earlier than expected, the risk-averse financial industry will continue to think about how to avoid similar disruptions by implementing paperless processes and electronic data capture options. Just as retailers and manufacturers are rethinking their supply chain infrastructure, financial services companies must reassess their FinTech applications in light of recent challenges.

Developers can help the financial industry better “pandemic proof” their processes by integrating better document viewing, file conversion, and data capture tools into their software solutions. Not only can they automate traditionally time-consuming (and error-prone) manual data entry tasks, but they can also build in additional functionality to auto-generate data for new contracts and allow people to sign documents digitally to eliminate the need for face-to-face meetings. 

5. Banking Partnerships

Banks and other traditional financial institutions are increasingly partnering with FinTech startups to reach new customers and engage with existing clients over new channels. As Deloitte noted in a recent study, the pandemic has removed many of the obstacles to digital transformation in the financial industry and forced many established firms to pour tremendous resources into their tools and infrastructure. But as banks engage with innovative startups, they will need to find ways to integrate operations and data quickly to remain competitive and roll out new services successfully.

That integration process will be easier if they have flexible software solutions in place that can navigate multiple file types, perform cleanup and conversion, and extract essential data quickly and accurately. Whether they’re building that functionality into entirely new applications or integrating features into existing legacy systems, FinTech developers will play a key role in helping financial organizations accelerate their merger and partnership timetables so they can begin reaping the benefits more quickly. 

Solving Your FinTech Challenges with Accusoft

Accusoft’s collection of RESTful APIs and SDKs provide FinTech developers with the tools they need to build comprehensive content processing, conversion, and automation solutions into software applications. Whether you’re using PrizmDoc Suite to view, edit, and convert documents directly inside their financial applications, capturing valuable financial data from various form types with FormSuite for Structured Forms, or embedding powerful image cleanup, OCR, and annotation tools into your application with ImageGear, our family of software integrations allow you to add the functionality your FinTech solutions need to meet the challenges of 2021 and beyond.

To learn more about how our software tools can enhance your FinTech applications, talk to one of our integration experts today.

TAMPA, Fla. – On September 22, 2020, Accusoft announced its latest SDK, ImageGear PDF. This integration enables developers to add a variety of PDF functionalities into an application.

“We are proud to add ImageGear PDF as the latest addition to our product portfolio,” says Jack Berlin, CEO of Accusoft. “We recognized a need in the market for a more robust PDF solution that developers could use to enhance their products. Using our proprietary technology, I knew we could bridge that gap.”

ImageGear PDF gives end-users the ability to merge multiple PDFs, split a PDF into multiple PDFs, rearrange pages within a PDF, add pages or remove pages in a PDF, and more. The SDK adds programmatic annotation capabilities as well as compression, signature, comparison, and data capture.

“ImageGear PDF is a great tool for developers looking to enhance their application,” says Mark Hansen, Sr. Product Manager of SDKs. “Accusoft has a variety of different PDF solutions, but we wanted to add a more robust SDK that solves PDF pain points more efficiently.”

ImageGear PDF is available with an optical character recognition (OCR) add-on feature, which programmers can use to search for specific characters within a document, highlight different sections, and markup the output for easier viewing and collaboration. To learn more about ImageGear PDF, please visit our website at accusoft.com/products/imagegear-collection/imagegear-pdf/.

About Accusoft:

Founded in 1991, Accusoft is a software development company specializing in content processing, conversion, and automation solutions. From out-of-the-box and configurable applications to APIs built for developers, Accusoft software enables users to solve their most complex workflow challenges and gain insights from content in any format, on any device. Backed by 40 patents, the company’s flagship products, including OnTask, PrizmDoc™ Viewer, and ImageGear, are designed to improve productivity, provide actionable data, and deliver results that matter. The Accusoft team is dedicated to continuous innovation through customer-centric product development, new version release, and a passion for understanding industry trends that drive consumer demand. Visit us at www.accusoft.com.