Technical FAQs

Question

We wanted to upgrade our previous version of PrizmDoc to the most recent release. However, when trying to install the latest version, the installation is failing. What do I need to do to get the latest version installed?

Answer

Typically, this issue may occur if you are upgrading from an older major version to a new major version, such as from PrizmDoc 11 to PrizmDoc 12 or PrizmDoc 13. If you are upgrading from one minor version to another, such as PrizmDoc 13.1 to PrizmDoc 13.6, then it should be seamless.

If you do have issues in either circumstance, it is usually due to files, folders, or registry settings that were left behind from the older version.

In order to fix the installation, please follow the process below to ensure the previous version is completely removed.

  1. Ensure previous installation folders are deleted:

    \Prizm and \ProgramData\Accusoft.

  2. Back-up your Windows registry, and then click on Start > Run, and type in regedit

  3. Click Edit and select Find, and then type Prizm

  4. When it finds a match, right-click on the registry key and select Delete

  5. Click F3 to find the next match, and repeat Step 4 for each key.

  6. Repeat Step 5 until the search comes back with “Finished Searching Registry”

  7. Reboot Server and attempt to re-install.

Question

What causes Session Expired errors in PrizmDoc?

Answer

Session expired errors normally occur when a viewing session is open for longer than 20 minutes. 20 minutes is the default value of viewing.sessionLifetime in the PrizmDoc central configuration file, and you can increase it if you would like your Viewing Sessions to be active longer. On PrizmDoc Cloud this value is set to 5 hours.

You can find the relevant config file using the following file paths:

  • Linux: /usr/share/prizm/prizm-services-config.yml
  • Windows: C:\Prizm\prizm-services-config.yml
Question

We are using the Webforms Samples and want to know how to enable the “Always User Raster” feature. Which file needs to be modified and how should it be modified?

Answer

In order to enable the “Always Use Raster” option for our Webforms sample, you will need to do the following:

  • Modify the Default.aspx file
  • Update the Central Configuration file

How To:

  1. In the Sample, before modifying, make a backup of the following file for safekeeping:

\Prizm\Samples\dotnet\webforms\full-viewer-sample\Default.aspx

  1. In the original file, modify the code that is located close to line 115:

\Prizm\Samples\dotnet\webforms\full-viewer-sample\Default.aspx

Line to Replace:

} else {
        sessionData.source = getDocumentSource(query.document || '');
        }

Replace with:

} else {
        sessionData.source = getDocumentSource(query.document || '');
        sessionData.render = {
          html5: {
             alwaysUseRaster: true
          }
       };
}
  1. Next, to update the Central Configuration file you will need to stop the Prizm Services.

  2. Make a backup of the prizm\prizm-services-config.yml file.

  3. Edit the .yml file and remove the leading # for the following line and add true to the array so that it looks like the following:

viewing.sessionConstraints.render.alwaysUseRaster.allowedValues:
[true, false]

  1. Restart the Prizm Services.
Question

When trying to create a viewing session directory to the PrizmDoc back end over port 18681:

(POST http://prizmserver:18681/PCCIS/V1/ViewingSession)

why am I receiving a 500 internal server error?

Answer

There are some troubleshooting steps below you can take to verify the health of the server as well as ensure the API call you are making is properly formatted.

  1. Verify the Prizm service is healthy by opening a browser on the Prizm server and using the following service health check URL (http://localhost:18681/admin)
  2. Verify your POST command has all the required elements which can be verified in detail on the following documentation page:

https://help.accusoft.com/PrizmDoc/latest/HTML/webframe.html#viewing-sessions.html

Question

When viewing an Excel document with hidden content in the viewer, the content remains visible when otherwise expected to remain hidden. Is this intended behavior?

Answer

Short answer: Yes.

Currently, both PrizmDoc Cloud and PrizmDoc Viewer (Self-Hosted) are configured to render hidden content by default, so this is expected behavior.

For PrizmDoc Viewer (Self-Hosted) users, this rendering behavior is configurable using the central configuration file.

The file paths for the central configuration file are:

  • Linux: /usr/share/prizm/prizm-services-config.yml
  • Windows: C:\Prizm\prizm-services-config.yml

Simply add/modify the following parameter:

fileTypes.excel.renderHiddenContent: false

Setting the render option to false will hide content as expected, whereas true will render it.

In a recent LegalTech article, Lisa Senger highlighted some of the concerns facing law firms in an age when sharing information is becoming increasingly digital. Collaborating with colleagues and sharing  information with opposing counsel can put confidential client information at risk. As the need for increased security rises, developers are under pressure to meet the demands of their clients and ensure the safe and confidential transfer of information over a variety of networks outside of the organization.

To save the money and effort it takes to develop and stay up-to-date on the latest software for security, many developers are looking to third party providers, like Accusoft, to supply the latest solutions for eDiscovery confidentiality and security. How can Accusoft enhance your current eDiscovery offer?

Redaction
The easiest way to preserve the confidentiality of your end users’ clients is to eliminate the confidential information. With built-in redaction capabilities, Prizm Content Connect makes file sharing and collaboration easy and secure. When text is selected and redacted from a document, the redactions are burned into the new saved version, eliminating the confidential data from the file before it is shared with a third party. With auto-redaction, eDiscovery is less burdensome on law firms, allowing them to find repeated instances of confidential information–like a social security number–and redact it throughout a document automatically.

Digital Rights Management
When sharing client information outside of the firm, your clients are worried about that information being stolen or otherwise misused. For instance, after a case is over, opposing counsel may not delete files in a timely manner, putting confidential information at greater risk. With DRM, you can control who sees which files, and for how long. Our software allows you to assign permissions to view, print and download files and documents. After a case is over, you can simply revoke permission to access the document to ensure users cannot view confidential client information longer than necessary.

These are just two ways Accusoft provides security and confidentiality solutions for you and your clients. Our Prizm Content Connect suite of products can be tailored to suit your unique needs in catering to your eDiscovery and legal clients. You can view code samples here.

To see PCC in action, download your free 30 day trial today.

download a free trial

Question

Why do the fonts in my document look different when rendered in PrizmDoc?

Answer

There are times when a document was created on a machine where a user installed a non-standard font (e.g., Maestro-Regular). When the document is viewed on another system, without that font installed, the text will look different.

PrizmDoc uses the fonts installed on the server where it is running when converting the document. If the document has a non-standard font, and the font is not installed on the server where PrizmDoc is running, then it will render the document with a default font.

To fix the issue, you need to install the font onto the PrizmDoc server that converted the document. The procedure below outlines how to install the font on a Windows server. You will need to ensure that you are logged in as the same UserId that the Prizm Service is using.

  1. Identify the name of the font that needs to be installed and download the font file associated with that font. The font file name will typically be in the format of fontname.ttf.
  2. Copy the .ttf file to the server running PrizmDoc.
  3. On the server, right-click the .ttf file and select Install from the menu.
  4. Stop all of the Prizm services.
  5. Clear all folders under \Prizm\Cache – this will clear the previously rendered files that had the wrong font rendered.
  6. Reboot the server and attempt to open the document again.
Question

We are currently using PrizmDoc Cloud licensing. After applying our cloud license, the Prizm services started and show healthy, however, I see “CloudLicenseValidationFailed” errors in the PccErrors.log file. Is this normal, and do I have to worry about Prizm functionality?

Answer

Currently the licensing messages referencing “CloudLicenseValidationFailed” in PccErrors.log are a false positive and should not be taken as an issue with PrizmDoc Cloud licensing.
The more accurate way to check whether the license has been validated successfully would be to use watchdog.log and look for “Cloud License Validation” – “isValid”:true which indicates that the license is valid.

The issue regarding that error in pccerrors.log is in our product backlog to consider addressing in a future release, but it is not yet prioritized on our roadmap.

Question

When looking at the configuration files for both PAS (pcc.win.yml, pcc.nix.yml) and PrizmDoc Server (prizm-services-config.yml), there appear to be similar settings for Viewing Session timeouts: defaults.viewingSessionTimeout (PAS) and viewing.sessionLifetime (Server). What is the difference between the two?

Answer

The difference is as follows:

PAS

defaults.viewingSessionTimeout

This setting is used when the viewing session POST requests use source.type="viewingPackage".

Prizm Server

viewing.sessionLifetime

This setting is used for all other viewing session POST requests.

Question

How can I enable content encryption in PrizmDoc Viewer?

Answer

First, you need to enable content encryption on the PrizmDoc Server in the central configuration file. To do this, find the viewing.contentEncryption.enabled section and change the value to true. Save the changes to the file and restart the PrizmDoc services for the change to take effect.

The file paths for the central configuration file are:

Linux: /usr/share/prizm/prizm-services-config.yml
Windows: C:\Prizm\prizm-services-config.yml

Next, you need to enable content encryption in the Viewer. To do this, in the index page of your viewer (Default.aspx in C#, index.php in the PHP sample, index.html, etc.), provide the encryption option in the viewer options parameter as follows so that the Viewer can handle encrypted data:

function buildViewerOptions() {
    ...
    var optionsOverride = args.pop(); // always last arg
    var options = {
        ...
        encryption: true
    };
    var combinedOptions = _.extend(optionsOverride, options);
    embedViewer(combinedOptions);
}

For more in-depth information on enabling content encryption in PrizmDoc, please refer to our documentation here.

Question

ImageGear .NET v24.6 added support for viewing PDF documents with XFA content. I’m using v24.8, and upon trying to open an XFA PDF, I get a SEHException for some reason…

SEHException

Why might this be happening?

Answer

One reason could be because you need to execute the following lines after initializing the PDF component, and prior to loading an XFA PDF:

// Allow opening of PDF documents that contain XFA form data.
IImGearFormat pdfFormat = ImGearFileFormats.Filters.Get(ImGearFormats.PDF);
pdfFormat.Parameters.GetByName("XFAAllowed").Value = true;

This will enable XFA PDFs to be opened by the ImageGear .NET toolkit.

 

FinTech adoption continues to accelerate. According to Wealth Professional, almost 40 percent of finance firms now prioritize the adoption of FinTech frameworks, even as new-to-market startups disrupt the status quo. 

However, spending alone isn’t enough to deliver streamlined and scalable FinTech processes. As noted by David Linthicum, Chief Cloud Strategy Officer at Deloitte in a recent protocol piece, firms now face the challenge of creating “high-quality, repeatable data processes with the profusion of systems involved in generating data” while simultaneously integrating unstructured and semi-structured data sources into existing processes.

At the front lines of this fundamental framework change is digital documents and business process workflows. Let’s dive in, and look at some of the biggest frustrations facing the finance industry, the solutions they need to streamline digital processes, and how Accusoft’s ImageGear can help redefine digital document delivery.


FinTech Framework Challenges

By leveraging data-driven techniques and digital-first processes, Forbes notes that it’s possible for even startup firms to differentiate their service delivery and compete with huge financial brands — but only when digital document processes align with on-demand performance expectations. 

Consider common use cases such as loan origination, credit applications, or mortgage approvals. Many FinTech firms now target client pre-approval within 24 hours rather than the days or weeks required by traditional finance corporations. The problem? As digital document processes naturally scale, so does complexity, creating a practical paradox around three key challenges:

  • Speed As noted above, many FinTech firms are looking to disrupt incumbent efforts by reducing approval times and increasing customer satisfaction. As the number and type of digital documents required for timely approval expands, disparate processes conspire to stifle speed. Consider a loan origination requiring identity verification, income confirmation, and current debt load documents for pre-approval, all of which are in different file formats, forcing firms to use multiple software solutions and slowing their progress.
  • SecurityCybersecurity and compliance are critical for FinTech firms to succeed, but both requirements come with rapid scaling complexity. For example, a recent FDIC document lists more than 200 types of Compliance Information and Document Request (CIDR) forms which must be customized for each financial use case. The result? Increased document processing volumes drives increased complexity and opens potential security gaps.
  • ConsistencyDigital data consistency is critical to ensure accurate approvals and assess potential risks, but contrasting document processes create the ideal environment for human error. Despite best efforts on the part of employees, the more manual processes introduced into FinTech functions, the greater the chance of misplaced assets or data conversion mistakes.

Streamlined Structure Solutions

To bridge the gap between FinTech potential and fast-track document processes, companies need solutions that deliver four broad benefits:

  • Document ConversionFinTech firms now face a diverse range of documents that often frustrate efforts to unify key data. Here, integrated conversion functionality is critical to ensure employees have the tools they need to quickly convert key documents without having to open multiple applications and manually move or manipulate data.
  • On-Demand AnnotationSpeaking of data, it’s also essential for staff to collaborate on key documents, especially as many FinTech firms embrace the remote work revolution. Advanced annotation tools that allow asynchronous collaboration are essential to ensure employees always have access to the most current document version and administrators can easily determine who edited documents, when, and why.
  • Digital CompressionAs digital documents become the de facto financial standard, storage space is at a premium. This is especially problematic for larger document types such as PDFs, which are often preferred by FinTech firms for the ability to easily control access, editing rights, and collaboration. Uncompressed, these PDFs can quickly overwhelm even enterprise storage systems, forcing companies to either spend more on cloud services or invest in bigger datacenters. Reducing PDF size both saves space and helps companies streamline document sharing.
  • PDF ManipulationWhile read-only access makes PDFs ideal for FinTech firms that need to share specific information without introducing security risk, adjusting and editing these documents in-house often requires multiple applications and increased employee effort. Even more worrisome? Staff encountering functional limits may opt for free, online applications that could compromise document confidentiality.

Practical Process Performance

ImageGear is designed to help FinTech firms both overcome current frustrations and help future-proof financial frameworks by combining disparate document functions into a single-source application and improve overall performance. Standout features include:

  • Complete PDF ControlImageGear provides a single-platform solution for PDF manipulation and control. Developers can easily integrate an SDK that enables application users to create, edit, view, and print PDFs from within the confines of existing applications, create searchable PDF documents, or flatten acroforms to remove file interactivity, all while automatically conforming to the PDF language standard.
  • Secure Signature VerificationSecure digital signatures now form a critical component of on-demand FinTech forms processing. If companies can’t accept and verify client signatures, they’re not able to deliver speedy approvals and meet evolving consumer expectations. ImageGear allows companies to ensure that electronic documents are authentic. It uses encryption to verify that the information  has not been altered and is coming from a trusted source.
  • Agile AnnotationsMaking changes to PDF files is easy with ImageGear. Staff can quickly add text, lines, hot spots, encryption, rich text, images, or even audio as needed to ensure documents are complete, accurate, and ready for approval.
  • Comprehensive Conversion OptionsTo deliver on the promise of FinTech performance, firms must be able to quickly and easily convert and combine multiple file types into a single PDF and convert PDFs as necessary into other file formats. ImageGear empowers developers to integrate a way for application users to quickly convert documents to PDF, create PDF/A files from raster images, and convert scanned pages into PDF searchable text using advanced optical character recognition (OCR). Annotations marks can also be converted as needed into XML files for enhanced auditability.
  • Substantial File Size ReductionImageGear enables file compression of up to 45 percent to save valuable storage space and utilizes automatic analysis to determine optimal compression operations for best-fit results.

Ready to embrace the future of FinTech and redefine digital document delivery at scale? Start your free trial of ImageGear today!