Technical FAQs

Question

I would like to be able to query my PrizmDoc Server for all documents currently in a state of processing. I want to be able to do this to determine if a document is “hanging” during conversion, to determine my system’s efficiency (My RAM and CPU are at X% with ten documents converting), or for other tasks. This is currently possible for individual processes if you know the process ID. Is this possible for all processes?

Answer

The current version of PrizmDoc does not have an API to determine if any file is currently converting on PrizmDoc Server. PrizmDoc provides viewingPackageCreator, contentConverter, redactionCreator, and markupBurner APIs that report the status of a specific process, and whether it is in progress or not. However, it is currently necessary to know a specific processId to obtain that information.

There is an active Feature Request for this item available for viewing here.

Question

We are running PrizmDoc on a Windows operating system and we noticed that our ms-office-conversion-service remained unhealthy even through a restart of the service. We also noticed an error in the MsOfficeConverter.log referencing the following error. What could be the cause?

“WARN – COM error occurs on 1 initialization attempt. Retrieving the
COM class factory for component with CLSID
{000209FF-0000-0000-C000-000000000046} failed due to the following
error: 80080005 Server execution failed (Exception from HRESULT:
0x80080005 (CO_E_SERVER_EXEC_FAILURE))”

Answer

The PrizmDoc MSO feature requires either Microsoft Office 2013 or 2016 to be installed in order to function properly. Based on the error, there is a Microsoft Office specific .dll file which is not registered properly.

The following process will re-register the .dll files and potentially resolve this issue (Note: for Step 2, this may vary depending on what directory you used to install Microsoft Office and the version of Office. You want to find the directory containing winword.exe):

  1. Run Command Prompt as Admin.
  2. Type cd C:\Program Files\Microsoft Office\Office15 or cd C:\Program Files\Microsoft Office\root\Office16
  3. Run winword.exe -regserver.
  4. Reboot the server.

If you don’t have the Prizm service set up to run on boot then make sure that Office applications are started by PrizmDoc, or from the command line, before being opened manually.

Question

Can we give network paths for source document location as well?

For example //10.216.2.312/test/test.doc

https://help.accusoft.com/PrizmDoc/latest/HTML/webframe.html#Transfer_Your_Document_to_PrizmDoc_Server.html.

When using http URL, for security reasons, only absolute paths are allowed, but could you map test to documents and use a local file?

Answer

Documents are stored by default in:

C:\ProgramData\Accusoft\Prizm\Documents 

so if the type in the request for source is document it will look in that folder. The configuration for that is set in PAS config:

    {
        "source": {
            "type": "document",
            "fileName": "1040ez.pdf"
        }
    }
Question

I have already licensed PrizmDoc. Where can I find my license key?

Answer

At the very top of the prizm-services-config.yml file located at C:/Prizm/ on Windows and /usr/share/prizm/ on Linux, you can locate the license key:

######################### PrizmDoc Configuration ###############################

############################### Licensing ######################################

license.solutionName: ________
license.key: 2.0...
Question

I changed the value of viewingSessionTimeout

Answer

If you are using Windows, the value that you are looking to modify is the viewing.sessionLifetime in the central config file prizm-services-config.yml located in the root of the PrizmDoc installation directory (C:\Prizm on Windows, /usr/share/prizm on Linux).

Make sure it is uncommented and without any leading whitespace.

Additionally, please make sure the viewing.cacheLifetime is greater than the viewing.sessionLifetime value.

More information can be found here.

You must restart the PrizmDoc service in order for your changes to take affect.

Question

By default, in the PrizmDoc Viewer, links are highlighted and underlined in blue. To follow links within a document, the user needs to click the link, wait for the floating popup to appear showing the link’s target URL, and then click that to actually follow the link. Is there a way to make this a single-click process and skip the floating popup?

Answer

The desired one-click functionality can be achieved by modifying the viewer.js source file:

Inspect around line ~9457; you’ll find the following else if block:

    } else if (ev.targetType === "documentHyperlink") {
        hyperlinkMenuHandler(ev, "view");
    }

This line of code executes when the user clicks on a link displayed within the Viewer. The call to hyperlinkMenuHandler is responsible for displaying the floating popup. If you’d like to immediately open the link in a new window/tab instead, replace the contents of the “if else” block with a call to window.open:

    } else if (ev.targetType === "documentHyperlink") {
        window.open(ev.hyperlink.href, '_blank');
    }

This will allow hyperlinks that appear in the Viewer to be followed in a new window/tab with a single-click.

Question

If I upload an HTML document to PrizmDoc that has image tags in it, will those images be rendered in the Viewer or will only the text be displayed?

What if the image tags are referencing local images?

Answer

When loading an HTML file, PrizmDoc will render image tags that are sourced from publicly accessible URLs. The relative links may not render though, as it’s likely that the source will not be found.

In PrizmDoc 13.2, a server-side configuration option called:

security.htmlRendering.blockExternalContent

was introduced to control whether or not externally-referenced HTML content will be blocked.

See the release notes for more information.

While digital transformation initiatives have been climbing the FinTech priority list for years, Eli Rosner of Finastra notes that thanks to COVID-19, “It feels like the fast forward button has been pressed.” Firms must now embrace the realities of remote work and rising consumer expectations even as investor patience wears thin on reliable ROI.

The result is a FinTech landscape that’s more than meets the eye. To deliver on transformative deployments, companies must look past familiar fintech trends to uncover key challenges, assess acceleration issues, and recognize the realities of digital revolution.

The Challenges of Change for FinTech Companies

FinTech solutions emerged as harbingers of change. Frustrated by restrictive policies and cumbersome processes, financial technology companies embraced the market reality of application-driven enterprises capable of meeting consumers on their own terms. But even these tech-first solutions couldn’t predict current challenges. As noted by recent Deloitte research, FinTech firms now face both external and internal barriers to effective change.

Externally, investors remain an ongoing challenge as their patience for digital revenue delivery wears thin. While they recognize the need for transformative spend, they’re not willing to wait years on steady returns. Internally, lacking enterprise agility now hampers the ability of finance technology firms to deploy new partnerships and coordinate digital innovation at scale. Changing market forces are creating unprecedented challenges for FinTech firms.

The Acceleration of Adoption

Even as enterprises grapple with evolving change frameworks, the global pandemic continues to push companies out of their comfort zone, forcing firms to quickly implement multichannel solutions capable of connecting with customers anywhere, anytime. Consider that 35 percent of banking customers have embraced more online options, while contactless credit card payments have jumped by 40 percent over the past few months.  

In effect, the COVID-19 crisis has revealed a need for speed that’s far beyond the comfort zone of many FinTech firms. The result of this adoption acceleration is equal parts potential and problem. Companies can’t afford to slow down, but need a better view of what lies ahead.

The Realities of Revolution

To overcome emerging challenges and embrace agile application adoption at speed, FinTech firms must leverage a two-step process that first recognizes the real-life impact of digital revolutions and then deploys specific solutions to improve operational outcomes.

In practice, this means addressing four new realities:  

  1. Customer-First Frameworks

As noted by Deloitte, the shift to customer centricity is often viewed as an enabler. If companies are able to deliver seamless, client-first experiences through common digital channels, they can significantly raise their reputational stock with consumers. But it’s one thing to recognize the reality of customer-first frameworks and another to implement them at scale. Here, fintech firms are best-served with workflow automation tools capable of streamlining key processes — such as loan applications and credit checks — to help reduce the time between customer inquiry and response.

  1. Complex Document Functions

With clients and staff now working and interacting remotely, FinTech firms are facing a substantive uptick in the volume and variety of digital documents they receive — and they need to process ASAP. Here, complexity itself doesn’t represent the full spectrum of change, since regulatory and compliance controls are familiar challenges for FinTech companies. Instead, it’s the velocity of complex document processing that can quickly overwhelm even experienced FinTech software as they look to process applications and approvals at speed without sacrificing security or consistency. Comprehensive, industry-compliant document management tools can help FinTech firms bridge the complexity gap.

  1. Comprehensive Data Foundations 

Spreadsheets remain essential for traditional firms and FinTech solutions alike. As data volumes grow, organizations face issues related to information-entry errors, version consistency, and data security. To ensure foundational finance data is accurately collected, consistently applied, and always protected, FinTech solutions need to deploy next-generation spreadsheet solutions capable of giving end-users the control and security they need.

Collaborative FinTech Forces

To deliver on client expectations around speed and security, FinTech solutions require SDKs that natively support document collaboration and control without introducing security risks such as unauthorized editing, downloading, or sharing. This means equipping their applications with the operational infrastructure that facilitates everything from editing and commenting to robust redaction, annotation, and file conversion.

FinTech in 2020: The Only Constant Is Change

The global business landscape in 2020 has been anything but predictable. Defined by pandemic pressures and driven by increasingly sophisticated digital initiatives, FinTech companies have managed what seemed impossible only a few years ago. They made a speedy shift to remote work that now delivers rapid customer responses while reducing overall risk.

However, it’s important to note that the market movement isn’t over. As COVID conditions continue to evolve and consumers recognize the value of advanced FinTech solutions, the only constant in FinTech industry this year is change.

There are 2 ways to password protect a document

  • Protected sheet for locked cells – we display the document as is and respect locked and hidden cells, but we don’t allow inputting the password to unlock it.
  • Password protected document for opening – we currently don’t support this use case; instead, it will fail to process the file with UnsupportedFileFormat.

developers sitting at computer

Docubee is a great no-code platform for automating your business processes. If you are a developer, we offer several ways to integrate Docubee directly into your site with straightforward APIs, and a few lines of code. If that isn’t your speed, no worries! You can learn more about how you can use Docubee code free here. Otherwise, read on!

You’ve got your perfect website and your customers know and love your unique style. With Docubee, it’s easy to use your own forms to collect data and much more. With additional effort, you could even send documents hosted on your site to Docubee and auto-populate them with data collected in a form.

To demonstrate a very simple use-case, here is a survey form in Docubee which can be used to collect and track response data. The Docubee workflow will be a very simple two step process – a web form and email step. Check out how to create a workflow template here.

 


The Docubee Workflow

Using Docubee’s fast form creator, it was easy to create a simple survey form.

Once created and published, the workflow’s form can be directly linked via URL for collecting survey data, or it can be submitted from your own site by initiating a POST request. This way you don’t need to worry about storing the data. Docubee allows you to track and export all responses.

Each field in the workflow designer has a Field Label and Property Name. The label is what shows up on the Docubee web form, and the Property Name is what the response data corresponds with in the Docubee dashboard.

So far, there are six “Single-Line Text” fields on the form, five of which have a data type of text and one of type e-mail.

(Label / Property Name)

  • What is your favorite product? / Favorite_Product
  • Why did your purchase this product? / Why_Purchase_Product
  • How satisfied are you with this product? / Product_Satisfaction
  • Would you recommend this product to a friend? / Recommend_Product
  • Would you recommend this company to a friend? / Recommend_Company
  • Your Email / Respondent_Email

The property name is also how the data is stored in the POST request body to Docubee that initiates the workflow.


The Docubee API

The workflow can be initiated from your site by having your form post to custom route on your server. The handler behind that route needs to format your forms response data to POST to the workflow instances API endpoint:

POST - https://docubee.app/api/v1/workflowInstances
Content-Type: application/json
Request Body
{
  "wfModelId": "yourModelIdHere",
  "wfData": {
    "Favorite_Product": "yourDataHere",
    "Why_Purchase_Product": "yourDataHere",
    "Product_Satisfaction": "yourDataHere",
    "Recommend_Product": "yourDataHere",
    "Recommend_Company": "yourDataHere",
    "Respondent_Email": "yourDataHere"
  }
}
Response
Content-Type: application/json
{
  "wfInstanceId": "instance-id",
  "redirectUrl": "url-if-there-is-a-next-workflow-step"
}

After a successful POST request, the workflow will be initiated with the data and a thank you email would be automatically sent to the email contained in the “Respondent_Email” property.

The survey responses can be tracked in the Docubee Dashboard under the “COMPLETED” instances tab.

All survey results can also be exported to a CSV file using the “Export Workflows” button.

 

 

Example CSV Export:

Docubee can be used for a wide variety of different use cases, from something as simple as collecting survey data, to more advanced use-cases requiring documents hosted on your site to be automatically populated with data.

Reach out today to schedule a demo, or to get started integrating Docubee’s other powerful APIs into your product. For more advanced use-cases our Professional Services team would be more than happy to assist.

Check out more here.

Landon Lamb

Landon Lamb, Software Engineer III – Docubee Team

Landon started out as a Software Engineer in Support at Accusoft in July 2016. In April of 2017, he transitioned onto the Docubee team initially as a Workflow Developer.

Currently, Landon is a Software Engineer III and works on the front end site, the back end services, and the product’s build pipeline. He enjoys helping deliver new features to Docubee’s growing user base.