Technical FAQs

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

 

 

Join us for an engaging webinar with Dan Lee, Senior Product Manager at Accusoft, as we unravel the use of AI in eDiscovery.

Key Focus Areas

AI in eDiscovery is a rapidly evolving field that leverages artificial intelligence to automate and enhance various aspects of the eDiscovery process. AI in PrizmDoc helps to protect sensitive information and ensure compliance with data privacy.

  • See how AI is used in PrizmDoc to streamline and automate the PII Detection process to find and extract personal information from text documents.
  • Explore methods to establish the context of the identified PII by using surrounding information to help interpret the meaning and relevance of PII in a document and determine the appropriate actions to take.
  • Learn how PrizmDoc’s Redaction tools enable you to add secure masking and removal of PII from your documents to prevent unauthorized access or disclosure and generate a resulting document with the PII securely removed.

In this webinar, we explore real-world cases using PrizmDoc’s APIs and SDK to build automated and more efficient PII identification and redaction workflows.

Key Take-Aways

  • How to use AI in PrizmDoc for PII detection
  • How to establish context for the identified PII
  • How to create resulting documents with the PII securely removed

Take advantage of this opportunity to shape the future of eDiscovery with AI.