Technical FAQs

Question

How do I use a Network Drive path for Image and ART storage in my ImageGear .NET web application?

Answer

In an ImageGear .NET web application, you have to define the location of the images and annotations directory in the storageRootPath and artStorageRootPath configuration property.
In the current version of ImageGear .NET, the storageRootPath and artStorageRootPath do not work with a network drive path \\SERVER-NAME\sharefilename.

The workaround for this would be to create a Symbolic link from a local directory to the network drive directory.

  • To create a symbolic link: Open “Command Prompt” as Administrator and type in > mklink /d "local path" \\SERVER-NAME\sharefilename
  • Pass in the path of the symbolic link as image or art storage root path in your web.config: storageRootPath="local path" artStorageRootPath="local path"
Question

How do I use a Network Drive path for Image and ART storage in my ImageGear .NET web application?

Answer

In an ImageGear .NET web application, you have to define the location of the images and annotations directory in the storageRootPath and artStorageRootPath configuration property.
In the current version of ImageGear .NET, the storageRootPath and artStorageRootPath do not work with a network drive path \\SERVER-NAME\sharefilename.

The workaround for this would be to create a Symbolic link from a local directory to the network drive directory.

  • To create a symbolic link: Open “Command Prompt” as Administrator and type in > mklink /d "local path" \\SERVER-NAME\sharefilename
  • Pass in the path of the symbolic link as image or art storage root path in your web.config: storageRootPath="local path" artStorageRootPath="local path"

 

Enterprises are continuously engaged in a process of evaluating their operations to identify opportunities for improvement. When one of the world’s leading mortgage lenders took a closer look at how it was handling documents to process applications, it quickly recognized the need to implement a solution that would allow them to scale capacity and enable faster loan processing. The company’s diversified businesses included banking, capital markets, and insurance, all of which combined to handle more than $1 trillion in mortgages, with nearly $2 billion in new loans each day.

Overview

For many years, the lender had processed applications by hand, entering information from paper and electronic forms into a mortgage processing application. While users had to thumb through paper documents, electronic loan documents were made available through a content management system and a dual-monitor workstation. One screen contained the loan processing application and a list of electronic loan documents. The other screen displayed the selected document and allowed the user to browse its contents. 

In examining their loan purchasing process, the lender discovered that while it took 7-9 days to close a paper document loan, electronic documents closed in just 4-5 days. Unfortunately, the legacy content management system limited scalability and performance, and a grossly underpowered document viewing application further impacted user productivity. The potential revenue gain in expanding their use of electronic documents was enormous – in terms of enhanced efficiency alone. To retain their competitive edge in a challenging market, the lender made the decision to replace their legacy CMS with an enterprise solution.

Challenges

But in order to realize the full productivity potential of the new enterprise CMS system, the lender also needed to upgrade its client document viewing application. The new viewer needed to provide reliable viewing for various types of electronic forms, including scanned documents, faxes, and emails in TIFF, JPEG, and PDF formats. To meet productivity demands, the first page of each document had to be accessed within two seconds. The technology also had to be entirely web-based since no documents could be stored on a client’s desktop or hard drive due to compliance constraints. From a user experience standpoint, the viewing solution also needed to provide scalable thumbnail rendering, accommodate mouse and keyboard navigation with “hot keys,” and be able to meet rigorous load-testing requirements. 

After a thorough review of available options, the lender selected Accusoft’s PrizmDoc® for Java, formerly VirtualViewer®, HTML5 viewing technology to address its complex functionality and security requirements. Critically, PrizmDoc® for Java supported the lender’s required document set of PDF, TIFF, and JPEG, as well as AFP, PCL, MS Office, and many other important business document formats, which provided the growing lender with additional flexibility for future expansion. The viewer also delivered a variety of thumbnail features, including page rotation sync, full panel view, and adjustable size options. PrizmDoc® for Java’s configurable user interface would also make it easy to implement navigation options and hot keys that enhanced productivity. 

The lender had little time to dedicate to the integration with its new enterprise CMS solution, especially since much of the integration time would be taken up by the load-testing process. Fortunately, PrizmDoc® for Java’s intuitive API made it easy to incorporate the product seamlessly while leaving plenty of time for load testing. 

Results

Replacing their legacy content management system and integrating Accusoft’s powerful PrizmDoc® for Java high-speed HTML5 viewer enabled the lender to achieve its desired performance standards. Because PrizmDoc® for Java is completely web-based and requires no software to be installed on the client’s desktop, the lender could easily roll out a scalable solution that met critical security and business continuity objectives within a single, high-speed viewing application. 

The viewer’s server component renders and delivers individual pages to the client quickly and seamlessly, well within the lender’s required sub-two-second access requirements, even when accessing large, multi-page loan documents in various geographical locations. PrizmDoc®for Java now helps to increase the mortgage lender’s productivity by allowing users to access, view, annotate, and manipulate loan documents on the fly without ever touching the client’s local hard drive.

As a result, the lender can now import daily peak loads of more than half a million documents and deliver them to users across the enterprise in under two seconds, improving their overall mortgage processing time by more than 40 percent.

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

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.

Question

Currently we are using PAS for viewing packages and it is pointed to our Accusoft Cloud subscription API key. PAS is installed locally and we store the viewing package artifacts in our S3 bucket. We are using 600 GB of storage on S3 for the viewing package artifacts we already have converted.

We would like to start using Accusoft’s Cloud PAS API to create viewing packages and no longer wish to host our own PAS and have the following questions:

  1. Is there a way we can migrate our current artifacts from our S3 bucket to Accusoft’s S3 bucket?
  2. Is there an additional charge for storing the artifacts at Accusoft?
  3. Is there a way to point the Cloud PAS to our existing S3 bucket?
Answer

Q: Is there a way we can migrate our current artifacts from our S3 bucket to Accusoft’s S3 bucket?

A: We do not currently offer an API for directly importing your existing viewing packages. However, you can re-create your viewing packages in PrizmDoc Cloud using the original source document.

Q: Is there an additional charge for storing the artifacts at Accusoft?

A: At this time there is no additional charge. However, this is
subject to change.

Q: Is there a way to point the Cloud PAS to our existing S3 bucket?

A: There is currently no setting available to configure your PrizmDoc Cloud account to use an S3 bucket which you own. If you use PrizmDoc Cloud, the storage is managed by Accusoft. If you need to own and manage the storage yourself, you’ll want to use your own Self-Hosted PAS.

Upgrading technology software

Periods of great disruption often have a way of presenting opportunities to companies willing to make the right investments in the future. That’s been especially true of the COVID-19 pandemic, which demonstrated that many organizations are, in fact, capable of implementing rapid and sweeping technology changes when they prioritize such initiatives. A survey of executives by McKinsey found that companies implemented significant digital transformations 20 to 25 times faster than expected, largely due to urgency and the removal of longstanding roadblocks. 

By undertaking major technology upgrades now, businesses can position themselves for future success before a new status quo settles in to stifle change. Companies would do well to focus their attention on a few potential areas where their applications could support digital transformation efforts with just a bit of customization.

The Great Remote Migration

The COVID-19 pandemic forced many organizations to rapidly implement the policies and technology necessary to support a remote working environment. Even though the vaccine rollout has made it possible for people to return to the physical office, not every company is rushing to bring everyone back. According to a survey of enterprise CEOs, 68 percent of large organizations are planning to downsize their office footprint and keep at least some portion of their workforce remote.

Although it no longer seems likely that remote work arrangements will completely replace traditional in-person offices, it does appear that the hybrid workforce is gaining popularity as the new normal for organizations. These workplaces will maintain a physical office presence while also incorporating a large number of remote employees. In some cases, these remote workers will be geographically distributed and never set foot in the office. This will allow companies to tap into broader talent pools from around the world. In other cases, employees will be given the option to work remotely under certain conditions, allowing them to decide when they have to actually travel to the office.

Both arrangements will present a number of challenges from a technology and a policy standpoint. In order to create a successful hybrid workplace, companies must continue to make investments in the digital document management technologies that make remote work possible. In addition to managing the myriad security challenges posed by remote employees, they also need to rethink how to handle documents now that passing paper for processing is not as simple as walking that paper document down the hall.  Developers can support the transition by focusing their efforts on building robust applications that can be accessed anywhere and can handle the viewing and processing of digitized documents.

Shifting Customer Expectations

Another major change coming out of the pandemic is the extent to which customers now expect brands to offer a better digital experience with their services. Not only do people use more digital services, but their expectations about how those services should respond to their needs also underwent a significant change. They expect services to be faster and less complicated, and their tolerance for experiences that fall short of those expectations will be lower than ever in the years to come.

Organizations that fail to invest in technology and applications that allow them to better address customer demands will find themselves falling behind in an increasingly competitive landscape. That creates tremendous opportunities for developers to build and market software that does a better job of creating a seamless link between companies and their end-users. That will include user experience features like better document viewing, more accurate data capture, and improved automation tools.

Developers are also under pressure to design innovative applications that can transform business processes and help companies get an edge over their competitors. Sophisticated features powered by machine learning and big data can provide valuable business intelligence and automate low-value tasks to boost productivity. To focus on those capabilities, developers will increasingly rely on third-party SDK and API solutions to deliver core functionality like viewing, conversion, annotation, and compression. By relying on proven, ready-made solutions, they can dedicate more time and resources to innovation.

Rethinking Document Lifecycle Technology

Even before the pandemic, organizations were trying to consolidate and simplify their technology infrastructure to eliminate unnecessary sprawl and software redundancies. Often referred to as application rationalization, this trend will undoubtedly continue as companies look to maximize efficiency to reduce costs while enhancing productivity. One business process that will certainly get a closer look is document lifecycle management.

Traditionally, companies have relied upon multiple software tools to handle the operations associated with each step of the document lifecycle. Common tasks like document scanning, form identification, data extraction, file conversion, viewing, and annotation could all be performed by distinct applications, forcing employees to constantly switch between programs and copy or move files in order to work with them. This process is not only grossly inefficient but also greatly increases the risk of human error or version confusion

Thanks to a new generation of SDK and API tools, developers can easily add new features to their software products that help to streamline and consolidate key elements of digital document lifecycles. From HTML5 viewing capabilities that make it easier to convert and open files within a web browser to more sophisticated data capture and document assembly tools that make true automation possible, these easy-to-implement integrations allow applications to carry out more essential workflow tasks without having to rely on external support.

Upgrading Your Application’s Potential with Accusoft

As organizations seize the opportunity to make essential technology upgrades, developers must be ready to provide them with the innovative applications capable of replacing legacy systems and keeping pace with customer expectations. Building software with the extensive functionality that companies require will continue to be a challenge for software teams facing budget and resource limitations. By turning to a partner with the right software integrations, they can quickly implement a wide spectrum of powerful features while keeping their own development efforts focused on designing best-in-class capabilities and bringing them to market quickly.

Accusoft’s collection of SDK and API solutions allows you to build a variety of powerful processing tools into your applications. Whether you need the conversion, viewing, and annotation features of PrizmDoc Viewer, the robust back-end processing capabilities of ImageGear, or the automated forms processing tools of the FormSuite Collection, our family of software integrations can help your application meet the varied needs of today’s companies. Learn more about our SDK and API solutions and explore how they can make your current project even more impressive.

Question

We are adding files to the viewing session with HttpWebRequests. We noticed with larger files the response is:

(413) Request Entity Too Large. -  at System.Net.HttpWebRequest.GetResponse(). 

What could be the cause?   

Answer

A 413 request entity too large error occurs when a request made from a client is too large to be processed by the web server. If your web server is setting a particular HTTP request size limit, clients may come across a 413 request entity too large response. An example request that may cause this error would be if a client was trying to upload a large file to the server (e.g., a large media file).

Depending on which web server you use, implement the necessary changes described below to configure your web server’s maximum HTTP request size allowance. Below are some suggestions for popular Web Servers:

For Nginx users:

The directive that determines the allowable HTTP request size is client_max_body_size. This directive can be defined in your nginx.conf file located at /etc/nginx/nginx.conf

For Apache users:

The directive is LimitRequestBody which can be defined in your http.conf file or in an .htaccess file.

For IIS users:

  1. Open Internet Information Services (IIS) Manager.
  2. In the Connections pane, go to the connection, site, application, or directory for which you want to modify your request filtering settings.
  3. In the Home pane, double-click Request Filtering.
  4. Click Edit Feature Settings in the Actions pane.
Question

When viewing documents using Internet Explorer 11, we are noticing an abnormally high CPU utilization. It gets worse when zooming in up to 800% through the PrizmDoc Viewer. It only seems to happen on certain machines. Why might this be happening?

Answer

A possible factor for this type of performance issue can potentially be corrected by enabling Internet Explorer’s hardware acceleration feature.

This feature can be enabled or disabled with the following steps:

  1. Open Internet Explorer 11, click on the Tools icon, and select Internet Options.
  2. Navigate to the Advanced tab and enable the Use software rendering instead of GPU rendering option.
  3. Click Apply and restart the browser.
Question

Currently we are using PAS for viewing packages and it is pointed to our Accusoft Cloud subscription API key. PAS is installed locally and we store the viewing package artifacts in our S3 bucket. We are using 600 GB of storage on S3 for the viewing package artifacts we already have converted.

We would like to start using Accusoft’s Cloud PAS API to create viewing packages and no longer wish to host our own PAS and have the following questions:

  1. Is there a way we can migrate our current artifacts from our S3 bucket to Accusoft’s S3 bucket?

  2. Is there an additional charge for storing the artifacts at Accusoft?

  3. Is there a way to point the Cloud PAS to our existing S3 bucket?

Answer

Q: Is there a way we can migrate our current artifacts from our S3 bucket to Accusoft’s S3 bucket?

A: We do not currently offer an API for directly importing your existing viewing packages. However, you can re-create your viewing packages in PrizmDoc Cloud using the original source document.

Q: Is there an additional charge for storing the artifacts at Accusoft?

A: At this time there is no additional charge. However, this is
subject to change.

Q: Is there a way to point the Cloud PAS to our existing S3 bucket?

A: There is currently no setting available to configure your PrizmDoc Cloud account to use an S3 bucket which you own. If you use PrizmDoc Cloud, the storage is managed by Accusoft. If you need to own and manage the storage yourself, you’ll want to use your own Self-Hosted PAS.

native excel support

Despite the explosive growth of big data and sophisticated analytics platforms, a 2019 study by Deloitte found that 67 percent of business leaders are not quite comfortable using them to inform decision making. For many organizations, spreadsheets remain the preferred tool for managing data and evaluating trends. Developers looking to build the next generation of business applications can accommodate those tendencies by integrating native spreadsheet support for Microsoft Excel workbooks.

Excel Worksheets vs Excel Workbooks

Although sometimes referred to interchangeably or described broadly as spreadsheets, there is a key distinction between an Excel worksheet and an Excel workbook. A worksheet consists of only one spreadsheet while a workbook contains multiple different spreadsheets separated by tabs.

The difference may not be very important when viewing or sharing XLSX files natively in Microsoft Excel, but it can create serious challenges when rendering those files in another application. Without some way of accurately rendering dynamic spreadsheet data, viewers are often forced to resort to a static print preview image. This process makes the file viewable, but also leaves it “flattened” because all interactive elements are removed from the spreadsheet cells.

If the workbook contains worksheets with linked data (that is, cell data from one sheet is affected by cell data from another sheet), it’s critical that a viewing solution preserves the dynamic aspects of the file. The advantage of a spreadsheet is that it can serve as a working document. Without the ability to interact with it, users might as well simply copy and paste the data into a text document.

Managing Excel Workbooks with PrizmDoc Cells

PrizmDoc Cells provides several options for managing Excel workbooks, making it easy to transition back and forth between XLSX format and web browser viewing. Once a proxy route is set up within the application to send API calls to the PrizmDoc Cells server, three different commands can be used to manage Excel workbooks.

Upload Workbook

This API call adds a new XLSX file for viewing and editing. When a document is uploaded to the system, the server assigns a unique workbook ID to it so it can be found and rendered in the application’s viewer in the future. After uploading a workbook, a new session can be created using the workbook ID for viewing and editing purposes. 

Download Workbook

When PrizmDoc Cells displays a spreadsheet, it renders the XLSX file itself, but it doesn’t make any alterations to that file. As each session makes edits to the workbook, those changes are associated with the document ID rather than the original XLSX file, which preserves the integrity of the original spreadsheet. At some point, however, those edits may need to be saved into a new Excel workbook. 

The download API call converts the current session document so it can be downloaded as an XLSX file. File availability can be set during the download process to control who will have access to the new workbook.

Delete Workbook

Old versions of workbooks often need to be deleted for security reasons, usually because they contain confidential data. Since the original XLSX file remains safely within application storage, there often isn’t much sense in retaining workbooks IDs that aren’t being used. The delete API call removes a workbook ID from the server. Once removed in this way, the workbook cannot be viewed, edited, or downloaded by PrizmDoc Cells.

Preserving Workbook Functionality

Since PrizmDoc Cells natively renders information contained in an XLSX file, it retains the dynamic elements that make spreadsheet workbooks so useful to organizations. Not only does it preserve proprietary business logic and formulas, but it also maintains the integrity of this information across multiple worksheets. Cell content can still be searched to quickly locate important text or data throughout the workbook.

For situations where proprietary formulas need to be protected, PrizmDoc Cells allows users to upload XLSX workbooks as values-only files, with all spreadsheet formulas removed. Also, any cells locked in an uploaded XLSX file will remain locked in PrizmDoc Cells to preserve workbook security.

True Spreadsheet Workbook Support for Your Applications

Many organizations continue to depend upon spreadsheet workbooks to manage their business. By providing feature-rich workbook support within their applications, developers can help them retain control over their proprietary spreadsheet formulas without sacrificing the functionality they expect from Excel. 

PrizmDoc Cells makes it easier than ever to share spreadsheet workbooks without having to rely upon Microsoft Excel dependencies. Shared XLSX files can remain safely within a secure application environment to prevent unauthorized downloads or troublesome version confusion. Get a first-hand look at how PrizmDoc Cells can enhance your application in our extensive online demo.