Technical FAQs

Question

I have an evaluation license for PrizmDoc. Can I evaluate MSO features with this evaluation license?

Answer

No, regular PrizmDoc evaluation licenses do not have MSO functionality. They will instead use LibreOffice to convert documents. Contact an Accusoft Support Technician or your Account Representative to discuss evaluating PrizmDoc with MSO enabled.

Although it might feel as though time has been standing still for several months, 2020 is finally coming to an end. It’s been a year of unprecedented disruption for many industries, and insurance companies often found themselves struggling to adapt to change. Firms that had the foresight to invest in digital transformation backed by InsurTech solutions, however, proved more capable of meeting the moment and are now poised to thrive in 2021 and beyond.

As the new year approaches, it’s helpful to take a look back at some of the key trends that defined 2020 and created opportunities for innovative InsurTech applications. Understanding the pressures facing the insurance industry will also identify InsurTech projections to watch in the future.

5 Insurance Trends and InsurTech Projections

1. Remote Collaboration

No discussion of 2020 insurance industry trends would be complete without exploring how the COVID-19 pandemic has affected organizations. According to a survey conducted by Deloitte, 48 percent of insurance executives agreed that the pandemic revealed how unprepared their business was for such a disruptive crisis. From the sudden transition to a remote workforce to a shift in risk adjustment factors across the market, insurers have had to scramble to adapt their operations and continue delivering quality services to clients.

With so many employees going remote and customers unable to meet with representatives in-person, organizations that made early investments in digital collaboration tools and automation software were better equipped to meet the challenges of 2020. The industry is expected to make tremendous investments in digital transformation in the upcoming year, whether it’s in powerful document editing and management software, file conversion tools, or secure communication channels that better facilitate true collaboration.

2. Customer Demographic Shifts

Prior to 2020, insurance customers tended to be older, with millennials purchasing life insurance policies at lower rates and often delaying home ownership until later in life. This trend seems to have reversed itself in the wake of the COVID-19 pandemic, however, with life insurance application activity growing twice as fast for people under 45 than those aged 45-49. Since many of these younger buyers are first-time applicants, it’s important for insurance agents and firms to make the process as streamlined and easy to navigate as possible.

According to a nationwide industry survey, just over 75 percent of independent insurance agents are age 50 or older and nearly 68 percent have more than 20 years of experience. Having such a long-tenured workforce poses challenges when it comes to implementing new processes and reaching out to potential customers with different needs and preferences than those of earlier decades. In order to remain competitive, however, firms must invest in the right InsurTech solutions to gather data that will give them a better picture of what insurance products and services younger customers will find attractive.

3. Robotic Process Automation

The shift to a remote workplace greatly disrupted traditional workflows. Without centralized offices, key insurance tasks like claims processing and document verification are much more difficult to perform manually. Organizations that had already invested in robotic process automation (RPA) to handle repetitive tasks were in a much better position to thrive in a remote landscape. 

Insurance companies must be able to process a variety of forms during an application or a claim. Having automated InsurTech tools in place to quickly extract data from a variety of sources and carry information over from one form to another not only saves time, but also greatly reduces the risk of human error. For a remote workforce, automation software helps to consolidate complex workflows to eliminate version confusion and enhance collaboration.

4. Artificial Intelligence

Risk assessment and data analysis are crucial to the underwriting process. In a volatile economic environment, insurance firms are under more pressure than ever before to set the right premiums. Although the data is now readily available to make more accurate assessments, sorting through that information manually is difficult and time consuming. 

As the COVID-19 pandemic demonstrated, the scope of risk can change dramatically in a very short period of time. By deploying artificial intelligence (AI) to analyze risk factors and review potential fraud claims quickly and accurately, insurers can create customized policies and provide more responsive service to their customers.

Implementing AI-driven algorithms as part of the underwriting and fraud analysis process will only be one part of the challenge facing firms in 2021. These powerful tools must have sufficient data in order to make informed predictions. By improving the data collection process with form processing tools, file conversion, and programmatic searches, insurers can provide their analytics platforms the best possible information for analysis.

5. Customer Experience

One of the few positive impacts of the COVID-19 pandemic was that it forced organizations across every industry to find new ways of connecting with their customers. The insurance industry has traditionally lagged behind other sectors, tending to lean upon a combination of tradition and legacy infrastructure to engage with customers. But the events of 2020 have underscored the need for a true digital transformation that fundamentally reorients the way firms market, sell, and deliver insurance products. The need has become so evident, in fact, that a recent PWC survey found that 70 percent of insurance CEOs are prioritizing customer experience and user interfaces as their top investment opportunity.

In the coming year, firms will likely continue to invest in technology that makes it easier for customers to research and manage their policies. Whether it’s applications that allow them to submit claims information in a variety of file formats or forms and contracts that automatically fill in commonly used form fields, the core focus will be on making the customer experience as frictionless as possible with a variety of InsurTech benefits.

The Role of InsurTech

Many insurance companies will be looking to upgrade their technology stack and client-facing applications in response to these trends. That creates a tremendous opportunity for InsurTech developers who are creating the next generation of software tools to streamline core processes common to the insurance industry.

Delivering those digital products on a short timeline with limited resources, however, can be quite a challenge for even the most innovative InsurTech startup. That’s why many of them turn to third-party solutions to provide proven functionality that lies outside the scope of their development expertise. 

Features like forms processing, document conversion, and image viewing can be easily integrated into an application using an SDK or API, saving the team weeks or even months of work. This helps InsurTech companies get their products to market faster to meet the digital transformation needs of their customers and keep them a step ahead of their competitors.

InsurTech SDKs and APIs

Accusoft’s family of processing and automation SDKs and APIs provide InsurTech developers with the tools they need to easily plug essential functionality into their applications so they can get back to focusing on their most innovative features. With a variety of deployment options and a diverse set of code-based solutions, we have the flexibility to meet your software’s unique use case and substantially reduce your time to market.

Whether you’re looking to integrate document viewing, collaboration, or processing to your InsurTech platform, our SDK and API-based products can help you deliver the InsurTech benefits your customers are looking for. Learn more about our insurance solutions or contact us today to demo one of our products.

Question

In the PrizmDoc Viewer, what are the two different ways to load annotation layers?

Answer

PrizmDoc has two options for loading annotations, the “My Annotations” pane and the “Annotations for Review” pane.

The “My Annotations” pane is used to load a single annotation layer for editing. You can add, delete, or make changes to annotations and then save those changes using the “My Annotations” pane.

The “Annotations for Review” pane is used for viewing annotations. You can load as many annotation layers for viewing as you would like. You cannot interact with annotations loaded in this way, but you are able to make comments on them. You can toggle between any of these layers to hide them. You can also merge these annotations to the currently loaded annotation layer from “My Annotations”.

For more information see our documentation here: https://help.accusoft.com/PrizmDoc/latest/HTML/Annotation_Layers.html

Question

When printing in PrizmDoc, the bottom of my document is being cut off. Why is this happening?

When I download the document as PDF, I do not lose parts of the document. However, if I print the document to PDF, I lose some data off the very bottom (maybe an inch or so).

Answer

In PrizmDoc, the page is to "fit to width" onto the paper by design. The bottom of the page will be cut off in cases where the length of the page extends further than the length of the paper. If you’re printing with Letter size paper (the default), it presumes a document that measures 8.50 by 11.00 inches. Suppose your document measures 8.50 x 13.00 inches. That additional 2 inches will be cut off during printing. This is why you may lose parts of the document while printing, but not if you download the document since it’s downloading the document as-is.  

To prevent this from happening, select a paper size large enough for your document (in the viewer print dialog and the system print dialog). Using the previous 8.50 x 13.00 inch example, you can select "Legal" size paper, which measures 8.50 x 14.00 inches, and would be long enough to support that document.

You could also modify your viewer to add a custom paper size if this fits your use case. Below is some sample code demonstrating this in our Viewer sample. You would need to enter your own custom paper sizes.

https://www.accusoft.com/code-examples/printing-custom-paper-sizes/

Changes to printTemplate.html:

    /*custom */
    .portrait .custom.page { width: 11in; height: 11in; margin: 0 auto !important; }
    .portrait .custom.pageIE { width: 9.5in; height: 9.5in; margin: 0 auto !important; }
    .portrait .custom.pageSafari { width: 8.9in; height: 8.9in; margin: 0 auto !important; }
    .portrait .custom.nomargins { width: 11in !important; height: 11in !important; }
    /* even without margins, Safari enforces the printer's non-printable area */
    .portrait .custom.nomargins.pageSafari { width: 9.32in !important; height: 9.32in !important; }
    
    .landscape .custom.page { height: 11in; width: 11in; margin: 0 auto !important; }
    .landscape .custom.pageIE { height: 9.05in; width: 9.05in; margin: 0 auto !important; }
    .landscape .custom.pageSafari { height: 8.4in; width: 8.4in; margin: 0 auto !important; }
    .landscape .custom.nomargins { height: 11in !important; width: 11in !important; }
    .landscape .custom.nomargins.pageSafari { height: 9.32in !important; width: 9.32in !important; }
    /*custom end*/

Changes to printOverlayTemplate.html (last line "Custom" is the only change):

    <select data-pcc-select="paperSize" class="pcc-print-select">
        <!-- US and International-->
        <option value="letter"><%= paperSizes.letter %></option>
        <option value="legal"><%= paperSizes.legal %></option>
        <option value="tabloid"><%= paperSizes.tabloid %></option>
        <option value="foolscap"><%= paperSizes.foolscap %></option>
        <!-- A formats-->
        <option value="a3"><%= paperSizes.a3 %></option>
        <option value="a4"><%= paperSizes.a4 %></option>
        <option value="a5"><%= paperSizes.a5 %></option>
        <!-- Architectural-->
        <option value="a6"><%= paperSizes.a6 %></option>
        <option value="a"><%= paperSizes.a %></option>
        <option value="b"><%= paperSizes.b %></option>
        <option value="c"><%= paperSizes.c %></option>
        <option value="d"><%= paperSizes.d %></option>
        <option value="e"><%= paperSizes.e %></option>
        <option value="e1"><%= paperSizes.e1 %></option>
            
        <option value="custom">Custom</option>
    </select>

Additionally, if you would like to change the default selected page size you can add selected to it as follows:

<option value=\"a4\" selected><%= paperSizes.a4 %></option>
Question

PAS appears to be unable to retrieve my document. What could be the issue?

Answer

If PAS is trying to retrieve documents from a source with a bad SSL certificate or a self-signed certificate and it is not configured to allow bad SSL certificates, it will fail to retrieve the document and log a generic 580 error.

For more information about Viewing Session creation parameters, including acceptBadSslCertificate see here:

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

Question

My PrizmDoc Cloud hosted server is reporting as unlicensed even though the license lease file is being written to the S3 bucket, what could be causing this?

Answer

This issue can occur when using a single S3 bucket for both licensing files as well as additional document storage. When our cloud licensing module attempts to search for the expected lease file inside of this S3 bucket, it requests the list of objects in that directory. However, whenever there are more than 1,000 objects in this bucket, this call only returns a list of the first 1,000 objects.

If there are over 1,000 objects in the bucket, then this could cause the Licensing Service to not see the license lease file when it gets the list of files. The result is that no lease file is found, which in turn causes the service to go unlicensed.

The solution for this issue is to make sure the bucket you are using for licensing is only used for that purpose. Should you encounter this issue, try moving all other files out of the bucket. If that is not possible, you may need to contact Accusoft Support to request changing the bucket your license uses for licensing.

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

Why does my markupBurner call with XML data get an InvalidJson error?

Answer

The MarkupBurner accepts two types of payloads, XML and JSON.

When making a call to the markup burner with either type, you have to specify what kind of payload you are sending by specifying a Content-Type header.

For more information on MarkupBurners, see here:

https://help.accusoft.com/PrizmDoc/latest/HTML/webframe.html#pas-markup-burners.html

Question

I am a PrizmDoc Cloud customer and need to do content conversion with PrizmDoc. Do I have to do anything special to make it work?

Answer

Yes, in order to do content conversion as a PrizmDoc Cloud customer, there are a few things you need to do:

  1. Most of the information regarding how to use our content conversion service can be found here, including the requests that can be made to it.
  2. The URL the requests need to go to is api.accusoft.com, so you will need to make sure the requests for content conversion are going there.
  3. You also need to add a header to the requests as follows: acs-api-key: yourapikey.

Doing these three things will allow you to use content conversion as a PrizmDoc Cloud customer.

Question

We are using PrizmDoc and may be adding more end users, so we wanted to verify whether there is a limit to the number of viewing sessions that can be active at one time.

Answer

PrizmDoc does not specifically limit the number of viewing sessions that can be active at any given time. However, when opening a viewing session with a document, a conversion does take place. The number of conversions that can be handled simultaneously is based on the hardware constraints of your server.

Various factors, such as the size of documents, the number of conversions, and the hardware being utilized may impact the performance of your PrizmDoc server.

We provide server sizing and performance documentation that is designed to provide guidance and approximate server size based on the number of conversions you plan to do per minute.

Please refer to our documentation page:

https://help.accusoft.com/PrizmDoc/latest/HTML/webframe.html#prizmdoc-server-sizing-servers.html

Question

How can I make significant changes to the UI of a PrizmDoc sample?

Answer

While jQuery can be used to make some small changes to the samples UI, it does not always make sense to make your changes programmatically on the front-end.

In this case, you will want to make your UI changes to the HTML templates used to compile the template that is passed in during viewer initialization.

To make changes and recompile the templates, you can utilize the following GitHub repository:

https://github.com/Accusoft/prizmdoc-viewer

Question

Why am I receiving a 500 error when making a Viewing Session PUT request?

Answer

This issue can occur if you forget to prefix the {viewingSessionId} portion of the URL with u, or if you simply request an invalid {viewingSessionId} in the call.

For example, the PUT call should look like the following:

PUT /ViewingSession/u{viewingSessionId}/SourceFile

For more information on syntax and other API calls related to Viewing sessions, please see:

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