Join us for an engaging webinar, as we unravel the potential of AI for revolutionizing document management.
Watch Now
Enable your employees to remain productive throughout the document management process.
Read More
Learn how SmartZone uses a regular expression engine integrated into the recognition engine to achieve the best possible accuracy on data that can be defined by a regular expression.
Docubee is an intelligent contact automation platform built to help your team success
For reporting purposes, we want to rename the markup layer JSON files to help identify which tenant made the markup. For example:
c1fea5868607402c1b664272e5b82aeb7fff7390_0_0hg91gTqSCeg_P9B2Ko7BaH-YxkaazjH.json
rename to:
accusoft_c1fea5868607402c1b664272e5b82aeb7fff7390_0_0hg91gTqSCeg_P9B2Ko7BaH-YxkaazjH.json.
accusoft_c1fea5868607402c1b664272e5b82aeb7fff7390_0_0hg91gTqSCeg_P9B2Ko7BaH-YxkaazjH.json
Is this possible?
The actual filename for an annotation .json file contains an encrypted value of the file path and document name. This is what is used to associate the JSON markup layer file with the document.
If you make changes to the first part of the file, PrizmDoc will no longer be able to associate those markups to the actual file.
As a alternative, you can set up a separate PAS instance for each tenant, which will provide a different markup layer for each tenant.
Or you can programmatically handle the markups and store them specifically for each tenant. The following articles outline our Markup JSON specifications: