Technical FAQs

Question

When I try to install PrizmDoc Server on Windows, my username/password are rejected as incorrect. How can I troubleshoot this?

Answer

It’s possible that there is some problem with the account you’re trying to log in under.

First, make sure the server is in the same domain as the username you login with. For example, if you are logging in under abc.com\flastname, ensure that your server is also a part of the abc.com domain.

Second, do a “whoami” from the command prompt – verify the id that comes up is in the local admins group (Control Panel -> All Control Panel Items -> Administrative Tools -> Computer Management -> Local Users and Groups -> Groups -> Administrators). You need to be a local admin in order to install the product.

Third, if none of the above work, you can type the password into Notepad and copy from Notepad into the installer. Sometimes the installer has difficulties with text copied directly from web browsers. Copying from Notepad resolves this issue.

If none of the above work, then as a workaround, try creating a new local account: (Settings App -> Accounts -> Other People -> “Add someone else…” -> “I don’t have this person’s sign-in information” -> “Add a user without a Microsoft account”) You can then enter the new credentials you just created into the PrizmDoc installer. Once the services are running, you can change the login information back to the desired administrator account (Services -> Prizm (Double click) -> Log on -> This account). You’ll want to repeat this for all three services (Prizm, Prizm Application Services, and PrizmDemo).

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!

Question

We are planning to upgrade our PrizmDoc Server and PrizmDoc Client to the latest major version. What is the best practice for doing so?

Answer

For best results, you will want to follow the instructions below to ensure the cleanest upgrade of the newest version:

NOTE: Before starting, make a backup of the following configuration files for use as reference when re-configuring your new version installation. This should be done before the PrizmDoc installer is run, as all configuration files will be replaced with new ones (resetting them to their default configuration).

  • Prizm Server Configuration: prizm\prizm-services-config.yml

  • Prizm Client Configuration (Windows): prizm\pas\pcc.win.yml

  • Prizm Client Configuration (Linux): /usr/share/prizm/pas/pcc.nix.yml

  • ServiceHost Configuration: prizm\PCCIS\ServiceHost\pcc.config

How To:

  1. Uninstall the previous version of PrizmDoc Server and PrizmDoc Client. Be sure to delete all PrizmDoc folders that are still present. For Windows you can Find PrizmDoc Server and Prizm Client under Add/Remove Programs. For Linux, please follow instructions below for uninstall instructions.

Linux Prizm/PAS Service Uninstall:

https://help.accusoft.com/PrizmDoc/latest/HTML/webframe.html#linux-uninstall-prizmdoc-serve.html

https://help.accusoft.com/PrizmDoc/v13.10/HTML/webframe.html#pas-linux-uninstallation.html

  1. Download the latest version of PrizmDoc for your operating system from https://www.accusoft.com/products/prizmdoc-suite/prizmdoc-viewer-builds/

  2. Install PrizmDoc Server first and then the PrizmDoc Client.

  3. At the end of the server installation, the install may request a reboot.

  4. Make a backup of your new configuration files as listed above.

  5. Modify each of the new configuration files and make the same changes as you did in the older configuration files.

NOTE: Do not just replace the new configuration files with the old version configuration files, as new configurations may have been introduced in the new version and they would be lost.

  1. Restart the Prizm Services and Prizm Application Services to ensure the newly configured file changes take affect.

NOTE: If either service fails to start with an error after modifying the configuration files, replace the configuration files with the original copy of the configuration files and try making the changes again.

NOTE: If you are using viewing packages and have an existing database, we provide additional scripts in the \prizm\pas\db folder to modify your existing database. For example, upgrading from PrizmDoc 12.x to PrizmDoc 13.x we provide an additional script addTenantId to add a new field to one of the existing tables.

digital vault application

Security is everything for organizations when it comes to their sensitive data assets. Whether it’s vital documents, account passwords, or proprietary financial formulas, essential business information needs to be well-protected as companies continue to incorporate digital platforms into their operations. Developers can support this critical goal by providing secure digital vault applications that allow their customers to manage and use information assets without exposing them to unnecessary risks.

The heightened emphasis on security has made digital vault services quite popular in recent years. In order to maximize the potential of these security platforms, however, developers must integrate the right tools for managing multiple file types ranging from standard documents to complex financial spreadsheets.

What is a Digital Vault?

Much like its physical counterpart, a digital vault is a secure repository for storing vital assets in one easy-to-manage and fully-encrypted location. In some respects, these platforms are similar to information management services or cloud-based storage, but they set themselves apart by emphasizing security and access control. Digital vaults are frequently used for estate planning thanks to their ability to securely store account log-in information and vital documents, but they’re also popular with high-net worth individuals and organizations that need a safe place for sensitive financial data.

The core feature of a digital vault is its ability to prevent unauthorized access to materials stored inside them. They do this by strictly monitoring access rights at multiple levels. Just because someone has access to the vault itself, for instance, doesn’t mean they have access to everything it contains. The files and documents stored within the digital vault can all be set with their own access permissions. These controls mirror those used in a physical bank vault, such as:

  • Requiring manual authorization from an administrator to access data.
  • Implementing dual key control mechanisms.
  • Limiting access to certain times of day.
  • Segmenting access to relevant assets only.

Managing Digital Vault Information

Digital vaults also make the process of managing data much more secure. Since all of the assets stored within the vault are protected by encryption, they can be shared through a portal rather than downloaded, copied, or transmitted over poorly secured channels like email. The data itself never leaves the protective confines of the vault, and the security controls track who has been granted access when files are shared. This makes it easy to monitor activity and ensure that confidential files are not broadly distributed.

In order to facilitate this access, however, digital vault developers need to build viewing and editing tools into their applications. Without the ability to open and view a document within the web-based portal, for instance, users will be forced to rely on external software. This defeats the whole purpose of a digital vault, as it exposes the file to whatever security vulnerabilities that application might possess.

Integrating HTML5 viewing capabilities into their vault’s web portal allows developers to let their customers review documents and even make annotation markups without having to remove the file from a secure, encrypted environment. For most documents and images, this is a relatively straightforward process using a series of API calls to render the file within the browser.

The Challenge of Excel Spreadsheets

Microsoft Excel spreadsheets, however, frequently pose a major challenge to digital vault platforms. Unlike documents, spreadsheets are often designed to be interactive and can contain sensitive financial calculations within cell fields. Simply sharing a static, print preview image of a spreadsheet might be helpful for reviewing financial records, but it’s not very useful to someone who needs to enter fresh data into the formulas to calculate new results.

While the XLSX file could be made available for download to anyone who is authorized to use it, this defeats the purpose of having it stored in a digital vault. Not only would it be impossible to track the downloaded file, which creates serious data security risks, but allowing multiple copies of the file to proliferate will quickly lead to version confusion.

Enhancing Spreadsheet Functionality with PrizmDoc Cells

Digital vault developers can easily solve their spreadsheet challenges by integrating Accusoft’s PrizmDoc Cells into their application. A completely web-based spreadsheet viewer and editor, PrizmDoc Cells provides native XLSX file support without any external dependencies. The API-based integration allows users to open their existing Excel files to view, edit, and add comments completely within the application’s web portal. PrizmDoc Cells provides a familiar interface that developers can customize to meet the specific needs of their customers.

That same customization extends to the spreadsheet elements themselves. A digital vault provider may not want to allow users to have full access to every element of an Excel file. For instance, an organization may be fine with allowing someone to enter new data and calculate results in the spreadsheet, but not want anyone to be able to view the proprietary formulas buried within the cell fields. When integrating PrizmDoc Cells, developers can control what aspects of the XLSX file are actually shared. This makes it easy to keep formulas and other data locked in place within the spreadsheet and secure from unauthorized viewing.

Unlock Your Digital Vault’s Potential with PrizmDoc Cells

Accusoft’s PrizmDoc Cells gives digital vault developers the ability to control how spreadsheet files are shared and managed within their secure application environment. By integrating native Excel support, they can sever their dependency on Microsoft Office and other potentially insecure software platforms and enhance the value of their digital vault services. With PrizmDoc Cells, their customers can easily access, review, and edit their spreadsheets without exposing them to additional security risks or version confusion.

To learn more about the versatile functionality of PrizmDoc Cells, check out our detailed fact sheet for an overview of critical features and use cases. If you’re ready to test the integration in your application environment, download a free trial today in an easy-to-deploy Docker file.

legaltech legal workflow automation

Legal organizations faced tremendous challenges in 2020 due to the impacts of COVID-19. Firms and departments rapidly transitioned to remote work environments and were forced to rely upon their established technology resources more than ever before. While the industry fared better than many others, the experience has caused organizations to rethink their longstanding business models and workflow processes. As firms consider what steps to take in 2021 and beyond, LegalTech developers must be closely attuned to the pressures informing those decisions so they can provide the software to support automation in law firms.

The research firm Gartner provided a glimpse into those pressures in a 2020 survey focused on legal spending trends. Their findings reveal an industry in transition as legal organizations increasingly work to expand their internal capabilities, improve legal document automation, and reduce reliance on outside spending. LegalTech developers are uniquely positioned to facilitate this inward turn with versatile legal workflow automation software.

Turning Weaknesses Into Strengths

The COVID-19 pandemic forced law firms and legal departments to take notice of organizational shortcomings that often escaped notice in previous years. According to Gartner research, the biggest area of concern was by far technology solutions. Some organizations found themselves saddled with legacy systems that lacked the robust feature set of modern LegalTech applications. Others, however, wisely made the investment in new software over the last decade, but those systems have not been fully adopted by legal personnel. This echoes the results from a 2020 Accusoft survey that found over 40 percent of firms are still relying on inefficient manual processes for document assembly, discovery, signature gathering, redaction, and contract management. 

For LegalTech developers, these twin shortcomings present a tremendous opportunity. Legal organizations will be in need of technology solutions that help them to automate low-value tasks and enhance collaboration capabilities while also looking to secure broader acceptance and buy-in from employees. That means delivering a streamlined, intuitive user experience will be every bit as important as integrating the latest legal workflow automation software.

Identifying Opportunities

The LegalTech market is a diverse and rapidly growing field that consists of multiple technology solutions. Gartner’s 2020 research into legal organizations offers a helpful snapshot of how far these firms and departments have to go when it comes to legal technology adoption and automation in law firms:

  • E-Billing: 48 percent
  • Contract LIfecycle Management: 44 percent
  • Document Management: 40 percent
  • eDiscovery: 33 percent
  • Records Management: 28 percent

Although overall legal spend did not change substantially from 2019 to 2020, the pandemic has caused firms to shift resources away from outsourced services and toward their in-house capabilities. With nearly a third of organizations looking to accelerate their technology, there are significant opportunities for LegalTech developers to deliver efficient and cost-effective solutions. Contract automation tools, document management platforms, and eDiscovery applications will all be in high demand thanks to their ability to help firms enhance their productivity and scale services in a sustainable fashion.

Improving Implementation

Understanding the work culture and processes of a legal organization is critical to any successful technology implementation. Without that knowledge, developers can end up building a solution that doesn’t meet a customer’s needs or is too removed from existing workflows to be easily adopted. This problem was quite pronounced in the early days of LegalTech software, when many legal professionals still had doubts about the usefulness of technology.

Communication between developers and legal departments is quickly improving, however. From 2018 to 2020, the number of organizations with a legal operations manager in place increased by 75.8 percent. In 40 percent of firms, that role is filled by a non-lawyer who is better equipped to facilitate conversations between software developers and internal stakeholders.

LegalTech developers can use this channel to get a better idea of how they can implement solutions like legal document automation through an organization’s existing technology stack with minimal disruption. They can also begin to address specific internal pain points and match those needs to the right software integrations to round out their application’s functionality. Versatile SDK and API integrations will play a crucial role in meeting these needs because developers may have to build out customized feature sets to provide the ideal capabilities.

Doing More with Less

Developers with the ability to build out customizable, flexible software applications can also help legal customers to eliminate redundant or outdated solutions they already have in place. There’s no reason for a firm to rely on one program for assembling documents, another for viewing and redlining them, and yet another for redacting them to protect privacy. With the right software integrations, LegalTech developers can build core productivity features into their platforms quickly and easily. They can then offer a comprehensive solution that solves multiple customer needs and allows them to incorporate more of their workflows into a comprehensive, secure application environment.

This consolidation of LegalTech capabilities will continue to be important as all but the largest legal organizations transition toward a more customer service-oriented business model that emphasizes competitive, transparent pricing and “off-the-shelf” legal services. Legal collaboration will increasingly expand to include the firm’s clients, which makes the adoption of easily-accessible web applications more important than ever. An ideal LegalTech solution will allow legal teams to share information easily, quickly, and securely with people inside and outside their organization. Developers can build the applications that make this possible, ushering in a new era of transparency, collaboration, and efficiency that will help firms continue to grow.

Choosing the Right Integrations

Accusoft’s collection of SDK and API integrations have long helped LegalTech developers incorporate the powerful features their customers are looking for into their applications. By turning to contract assembly tools like PrizmDoc Editor or the legal document automation capabilities of Barcode Xpress, software teams can quickly implement core functionality while dedicating the bulk of their resources to building innovative new features that will set their product apart in a crowded market. 

The benefits of selecting the right integration partner are particularly evident when looking at eDiscovery applications. Developing a comprehensive LegalTech eDiscovery platform requires a wide-range of viewing, annotation, comparison, conversion, search, and redaction options. Building those features from scratch can extend development timelines by months, which could potentially cost a software developer their chance to break into a highly competitive market. With an API integration like PrizmDoc Viewer, however, they can rapidly integrate proven features into their application to help deliver better performance to customers while also getting to market faster and saving valuable resources that may be needed elsewhere during the development cycle. 

To learn more about how Accusoft’s family of SDK and API integrations can transform your LegalTech application and improve automation in law firms, have a look at our LegalTech Fact Sheet and match the right solution to your development needs.

Implementing any technology solution within an established organization can be a monumental challenge for a developer. Doing so for a legal firm that has a strong culture and longstanding processes can be even more difficult. That’s why LegalTech developers need to take a few key factors into consideration as they work on applications for the legal industry.

Build vs. Buy

One of the first questions any firm needs to ask is whether it wants to build a specialized solution or turn to an existing LegalTech application. In many cases, this comes down to a question of resources. For larger “big law” firms or legal departments within an enterprise business, internal developers may be available to build a customized application that caters to specific organizational needs. 

If the resources and development skills are on hand, building a dedicated solution can be an effective strategy. Developers can focus narrowly on the established processes used at the firm and design technology that targets clear pain points more effectively than an “off-the-shelf” product.

More importantly, as Kelly Wehbi, Head of Product for Gravity Stack, points out, building doesn’t necessarily mean starting from nothing

“I think a lot about how to leverage the platforms we have or could potentially purchase, but then add our own expertise and strengths on top of it. That doesn’t have to mean you have to build some entirely new interface or have to invent some new technology. It could be there’s a tool that’s out there that does exactly what you need and maybe you have to build a few customizations on top of that.”

Of course, building a solution also presents a number of challenges, especially if the project’s requirements are not well defined from the beginning. There’s a great deal of overhead involved with building new technology in terms of maintenance and ongoing support. It’s easy to fall into the trap of focusing on technology at the expense of services. But legal firms are not product companies; they need to focus instead on finding ways they can use technology to leverage their core services.

It’s that emphasis on services that drives many firms to buy the technology solutions they need rather than to build them. Existing software integrations are typically better positioned to maintain security and don’t need to be maintained as extensively. Deploying proven software integrations also helps organizations to maximize their on-premises resources and enhance their flexibility in the long-term. 

“I tend to default toward leveraging an existing platform when possible,” Wehbi admits. “Security ends up being a huge part of this and when you can leverage a company that’s solved that really well, that goes a long, long way. It offers you a bunch of options you wouldn’t have if you had to build it yourself,” Wehbi says. “That’s a pretty big undertaking to start from scratch.”

Getting Buy-In for LegalTech Solutions

Once the build or buy decision is finally made, there’s still the critical matter of executing and putting the new solution into practice. Getting feedback throughout the development and integration process is important, whether it’s gathered from anecdotal observations or some form of usage analytics. 

Neeraj Raijpal, CIO at Schroock & Schroock & Lavan, finds that implementations tend to go smoother when the development team is able to get rapid feedback from key decision makers: “The faster you get the feedback, the faster you know you’re down the right path or not. It is very frightening when the stakeholder…looks at something and says ‘This is exactly the opposite of what I expected.’ You don’t want to be in that situation.”

Ultimately, a LegalTech application’s success depends largely upon whether or not the firm as a whole embraces it. When developers are seeking to implement a solution, they need to be especially careful to take the culture of the firm into consideration. Without buy-in at the top, it will be difficult to convince anyone in the organization to commit to change. 

“If you’re trying to solve a problem because you have a deficiency in a current business process, but you’re not willing to change the process…that’s (a) disaster,” Raijpal warns. Although LegalTech solutions are designed to enhance efficiency and reduce errors, they often require people to learn how to use them or to abandon existing technology solutions.

Take, for example, a legal firm that needs to redact documents during the discovery process. The existing process likely involves printing out documents and then laboriously redacting them by hand with marker. Once that process is finished, they are scanned and saved as image-based PDFs. An HTML5 viewer with redaction capabilities could easily streamline this process to make it faster, more flexible, and more secure. Unfortunately, if the firm’s attorneys aren’t willing to adopt the new process, all of the potential efficiency benefits go to waste.

The Importance of Communication

Communication and ongoing support are critical to ensuring a successful LegalTech implementation. Developers can begin this important conversation right from the beginning when they’re designing application features. Whether they’re building everything from scratch or turning to software integrations, they need to have honest and thorough discussions to determine what specific features are needed to support legal processes. Implementing a LegalTech solution is more likely to be successful if that solution is closely aligned with the firm’s existing needs and future goals.

But the conversation doesn’t stop once the application goes live. Ongoing support and education is often necessary to help firms adopt new technology and make the most of its potential. Developers may even need to adjust some features over time as needs change. If they utilized third party software integrations to add key functionality, they need to know they can count on those vendors to support them as the LegalTech application evolves.

Make Your LegalTech Implementation a Success with Accusoft

Accusoft’s family of software integrations allow LegalTech developers to quickly add the features their clients need to modernize workflows and improve efficiency. Whether it’s PrizmDoc’s extensive document redaction capabilities that make it easier to protect privacy during eDiscovery or the automated document assembly features of PrizmDoc, developers can lean on our 30 years of document processing expertise so they can focus on building the tools legal teams require

As part of our ongoing work with the LegalTech industry, Accusoft recently sponsored a Law.com webinar on the subject of building vs buying technology solutions for legal firms. You can listen to some of the highlights with contributors Kelly Wehbi and Neeraj Rajpal along with host Zach Warren, editor-in-chief of LegalTech News, on the Law.com Perspectives podcast.

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.

In part one of our series on how APIs are empowering a new generation of LegalTech solutions, we looked at some of the technology obstacles facing today’s legal organizations. We also covered the basic principles of how API integration works and how it can bridge the gap between legacy systems and new applications. In part two, we’ll be taking a closer look at some specific API integration use cases and explain why they’re an essential part of a successful firm’s LegalTech toolkit.

4 Benefits of APIs for Legal Teams

Before going into more detail about how LegalTech API integration works, it’s worth highlighting the broad benefits APIs can deliver to a law firm. 

1. Streamlined Workflows

The average legal department relies on more than one software solution to meet their business needs. While larger firms that provide a broad range of legal services typically require more specialized platforms, even smaller legal teams deploy different software applications to address different business needs.

Thanks to API functionality, these diverse LegalTech solutions can be integrated into a single, platform-agnostic portal that eliminates the workflow disruption caused by constantly switching back and forth between programs. 

2. Remote Functionality

API integrations also make it possible for lawyers to access an assortment of LegalTech tools from any location, even if they can’t physically be at their offices. This capability is more important than ever as the legal profession continues to grapple with the impact of the COVID 19 pandemic. 

Many lawyers are still working from home and communicating with their clients and colleagues remotely. In some states, virtual court proceedings might remain in use even after the pandemic. If law practices aren’t able to function effectively in a remote context, they will struggle to deliver quality legal services to their clients.

3. Competitive Advantage

Managing multiple technology resources and facilitating remote collaboration isn’t just about making work easier for legal teams. Streamlining workflows results in greater efficiency, which means lawyers can spend more time doing high-value work for their clients rather than sorting out technical issues or tracking down hard-to-find documents and files. 

It also translates into reduced costs, since key administrative functions can be automated and carried out both faster and more accurately. Law firms that invest in technology integration can deliver better services to their clients at lower costs than their competition while still retaining the flexibility to adapt to future disruptions.

4. Enhanced Security

By its very nature, the legal industry ends up handling a great deal of sensitive information. Financial records, contracts, protected health data, and private correspondence are frequently relevant to legal proceedings of all kinds. There’s also the matter of attorney-client privilege, which greatly restricts what information can be shared outside the firm. 

Without a way to securely manage files and documents, law firms leave themselves exposed to significant liability. Thanks to API integrations, attorneys can use their existing LegalTech solutions to access, share, and edit essential files safely and securely. 

PrizmDoc Viewer: LegalTech API Integration in Practice

For a better understanding of how API integration can enhance the performance of LegalTech applications, it’s instructive to look at some specific examples. Accusoft’s PrizmDoc Viewer uses a powerful collection of REST APIs to provide HTML5 document viewing functionality through a single interface. It not only allows LegalTech developers to quickly and easily integrate document viewing capabilities into their applications, but it also delivers several additional features that are particularly relevant to the legal industry’s eDiscovery process

Document Conversion

The digitization of the discovery process has made it easier for legal organizations to share documents and back up important data. Unfortunately, it’s also created a huge glut of electronically stored information (ESI) in a variety of formats. In addition to the large number of commonly used file formats (such as DOCX, PDF, and JPEG), firms must also deal with a variety of proprietary file formats and case-specific formats (like DICOM for healthcare clients). PrizmDoc Viewer uses an array of APIs to convert more than 100 file formats for easy presentation within a browser-based HTML5 viewer. It can also convert image-based documents into searchable PDFs or editable text files with a built-in OCR engine. Thanks to this integration, attorneys can quickly share and view documents internally or with clients and the court without having to download and install specialized applications.

Annotation

The ability to annotate and markup documents is essential for any collaborative legal process. Although many platforms make it easy to insert comments and edits into documents, these programs often don’t support more than a handful of file types and alter the original file when making annotations. PrizmDoc Viewer’s annotation functionality supports over 100 file types and allows multiple users to make layered edits that can be easily shown or hidden. More importantly, all markups exist on top of the original document, preserving the integrity of the original file to comply with state and federal preservation of data requirements. When the time comes to present documents, annotations can be burned into the file if necessary. 

Redaction

Sharing documents is always a sensitive process in the legal profession. Information may be protected by attorney-client privilege, disclosure agreements, contractual obligations, or government regulations. LegalTech applications need to be able to redact sensitive data when sharing documents with outside parties. PrizmDoc Viewer’s REST API allows users to manually redact individual sections, use search features to redact specific terms, or even programmatically redact data for pre-determined reasons (such as account numbers or Social Security numbers). Redacted content is not only hidden from view, but no longer shows up in search results and cannot be copied or highlighted.

Security

As mentioned previously, security should be a key consideration for any LegalTech solution. Firms need to strictly control who has access to data and confidential documents, whether that consists of sensitive client information or internal litigation strategies. PrizmDoc Viewer provides a few key features to help LegalTech applications maintain high levels of security.

  • DRM: Digital rights management (DRM) controls can manage who has access to documents and what functions they can use (such as printing, downloading, or viewing). This makes it easy to restrict how files are shared and track any document leaks back to their source to hold the responsible parties accountable.
  • Watermarking: PrizmDoc Viewer can hard code identifying information into documents to prove ownership and prevent the unauthorized reproduction of documentation.
  • Encryption: With so many people working remotely from potentially unsecured Internet connections, file encryption is absolutely essential for any LegalTech application. PrizmDoc Viewer uses 256-bit AES content encryption to ensure that documents remain secure throughout the collaboration process.

Transform Your LegalTech Strategy with API Integration

As we covered in part one, many legal organizations cling to outdated processes and technology due to familiarity and deeply-ingrained status quo bias. But familiar doesn’t always mean functional. Over reliance on manual processes exposes firms to increased human error and a range of potential data security risks, to say nothing of undercutting productivity. Advanced APIs offer a new tactical toolkit, a way to select best-fit code that solves specific issues and helps legal firms improve operational outcomes. Learn more about how Accusoft’s PrizmDoc Viewer can unlock the full potential of your LegalTech applications today.

Gain Peace of Mind with GDPR Compliant Document Viewing Tool for Secure Collaboration

These days there is a heightened awareness of the risk of opportunity for a data breach or cyber attack. Whether the spike in attention came from a global pandemic, brink of international war, or an unknown hacker that set its sights on Elon Musk, there is a general consensus that our personal data is at risk at any point through a breach of security.  This becomes more potent for companies as the cost of such insecurity could potentially end its tenure.  According to an IBM Data Breach Report, 2021 had the highest average data breach cost in a 17-year history of $4.24M. Securing data and maintaining an individual’s privacy is a priority for many organizations throughout the world, but following a strict standard has only been attempted by the European Union (EU) thus far.  

The EU has taken this priority a step further than just suggesting companies and organizations increase data protection – since 2018, they’ve mandated and enforced specific requirements through the General Data Protection Regulation (GDPR). Given the broad parameters covered under GDPR compliance, ensuring the standards are met can become a time-consuming, stressful and ongoing issue if not resourced properly.  The parameters go beyond the protection of personal data and go as far as requirements, to prove security measures are set in place.  

Who Needs to Maintain GDPR Compliance?

While often only associated within the European Union, the requirements and legislation of the GDPR extend as far as all “entities who are offering goods or services to anyone residing in the EU (even if those services are provided free of cost).  Any global business either has to become compliant for all of its users/customers or be able to accurately identify EU residents and enable compliant systems to handle only that subset of the customer base.”

GDPR requires companies to know the following as related to personal data:

  • What personal data is being shared 
  • Where it is being shared 
  • How it can be deleted at a moment’s notice if necessary

The GDPR also highly encourages that an organization designates an employee to be the point of contact and in control of the data security processes and systems to maintain compliance.  A first step to having an effective process in place is choosing the right tools with security features to protect data being shared within the company.

Managing Risk through Secure Document Viewing

As risk management becomes an essential part of strategic planning, the importance of IT security and data encryption skyrockets to the top of priorities for most companies. GDPR suggests encryption as a means to manage risk in file sharing but does not outline explicit instruction.  With PrizmDoc™ Viewer, companies gain added data security, aligned with GDPR compliance, in document viewing and sharing without heavy client-side installations or downloads. 

PrizmDoc™ Viewer is created with Multi-Level Data Protection including:

  • 256-bit AES encryption 
    • (Advanced Encryption Standard) is an international standard that ensures data is encrypted/decrypted following this approved standard. It ensures high security and is adopted by the U.S. government and other intelligence organizations across the world.
  • Configurable user permissions add a strong measure of privacy and protection to document content.

A Simple Path to Secure Document Sharing

Remote work or not – collaborating on a project today means sharing documents among many colleagues to finalize a document, project, or presentation. To do that with security in mind, organizations are cobbling together tech stacks to meet their productivity needs along the way, and several different file types can come across their desks in a single day.  

PrizmDoc™ Viewer integrates into your current application to render and display a multitude of file types with high fidelity and speed.  The ease of use features include:

  • Flexible use across many platforms
  • A self-hosted version that resides on any organization’s servers
  • Empowers developers to provide their users with responsive file viewing
  • Search and redaction can be easily turned on/off

PrizmDoc Viewer is also designed to run on all devices with a zero-footprint viewer that makes it easy for employees to work where and how they wish. The white label services give an organization the flexibility to brand and customize while gaining peace of mind in data security.

Open and View an Image Securely the First Time

While documents have a range of formats from Word, PDF, spreadsheets, and more – images are often more of a culprit when it comes to difficulty viewing, let alone being able to download, edit, markup, or save information as a separate file. Workers find themselves quickly downloading a media player just to open the image.  Having multiple solutions in place is not only confusing, but it also contributes to inefficiency and human error which means added risk for images to remain secure. 

As photographs can constitute personal data under the GDPR, this means organizations must be able to quickly and easily remove all images where the individual can be identified.  

With ImageGear, an organization is able to add powerful image processing capabilities that enhance secure collaboration such as:

  • PDF manipulation that includes managing access with digital signatures for added security levels
  • The image processing library offers developers a set of methods for modifying an image including to resize, crop, merge, rotate, and flip.
  • An option to add OCR for document search and data capture support

Getting Started 

To quickly gain peace of mind with secure collaboration, contact us today

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.