Previously, if you had external integrations setup for multi page PDF files uploaded via the async API or sent via email attachments, these integrations would get triggered for each page in the document. This would lead to unintentional side effects in your integrations such as the triggering of integrations multiple times.
Support has been added to trigger them only once at a file level.
There are new amount and string based validation rules. You can now configure amount based validations rules. For eg: A finance manager should only get a document for review if the total amount on the invoices crosses $5000
There's a new and improved currency detector. This is available as a post processing step. Currencies will appear as 3 digits codes that can be changed via a simple dropdown
Your team members can now get notified when files are assigned to them or when validation rules against your files trigger a review.
You can also set the notification settings from your accounts section, these can be configured at an immediate, daily and weekly level.
Nanonets finally has document level results! This has been a long standing feature request from a lot of our customers.
This feature gives you the ability to process documents at a file level as opposed to a page level. Results will also be available only at a file level across our APIs and CSV downloads and external integrations.
The post processing options in workflows are now even more powerful and easy to use! You can now use the output from post processings in subsequent steps more easily!
Nanonets now has a feature that stores the email metadata information that is sent. The senderemail, emailtimestamp, subject and email_contents are saved. The email contents has a 2000 character limit.
This setting can be enabled from your model settings screen. Here is a short video explainer.
The email contents can be retrieved using the GetByPageID API and GetByFileID API. The info is stored in the request_metadata key.
We've added the ability to read and extract information from email bodies as well now. Previously, the dedicated email inbox of your model would only read data from attachments.
Email bodies will be first converted to PDFs and proceed for data extraction. This setting can be enabled on your model from the model settings screen as well as the email upload dialogue.
You can now select data from dropdowns in your document.
For example, let's say you wanted to add the currency code to a document. Simply upload a csv file with th 3 digit currency codes and create a select from dropdown label, choose your database and column and you're all good to go!
We've finally released this feature! You can now go ahead and upload CSV files in your external integrations and use that to pull/enrich information on your document.
Let's say you want to pull the Vendor GL code based on the vendor name in your invoice. All you need to do is upload the CSV file, use the derive fields from database post processing and get the vendor code into Nanonets!
