Technical FAQs

Question

Are there any specific applications or folders which should be excluded in order for PrizmDoc to work on a system with antivirus software?

Answer

As a suggestion, the first place to start would be your antivirus logs to ensure there are no entries specific to the following services:

  • conhost.exe
  • node.exe
  • policyhost.exe
  • PrizmApplicationServices.exe
  • wmiprvse.exe

If there are, you can exclude those files or the following folders where PrizmDoc is installed by default. If you modified the folder name for PrizmDoc, ensure to include that name.

  • C:\Prizm
  • C:\ProgramData\Accusoft

Please consult your antivirus documentation for instructions on how to add exclusions.

 

For over 30 years, Accusoft has developed groundbreaking digital imaging technology that has revolutionized the way applications manage and process content. From high-resolution image compression and file format conversion to data extraction and barcode recognition, Accusoft technology can be found in some of the most sophisticated and widely used software in the world. The company’s enduring success is built upon a combination of patented engineering innovations and key strategic acquisitions.

Humble Beginnings and Early Success

The origins of Accusoft go back to the late 1980s, when founder and CEO Jack Berlin got a hands-on look at one of the first digital cameras at a trade show and developed an interest in the nascent technology.

“I just fell in love with it and wanted to get involved in digital imaging,” he recalls. That desire led Berlin to found Pegasus Imaging Corporation in September of 1991. “It started as a hobby, but it became serious pretty fast.”

The company quickly found its niche selling innovative image compression and decompression technology that software developers could incorporate into their applications. Over the next decade, Pegasus Imaging made a name for itself thanks to advancements in lossy and lossless JPEG compression that were adopted by leading photo imaging companies such as Kodak, Canon, Nikon, Fujifilm, and Konica Minolta.

In 1998, Pegasus Imaging expanded into medical imaging with the groundbreaking PICTools Medical SDK. The company quickly made a splash in the market by solving the infamous “DICOM bug” associated with the Cornell codec, an open-source codec frequently used for lossless JPEG compression. Pegasus Imaging’s engineers were able to identify why the codec rendered some images unreadable after decompression and provide a means of both compressing images safely and decompressing files once thought to be corrupted beyond repair. That ability to quickly solve imaging problems helped make PICTools Medical a major success with some of the world’s largest medical technology companies, including GE Healthcare, McKesson, Philips Medical Systems, Siemens Medical Solutions, and Toshiba.

Evolution and Expansion

Although Pegasus Imaging enjoyed a great deal of success in its first decade, Berlin knew the company needed to grow if it was going to retain a competitive edge in the 21st century.

“The challenge with the technology business is you have to improve it or lose it,” he says. “You don’t get to sell the same product ten years later. You have to continue to innovate.”

The early 2000s saw Pegasus Imaging embark on a series of acquisitions that helped expand its business and continue pushing the boundaries of innovating in digital imaging. Each merger involved a strategic consideration of how it would position the company to evolve to meet the complex challenges of the future.

“People typically want to buy growth, but we look at it differently,” Berlin says. “We’re a big believer that the reason to buy companies is their customers, their products, and their people. Products are worth nothing without their people.”

In 2004, Pegasus Imaging acquired TMSSequoia, which had developed the most sophisticated structured forms processing and document image cleanup technology in the world. The people behind that technology, however, proved even more valuable to the growing company, contributing to the development of several proprietary innovations over the years that followed. Their ongoing contributions can be seen in products like FormSuite, which remains an industry leader in forms processing technology.

The TMSSequoia acquisition, along with the development of its lightning fast ImagXpress toolkit, set Pegasus Imaging on the path to becoming a much bigger player in the document imaging market. Its next major acquisition came in 2008 with the purchase of AccuSoft, a Massachusetts-based imaging software company best known for its powerful ImageGear SDK. No sooner had the deal closed, then Pegasus Imaging expanded once again by acquiring the UK-based Tasman Software, which had developed groundbreaking barcode recognition technology that would eventually be incorporated into the popular Barcode Xpress SDK product.

Over the course of just a few years, Pegasus Imaging had greatly expanded its portfolio of document imaging and processing solutions by strategically identifying the technology and engineering talent that could fuel the company’s growth. To Berlin, making the most of those acquisition opportunities are critical to sustained success in a competitive industry:

“It’s grow or die. We’re up against larger and larger competitors. Consolidation gives you market share and economies of scale. If profitability goes up, you can invest in new product development, marketing, and growth.”

In 2009, Pegasus Imaging changed its name to Accusoft Pegasus to rebrand the company as a key player to watch in the document imaging and processing industry.

Integration and Innovation

The acquisition of AccuSoft expanded the company’s market share and expertise, but it also created a new challenge for the engineering team. AccuSoft’s ImageGear SDK frequently competed directly with Pegasus Imaging’s ImagXpress. While there was no question that the newly rebranded Accusoft Pegasus would continue to support customers using these products, strategic decisions had to be made about their respective futures.

As the team evaluated each product, it quickly became clear they were the result of very different approaches to software development.

“ImagXpress was much easier to use, but it didn’t have all the platforms and features of ImageGear,” Berlin recalls. “Their idea was to throw everything but the kitchen sink into the product, and if somebody complained, fix it. Pegasus wanted to make everything perfect and add features very slowly. I think there was a happy medium there somewhere.”

ImageGear’s ability to support multiple platforms and the rapid development of modern compilers eventually made it a more attractive SDK for developers, but the Accusoft Pegasus team incorporated the best features of ImagXpress into it to make ImageGear an even better product. Throughout the integration, the company put new processes into place to strike a balance between speed and perfection. Product management structures were also established to improve feedback loops, lay down feature roadmaps, and keep to development timelines without compromising quality.

All of these lessons would prove invaluable when Accusoft Pegasus acquired Adeptol in 2011 and added the company’s AJAX Document Viewer to its portfolio. While Adeptol’s browser-based viewing technology was undoubtedly innovative and correctly predicted what future web applications would require from viewing integrations, the product itself was Flash-based. In addition to being a proprietary technology, Flash contained multiple security vulnerabilities and was already on the decline by 2011.

The Accusoft Pegasus team got to work rebuilding the viewer using HTML5, making it much easier for developers to incorporate viewing features into web-based applications. As the new product took shape, it also allowed the company to expand into the growing market for cloud-based API integration products. Released as Prizm Content Connect in 2012, the HTML5 viewer would be rebranded in 2016 as PrizmDoc.

30 Years of Growth and Innovation

In 2012, Accusoft Pegasus rebranded once again to become Accusoft. Today, the company remains a pillar of the tech community in Tampa, FL even as it strives to expand its business globally. In 2021, Accusoft celebrated its 30th anniversary, a significant milestone for a privately held, employee-owned corporation that began as a hobby.

For Berlin, those humble origins and the long journey to success are what make a company like Accusoft special.

“It’s not just dollars and cents, but a sense of pride and competitiveness,” he says. “It stops being about money at some decimal point. It’s about the people and the legacy and seeing what you can do. We give back a lot to our community. I really enjoy that. We participate in our community, both in tech forums and charity drives and work days. If we cease being Accusoft or cease being Accusoft in Tampa, FL, that’s gone.”

Accusoft and Snowbound Join Forces

That same sense of pride and passion was shared by Simon Wieczner, President, CEO, and co-founder of Snowbound Software. Established in 1996, Snowbound first made a name for itself in the document imaging market with the RasterMaster conversion and imaging SDK. RasterMaster supports hundreds of formats and uses proprietary technology to quickly convert, archive, and display files in high resolution without loss of fidelity.

As two of the leading innovators in document imaging integrations, Snowbound and Accusoft routinely found themselves competing for the same customers over the years. “We were competitors, but not fierce competitors,” Wieczner recalls. “We would mostly run into each other at trade shows and talk about the market.”

Berlin first floated the idea of merging the two companies around 2015, but it wasn’t until much later that acquisition conversations turned serious. With so much money being invested in the tech industry over the previous decade, Snowbound had already received substantial interest from potential buyers, but most of the offers didn’t sit well with Wieczner.

“There’s been a craze over the last few years of growth equity companies looking for SDK companies,” he says. “They were offering good dollars, but without understanding our technology. So there was a little bit of distrust on my part. Some actually wanted to outsource everything and that would totally destroy the company.”

Many potential suitors were primarily interested in incorporating Snowbound’s technology into their own products rather than supporting existing customers and continuing to sell into the market. As conversations with Accusoft continued to progress, Wieczner realized that he’d already found the ideal acquisition partner.

“Accusoft understood the market, what our company did, and how we could fit together,” he says. “That’s why we felt ready to move on together.”

“Both Simon and I are passionate about the success of the company,” Berlin says. “It’s what small business people do. We tend to worship entrepreneurs that get in, build a shell, and get out with a billion dollars, but I don’t know if they’re fulfilled because there’s such fulfillment in seeing what you’ve built accomplish something.”

In late 2022, the companies moved ahead with a deal that saw Accusoft acquire Snowbound. The merger brings Snowbound’s RasterMaster® and VirtualViewer® products into the portfolio of Accusoft solutions:

  • RasterMaster®: A Java-based conversion and imaging SDK, RasterMaster can be incorporated into applications for all computing platforms, including Unix, Linux, Windows, and Mac. The SDK supports hundreds of document types through its proprietary format library and provides a variety of document imaging tools, such as annotations, redactions, OCR, text extraction, and image cleanup.
  • PrizmDoc® for Java, formerly VirtualViewer®: Developed to meet the demanding needs of the banking industry, PrizmDoc® for Java is an HTML5-based viewer that can be easily incorporated into web applications to allow users to view, annotate, and redact documents and images from any platform, anywhere. PrizmDoc® for Java’s library of APIs and out-of-the-box connectors for popular ECM applications (including Alfresco, IBM, and Pegasystems) make it a powerful tool for developers looking to quickly integrate advanced document workflow capabilities.

The Future

In keeping with Accusoft’s long history of strategic acquisitions, the Snowbound merger brings with it an influx of new customers, new technology, and new talent into the Accusoft family. Those resources will help the company to continue investing in innovation to compete in an increasingly high-stakes market.

“It’s a real challenge to incorporate other companies and take that risk, but they’ve done well with it,” Wieczner says. “We were deliberate in selecting an organization with a leadership team and product portfolio that would continue to grow, develop, and nurture what we have built at Snowbound.”

With three decades of experience and success to draw upon, Accusoft is better positioned than ever to meet the evolving needs of its customers and deliver a new generation of document imaging products powered by groundbreaking technology.

Question

How do I get Viewing Packages working in PrizmDoc?

Answer

Viewing Package Full Setup Instructions

We recommend pre-converting documents through a feature called viewing packages and it can be turned on in PAS Configuration.

viewingPackagesdefault: disabled – Enable Pre-Conversion Services and APIs, which allow you to pre-convert documents and cache on-demand document views in PAS, to improve the speed at which documents can be viewed, as well as reduce the processing time in PrizmDoc Server for repeat document views.

Enable Viewing Packages Feature

feature.viewingPackages: enabled

Since viewing packages also use a database you will need to create a database for PAS, configure a database, and run the scripts that are included to create the tables necessary for viewing packages to work.

Configuring Database


Install Microsoft SQL Express

Note 1: If you have Visual Studio installed, you might have to uninstall the recent versions of C++ that are installed before MSSQL Express will successfully install.

Remove Visual Studio C++ Redistributables

Note 2: When installing, use all default install settings except for setting a custom database instance id and set mixed mode authentication so a custom password can be set.

Turn On TCP/IP For Database Instance

Step 1:

step 1 enable tcp/ip

Step 2:

enable tcp/ip

Set Port 1433 for TCP/IP Connection

set port 1433 for tcp/ip connection

Restart SQL Express Instance

Right-click and select "Restart" or double-click and select "Restart".

restart sql express instance

Install Microsoft SQL Management Studio

Install from this downloads page

Connect To Database Instance In Microsoft SQL Management Studio

Connect To Database Instance In Microsoft SQL Management Studio

Create A Database In Microsoft SQL Management Studio

Create A Database In Microsoft SQL Management Studio

PAS Config Database Settings

feature.viewingPackages: "enabled"

database.adapter: "sqlserver"
database.host: "localhost"
database.port: 1433
database.user: "sa"
database.password: "Password1"
database.database: "prizmdb"


# Default timeout for the duration of a viewing session

defaults.viewingSessionTimeout: "20m"

viewingPackagesData.storage: "database"
viewingPackagesProcesses.storage: "database"
viewingSessionsData.storage: "database"
viewingSessionsProcessesMetadata.storage: "database"

viewingPackagesArtifactsMetadata.storage: "database"
viewingPackagesArtifacts.storage: "filesystem"
viewingPackagesArtifacts.path: "%ALLUSERSPROFILE%\\Accusoft\\Prizm\\ViewingPackages"

Create the database tables

Create the database tables

Restart PAS

Restart PAS


Create Viewing Package

viewing-package-creator

Get State of Viewing Package Creator Processing

viewing package creator process

Get Viewing Package Info With Document Id

viewing package info with document id

Create Viewing Session From Viewing Package With Document Id

Create Viewing Session From Viewing Package

View Document In Viewing Package With The Created Viewing Session Id

View Document In Viewing Package With The Created Viewing Session Id

For examples of creating viewing packages, click on the link below to see the various ways of using them:

Viewing Package Creators

Question

With a fully-running PrizmDoc environment (version prior to v10.5), I’m noticing times where the system becomes unresponsive. That is, at some point, it no longer processes requests being made to the backend and I have to restart PrizmDoc in order to alleviate it. What could be causing this?

Answer

Prior to version 10.5, PrizmDoc used ProxyServer as its image processing system. Our Development Team eventually began seeing that the ProxyServer exhibited architectural problems that lead to a multitude of issues, such as unresponsiveness.

Starting in version 10.5, the Development Team created the Prizm Content Connect Imaging Service (PCCIS), which is far more stable.

To resolve this issue we suggest upgrading to the latest revision of PrizmDoc. Please see the product page for more information found here: https://www.accusoft.com/products/prizmdoc/overview/

Explore PrizmDoc Hybrid Viewing

The financial services industry has seen a breathtaking amount of innovation over the last decade thanks to FinTech applications that streamline user experiences and improve operational efficiencies. Many of these solutions incorporate third-party viewing integrations that allow people to view and manage documents, eliminating the need to switch back and forth between different software. 

Implementing specialized viewing technology saves time and resources during the development process so FinTechs can get their products to market faster. By selecting the right integration partner from the beginning, they can put themselves in a position to scale capabilities in the future without suffering unexpected costs or compromising performance. 

Viewing Integrations and the Problem of Scale

FinTech developers often turn to API-based viewing integrations like Accusoft’s PrizmDoc because they provide the tremendous power and flexibility that modern financial services applications require. Whether it’s file conversion, robust annotation, document assembly, or redaction, FinTech software must be able to provide extensive document processing features to meet customer expectations.  

In order to implement those advanced viewing capabilities, the developer usually needs to set up a dedicated server as part of their on-premises infrastructure or in a cloud deployment. One of the biggest advantages of API-based integrations is that customers only have to pay for the processing resources they use, but this can also pose some challenges when it comes to scaling application capacity. 

As FinTech companies expand their services, they need to be able to deliver document viewing capabilities to a larger number of users. If each viewing session requires the server to prepare and render documents for viewing, costs can quickly escalate. As server workloads increase, viewing responsiveness may be affected, resulting in delays and slower performance. 

While some users may still need to use server-based viewing to access more powerful imaging and conversion features, many customers simply need a quick and easy way to view and make minor document alterations. FinTech developers need a versatile solution that can meet both requirements if they want to scale their services smoothly. 

Introducing PrizmDoc Hybrid Viewing

PrizmDoc’s new Hybrid Viewing feature provides FinTech applications the best of both worlds by offloading the document processing workloads required for viewing to client-side devices. Rather than using server resources to convert files into SVG format and render them for display, Hybrid Viewing instead converts files into PDF format and then delivers that document to the end user’s browser for viewing.  

Shifting the bulk of document processing work to client-side devices significantly reduces server workloads, which translates into lower costs for FinTech applications. 

For documents not already in PDF format, the PrizmDoc Hybrid Viewing feature offers new PDF viewing packages that pre-convert documents into PDF for fast, responsive local viewing. 

By reducing the server requirements for rendering files, FinTech providers can easily scale their applications without worrying about additional users increasing their document processing costs. PrizmDoc Hybrid Viewing also eliminates the need for separate viewing solutions implemented to work around server-based viewing, which allows developers to streamline their tech stack and further optimize customer experiences. 

5 Ways Hybrid Viewing Enhances FinTech Applications

PrizmDoc’s Hybrid Viewing feature provides FinTech developers with several important benefits that improve application flexibility and deliver greater value to their customers.  

1. Resource Savings 

Hybrid Viewing minimizes server loads by offloading the bulk of the processing required to view a document to client-side devices. Reducing server requirements translates into lower costs and frees up valuable processing resources for other critical FinTech workloads. 

2. Scalable Viewing 

Shifting the processing work required for viewing to local devices allows FinTech applications to scale their user base with minimal cost. 

3. Enhanced Performance 

Offloading document preparation to the end user’s device improves viewing speed and responsiveness, especially for large documents. 

4. Increased Productivity 

Diverting workloads to client-side devices allows application users to process, view, and manage multiple documents faster. FinTech developers can leverage Hybrid Viewing to provide a better user experience that helps their customers to be more efficient and productive. 

5. Improved Storage Management 

For documents not already in PDF format, Hybrid Viewing can utilize PDF-based viewing packages that are significantly smaller than conventional SVG viewing files. Files can be pre-converted for fast, easy viewing without taking up extra storage space. 

Enhance FinTech Applications with PrizmDoc Hybrid Viewing 

PrizmDoc’s new Hybrid Viewing feature allows FinTech developers to seamlessly scale their application’s viewing capabilities without having to deploy new servers or rethink their cost structure. Shifting document processing to local devices provides end-users with faster, more responsive performance, especially when viewing lengthy documents. By keeping viewing-related costs low, FinTech developers can focus their resources on developing new application features that help their products stand out in an increasingly competitive market. 

To learn more about how PrizmDoc’s Hybrid Viewing can benefit your FinTech application, talk to one of Accusoft’s PrizmDoc specialists today.

Question

When loading PDF documents into PrizmDoc that contain embedded highlights, rather than appearing translucent, the highlights are appearing opaque and are covering the underlying text. Why is this happening?

Answer

Prior to version 13.4 of PrizmDoc, this was occurring due to limitations in web browsers. The SVG attribute comp-op="multiply" was not widely supported in modern browsers.

With PrizmDoc version 13.4, the way highlights were rendered was changed to resolve this issue.

Question

In PrizmDoc, my document appears to be small on the page relative to the viewer. How can I fix this?

enter image description here

Answer

By default, PrizmDoc renders a PDF file according to the MediaBox, which is normally the same as CropBox, though sometimes this is not the case. The larger area you see in the PrizmDoc Viewer is the size of the MediaBox. Please note that the product provides the fileTypes.pdf.pageBoundaries control option (or useCropBox in the older versions) to change the default behavior. Try setting the option to cropBox in the Central Configuration File in order to get the PDF content rendered according to the CropBox. You can read more about configuring image frame rendering in our documentation here.

For additional reading, see 7.7.3.3 on “User Space” of Adobe’s PDF 1.7 specification:

https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf

Note: In some older versions of PrizmDoc, there exists an issue where setting the pageBoundaries field to cropBox can cause light blurring/distorting on the page. This issue was addressed in version 13.4.

Question

Where can I find the documentation for Accusoft PDF Viewer?

Answer

Our product documentation is located here.

Question

When loading PDF documents into PrizmDoc that contain embedded highlights, rather than appearing translucent, the highlights are appearing opaque and are covering the underlying text. Why is this happening?

Answer

Prior to version 13.4 of PrizmDoc, this was occurring due to limitations in web browsers. The SVG attribute comp-op="multiply" was not widely supported in modern browsers.

With PrizmDoc version 13.4, the way highlights were rendered was changed to resolve this issue.

Question

In PrizmDoc, my document appears to be small on the page relative to the viewer. How can I fix this?

enter image description here

Answer

By default, PrizmDoc renders a PDF file according to the MediaBox, which is normally the same as CropBox, though sometimes this is not the case. The larger area you see in the PrizmDoc Viewer is the size of the MediaBox. Please note that the product provides the fileTypes.pdf.pageBoundaries control option (or useCropBox in the older versions) to change the default behavior. Try setting the option to cropBox in the Central Configuration File in order to get the PDF content rendered according to the CropBox. You can read more about configuring image frame rendering in our documentation here.

For additional reading, see 7.7.3.3 on “User Space” of Adobe’s PDF 1.7 specification:

https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf

Note: In some older versions of PrizmDoc, there exists an issue where setting the pageBoundaries field to cropBox can cause light blurring/distorting on the page. This issue was addressed in version 13.4.

Question

I want to re-arrange the page order of a PDF. I’ve tried the following…

var page = imGearDocument.Pages[indx].Clone();

imGearDocument.Pages.RemoveAt(indx); //// Exception: "One or more pages are in use and could not be deleted."

imGearDocument.Pages.Insert(newIndx, page);

But an exception is thrown. Somehow, even though the page was cloned, the exception states that the page can’t be removed because it’s still in use.

What am I doing wrong here?

Answer

If you’re using an older version of ImageGear .NET, you may run into this exception when you clone the page. Some of the resources between the original and the clone are still shared, which is why this happens.

Starting with ImageGear .NET v24.8, this no longer happens, and the above code should work fine.

If you still need to use the earlier version, you can use the InsertPages method instead.