Postmark Scan Release Notes v2.x - Pre 2.9

V2.8.1.9 – June 2024

Issues Resolved

· Fixed an issue with Okta OIDC user authentication could fail under certain conditions.

· Upgrade .Net Core framework to v8.0.6.

· Added a test to the Airmail2 Hub to prevent double posting of document feedback from multiple users.

Prerequisites

· Windows Server 2016 or newer

· Microsoft SQL Server 2016 or later (must run in compatibility level 130 or greater)

· Microsoft ASP.Net Core Runtime Windows Hosting Bundle v8.0.6

· Visual C++ x86/x64 (2013)

· Visual C++ x86/x64 (2015-2022)

· ASP.NET Framework 4.8 or greater

V2.8.1.8 – Skipped

V2.8.1.7 – April 2024

Issues Resolved

· Fixed a problem causing OIDC tokens to refresh every hour.

Prerequisites

· Windows Server 2016 or newer

· Microsoft SQL Server 2016 or later (must run in compatibility level 130 or greater)

· Microsoft ASP.Net Core Runtime Windows Hosting Bundle v7.0.5

· Visual C++ x86/x64 (2013)

· Visual C++ x86/x64 (2015-2022)

· ASP.NET Framework 4.8 or greater

V2.8.1.6 – March 2024

Issues Resolved

· Okta OIDC user authentication could fail under certain conditions.

Prerequisites

· Windows Server 2016 or newer

· Microsoft SQL Server 2016 or later (must run in compatibility level 130 or greater)

· Microsoft ASP.Net Core Runtime Windows Hosting Bundle v7.0.5

· Visual C++ x86/x64 (2013)

· Visual C++ x86/x64 (2015-2022)

· ASP.NET Framework 4.8 or greater

V2.8.1.5 – March 2024

New Features & Enhancements

· Added a feature to open Records Room filing folders in a collapsed state. This could make it easier to work the UI when there are many folders defined on a workspace.

Issues Resolved

· Fixed a problem with the XML schema returned from APIv2/SearchKGS.

· Fixed a problem with eCover reprint in the Console.

· Fixed a problem in Microsoft Entra Id user synchronization that could fail when synchronizing more than 100 users.

Prerequisites

· Windows Server 2016 or newer

· Microsoft SQL Server 2016 or later (must run in compatibility level 130 or greater)

· Microsoft ASP.Net Core Runtime Windows Hosting Bundle v7.0.5

· Visual C++ x86/x64 (2013)

· Visual C++ x86/x64 (2015-2022)

· ASP.NET Framework 4.8 or greater

V2.8.1.3 – November 2023

New Features & Enhancements

· None

Issues Resolved

· The function to export a list of documents in the Airmail2 Console did not respect the filters that had been applied so it would export all documents.

Prerequisites

· Windows Server 2016 or newer

· Microsoft SQL Server 2016 or later (must run in compatibility level 130 or greater)

· Microsoft ASP.Net Core Runtime Windows Hosting Bundle v7.0.5

· Visual C++ x86/x64 (2013)

· Visual C++ x86/x64 (2015-2022)

· ASP.NET Framework 4.8 or greater

V2.8.1.2 – October 2023

Issues Resolved

· Repaired an issue with the Notification Service; the service could fail to send when multiple recipients are on the To or Cc list.

Prerequisites

· Windows Server 2016 or newer

· Microsoft SQL Server 2016 or later (must run in compatibility level 130 or greater)

· Microsoft ASP.Net Core Runtime Windows Hosting Bundle v7.0.5

· Visual C++ x86/x64 (2013)

· Visual C++ x86/x64 (2015-2022)

· ASP.NET Framework 4.8 or greater

V2.8.1.1 – September 2023

Issues Resolved

· Fixed a problem that could cause the Document Lifecycle Service to fail on startup.

Prerequisites

· Windows Server 2016 or newer

· Microsoft SQL Server 2016 or later (must run in compatibility level 130 or greater)

· Microsoft ASP.Net Core Runtime Windows Hosting Bundle v7.0.5

· Visual C++ x86/x64 (2013)

· Visual C++ x86/x64 (2015-2022)

· ASP.NET Framework 4.8 or greater

V2.8.1 – June 2023

New Features & Enhancements

· Enhanced authentication options are available in this release including Azure AD, Google, and Okta.

· A new optional service is designed to help managers monitor not only when mail is delivered but if a recipient has acted on the delivered item. This feature is available only if mail items are delivered into the firm’s DMS (iManage or NetDocuments.) The feature supports optional read reminders, Postmark Console Cards, and a new Unread Mail report.

· A new feature allows uploading of electronic PDF files directly into the Airmail2 client without the need for scanning. After being uploaded, electronic files are processed in exactly the same manner as a scanned file.

· A new ‘Redeliver’ action is available on the Postmark Console ‘UnDelivered Documents’ card. This new feature will allow anyone with access to the Console to attempt a second delivery and will likely be most useful when the reason for the delivery failure is well known and has been addressed.

· Added a new ‘UnFixed Documents’ card to the Postmark Console to show documents that have been marked in QC as requiring a fix.

· A new feature of Mailroom workflows (non-Matter Driven) allows the mailroom to make the recipient the document owner; in current versions the mailroom operator would always be the owner. This feature may be useful in a two-step mail process where the mailroom forwards the document to another person for further filing or addressing.

· A new feature of the system is the ‘Filter by user’ option on the document drawer. By using this feature, QC operators can work only with documents where they are the document owner unless they are allowed the Manage role on the drawer.

· Upgraded our imaging framework for improved performance and barcode recognition.

· Added a notification template registry to this version so implementation team members can select templates from a list rather than maintaining columns using SQL in SSMS.

· A new feature of the QC module allows operators working from a list to show or hide documents that have been previously processed with a ‘Fix’ button. Firms that use a ‘Fix’ button in QC typically expect that someone other than the initial QC operator is responsible for repairing the document, this feature makes it easier to identify those documents that need to be fixed.

Issues Resolved

· Fixed a problem with dates displaying in the incorrect format when using any language other than EN-US.

· Fixed a problem in QC file download that could prevent the system from downloading larger PDF files.

· Increased the timeout value for upload/download of files in QC. These operations could stop abruptly if the file took longer than 1 minute to upload or download.

· Fixed a problem where QC operators could accidentally change a document workflow to a Scanback workflow, which should never be allowed. This version removes any Scanback workflows from the workflow selector in QC.

· Fixed a problem where a ‘Delete’ button label could appear sometimes in QC even if no such button was defined on the drawer.

· Reworked the metadata pop-up that appears on mouse-over of a barcode value in the Console. The modifications include showing both the Deliver To and Operator (if they are not the same) hiding drawer fields that contain no value.

· Upgraded some third-party JSON tools to the latest stable version.

· Upgraded to ASP.Net Core 7.

Prerequisites

· Windows Server 2016 or newer

· Microsoft SQL Server 2016 or later (must run in compatibility level 130 or greater)

· Microsoft ASP.Net Core Runtime Windows Hosting Bundle v7.0.5

· Visual C++ x86/x64 (2013)

· Visual C++ x86/x64 (2015-2022)

· ASP.NET Framework 4.8 or greater

V2.8.0 – March 2023

New Features / Enhancements

This version implements DocSolid’s Scanback^® within the Airmail2 framework. Scanback is a scan-first application for front-office workers without requiring hardware or software added to the scanning device:
- To support customized notifications, a ‘Valid on Scanback’ option has been added to Workflows in Airmail2 / Settings.
- Added a Scanback tab to the Postmark Console, so personal Scanback preferences can be set for individual users. These preferences include the delivery method and who should be notified of the delivery.
  - Delivery Method options are Document Management System, Regular Email Attachment, Secure Link via Email or Cloud Repository.
  - Email To: Will default to the Scanback user but may be set to one or more registered email addresses.
- Scanback documents may be processed using stamps, labels, Scanback eCovers or a personal file/folder name.
- Added a new feature to the Postmark Console to generate and deliver Scanback eCovers to selected users or groups.
Added a new secondary delivery option for mail. The feature is meant to meet the needs of mobile recipients who need to access mail items via their smartphone. With the feature configured, the system makes the typical primary delivery, e.g. to the DMS but will also make a second delivery via email attachment or cloud repository accessible to the mobile recipient. Secondary delivery settings may be persistent or time limited.
New multi-lingual capabilities of Airmail2, allows operators to run the system in their preferred language. Recipients may also receive email notifications and leave feedback using their preferred language.
- The system currently supports EN-US and ES-MX but the framework can support many other translations.
- Any workflow can be designed with multiple languages so that field labels and notifications are presented in the native language for each operator or recipient.
- Datetime format may also be configured for the firm’s preference.
- Multi-language is available in the Airmail2 main application and the Hub but not in the Postmark Console or legacy clients.
Airmail2 delivery notification subject and body text are now configured on the workflow instead of on the delivery service. This modification makes it easier to customize and insert custom metadata into the configured strings.
The Airmail2 navigation panel can now be customized by the operators so that each operator can reorder their Workflow options and set one as their personal default. The system will always open in the operator’s default Workflow. In addition, the hard-coded Mailroom and Records Room subheadings have been removed because some customers use ‘Mailroom’ Workflows to process Records Room transactions and vice versa.

A new optional feature allows recipients to send feedback notifications to the mailroom by using buttons in the delivery notification email in lieu of the launching the Airmail2 Hub.

These buttons can be configured to send simple choices, or they can send email containing comments to a special inbox that is monitored by the system.
A new service (Email Reader Service) has been created to parse received messages and update documents with the submitted feedback details.
Mailroom operators are notified of received feedback in a subsequent notification.

Added optional capabilities to deliver mail to several cloud repositories including OneDrive and Google Drive.
Standardized all Postmark platform applications and services to 64-bit for improved performance and stability.
Added general support for Unicode characters in all drawer fields. This may require some manual database changes when upgrading an existing system from any previous release of Postmark / Airmail2.

Issues Resolved

Upgraded several 3rd party packages for better performance and security.
Upgraded .Net Core and ReactJS frameworks to new release version.
Fixed several authentication issues that could cause a blank screen on initial launch.
Packed the Airmail2 Hub in its own project to allow for more flexibility in deployment.
Fixed a problem in document class lookup in records room workflows.
Fixed a problem when using Unicode characters in an Office Location that could prevent some operators from accessing the system.
Repaired some issues with the Customer Success Report. Processing time was not calculating correctly and matter-drive mail workflows cannot correctly count recipients.
Notification type 400 - Subject/Body with [dateIndexed] and [scannedPageCount] meta-tags are not being replaced with the proper values.
QC Daily Activity - the processing column wasn’t being updated correctly to show the current state of the document.
Several Postmark Console cards were showing the operator who processed the item instead of the recipient, these have been modified to focus on the recipient instead of the operator.
Several items that were being logged as errors in the APIv2 log were not actually errors, and so have been reclassified in the log appropriately.
Improved miscellaneous spelling errors and language issues in several application logs.
The report subscription service was holding prepared reports in cache causing the service to deliver stale reports should any report be requested more than once within a few hours.
Several schema and query changes have been made in the PostmarkMaster database to improve performance.
Fixed several issues that could cause odd display behavior on resize or zoom of the Airmail2 webpage.
Changed the logo at the bottom of most notification emails to Airmail2 instead of DocSolid.
Renamed the Postmark Console card “MM3 Files on Hold” to “Files on Mailman Hold” for clarity.
In previous releases, the Postmark Console and APIv3 coexisted in the same project, but this version separates them into distinct projects. This enables better control of the installation and how it is accessed.
To provide better control of QC operator activities, this version does not use the older PostmarkClient.QCOperatorPrivilegeClass (type: 10, id: 88) but has replaced that with two new Airmail2 (type: 12) settings. These two options must be edited in the database or by using PMKSAdmin.
- QCAllowUploadDownload (type: 12, id: 106) If set to FALSE, the upload and download buttons are not available to the QC operator.
- QC AllowMetadataEdit (type: 12, id: 105) If set to FALSE, the metadata edit options not available to the QC operator.
Modified the Postmark installer so the SQL ‘sysadmin’ role is no longer required for database installation.

Prerequisites

Windows Server 2016 or newer
Microsoft SQL Server 2016 or later (must run in compatibility level 130 or greater)
Microsoft .NET Runtime Hosting Bundle - 6.0.0
Visual C++ x86/x64 (2010)
Visual C++ x86/x64 (2013)
Visual C++ x86/x64 (2015-2017)
.NET Framework 4.8 or greater

V2.7.0 – August 2022

New Features / Enhancements

· Enhanced QC features:

o Operators now have an easy way to move one scanned page to the end of the document, which may be useful in some mailroom workflows where envelopes are scanned as page one of the document.

o The system now supports a ‘One-Touch’ Mailroom workflow which is a scan-first workflow that does not require a profiling step prior to scanning. Mail items are scanned into a specially configured Mailman Collection Point and inserted into the Postmark system without metadata, the metadata (Recipient, Sender, etc.) are supplied by the QC operator.

o A new optional feature allows operators to choose documents from a list of items that are ready for QC rather than keying barcode values. This new feature warns QC operators if some other operator has already opened a document on the list for processing.

o Added an auto-select feature that works with the QC list to open the next document in the list without the operation needing to select one. This might be useful if QC is done without paper.

o Daily Activity is now available to the QC operator so they can see which documents have been processed in the last day. This new pop-up also shows delivery status as QC’d documents are processed after acceptance.

o Removed the QC option from the UnQC’d card in the Console, QC is available only in Airmail2.

o Reworked the QC settings to add control of the list and auto-select features.

· A new system feature supports Persistent Messages, these are text messages that may be assigned to recipients, then displayed to operators during profiling and QC Mailroom operations.

· A new system feature supports temporary Special Handling instructions and override of normal preset values for the recipient.

o Mail can be forwarded to another recipient.

o All preset values (delivery method, To and Cc) can be overridden while the Special Handling item is active.

o Special Handling text message is optional and may be displayed to Airmail2 operators either during profiling, QC or both.

· A new feature of this release allows admins to change the retention configuration on a drawer which causes the retention dates for all documents existing in the drawer to be recomputed per the new settings.

· Reports:

o Added a new Customer Success Report that shows offices and production by workflow. This report includes no user personal data and identifies the firm only by their DocSolid customer id.

o Added a time and day to better control when report subscriptions are filled.

o Exposed a few simple reports.

· Workflow definitions

o Features have been added to allow more customization of how custom fields are handled during profiling and QC.

o Several new notification formats are available depending on the combination of workflow, delivery method and document status. Both the Subject and Body text lines can be built using a combination of literal text, system field values and workflow field values. Enclose system fields in double square brackets like [[barcode]]. Enclose non-system workflow fields in single curly brackets as in: {Sender}.

o Added support for ‘Matter Driven’ workflows. In workflows of this type, the recipient is information only, is not used for filing and may even be omitted from the configuration. These workflows push documents into a named folder that exists in the matter workspace.

o Added highlighting to the workflow selector (the blue vertical menu on the lefthand side of the screen) so it’s easier for operators to know which workflow is currently in use.

· Added a new system feature that will prompt the operator to remove any email reference to an account that has been disabled. Disabled accounts are not valid as mail recipients or for notification.

· Added a new feature to re-print eCovers in Airmail2 or from the Console.

· Improved Feedback from the Hub:

o Some feedback message choices may be configured to require the recipient to enter notes to further explain the issue.

o Added a feature to send feedback notifications to the mailroom instead of simply adding the document to a card.

· Added a feature that will deliver completed images to a system folder without the metadata.

· Added an option to Airmail2 and the Console to show document metadata when the operator uses the mouse to ‘hover’ over a barcode.

· Added an option to display a link to the recipient’s DMS mail folder in the notification rather than just to one delivered document.

· System fields:

o Added Delivery Method to every document.

o Added Recipient Id to every document (on Records Room or Structured Scan documents, the system field contains the operator id.)

· Added a new API endpoint to allow the delivery service to write status messages back to the Postmark document.

Issues Resolved

· There were some complaints about the page-view quality when reviewing documents in QC. To address this issue, this version supports an ‘Undocked’ page view that allows a selected document page to be opened in a new browser tab rather than in the previous on-screen control. This setting is selectable by each operator.

· Some users complained that the string showing the delivery method, To and Cc users was too easy to overlook as it was displayed in the lower-right corner of the profiling screens. The forms have been modified so that data shows immediately under the active recipient or matter, making the current settings more noticeable.

· The ‘Delivery Method’ pop-up available during the profiling steps included a notification ‘Subject’ and ‘Body’ text, which caused some users to believe they needed to enter custom text with each mail item. This version can build these strings using a combination of literal text and document metadata, so it is not necessary for operators to key this data while profiling.

· Modified the User Group Service (AdSync):

o Matches users using the AD native GUID instead of the login name. This allows for changes to the logon name without breaking the synchronization.

o Added a configuration option of prevent the service from synchronizing user office locations.

· Upgraded the OCR engine used in the QC Service for better performance and improved OCR.

· Fixed a problem in Records Connect that could prevent the document disposition from displaying correctly.

· Fixed a problem in the Console that required an ending slash on the page URL.

· Fixed a problem in QC that could prevent the system from showing all document pages when using the Next/Prev buttons to navigate through the document.

· Modified the system so that document location is controlled by the mailroom that processed the document instead of the recipient.

· Improved date display for international users.

· Made the barcode image smaller on eCovers to consume less toner printing.

· Fixed a problem with QC when multiple document versions are available. Added a feature to allow QC of any filed version, not just the latest.

· Fixed a problem that could cause temporary report files to be left on the disk.

· Fixed some performance issues when reading matters and folders for Records Room workflows.

· Added some indexes and clean-up logic to the Daily Activity table for better performance.

· Improved ‘Favorites’ filing and logic to improve usability and performance.

· Opening files that are too large in the Console could result in an error.

· Reworked the formatting of Console/People/Properties for better usability.

V2.6.0 – January 2022

New Features / Enhancements

· Added new user roles to the Postmark Console to better control operator access to system features.

· Added a helpdesk feature to the Postmark Console allowing operators to register barcode roles on behalf of others.

· Added an advanced search capability to the Postmark Console supporting search by date range and/or whole word matching.

· Added the Timeline action to all Dashboard cards and document lists where a barcode value is included.

· Added a Move Image action to the L&F card in the Dashboard to match a scanned image to an existing reservation.

· Refactored the Airmail2 client to improve security, offer better system performance, and add several new features.

o Flexible workflow structure to configure custom user interfaces, messaging, etc.

o Email-enabled user groups may now be used as mail recipients.

o To improve promote filing efficiency, Records Room operators may now build a list of favorite filing workspaces or folders.

o A new feature allows operators to create new profiles from their recent system activity.

· Added features to the Postmark Console and Airmail2 supporting multiple office locations.

o To use the muti-location feature, each synchronized account (either operators or recipients) must be assigned a single office location.

o Most synchronized accounts are given the “Mail Recipient” role.

o System operators always have access to their own location, but other locations may be added if the operator requires more access.

o In Mailroom workflows:

§ The “Deliver To” user list includes only Mail Recipients who are assigned to one of the operator’s allowed locations.

§ Mailroom notifications may be sent to any email address registered in the Postmark user table and are not filtered by location.

o All Postmark Console Dashboard cards that contain identified documents are filtered by office location.

· Added features to restrict operator access to certain clients or matters.

o By default, all Records Room operators are allowed to file documents into any matter.

o The new option effectively associates a list of matters with a workflow, so if the operator has access to the workflow, they have access to the matter.

· Added features to support envelope scanning (personal mail) workflows where recipients must respond to a pre-delivery notification and send handling instructions to the Mailroom before mail items can be delivered.

· Added features to allow recipients to provide feedback to the Mailroom or Records Room regarding delivered documents.

· Added a flexible workflow structure that can be used to control how documents are handled and processed in the Mailroom or Records Room. Among other things, workflows can be used to:

o Define whether the application should launch the filer for the Mailroom or Records Room.

o Define the specific data items to be captured for each document.

o Control the format of notifications.

o Define pre-delivery and feedback options that are available to recipients.

o Control the list of clients/matters available in Records Room applications.

· Added a new Airmail2 Hub page to be used by recipients for:

o Secure delivery via email where a link is included in the delivery notification so the recipient can view or download the document from the Postmark repository.

o Capturing pre-delivery instructions when used in an envelope scanning (personal mail) environment.

o Capturing post-delivery feedback from recipients regarding things like image quality or paper disposition.

· Airmail2 in all Mailroom workflows we removed the Recipient List to improve overall performance and declutter the UI. Instead of picking from a list or using the search box, type directly into the “Deliver To” field to start searching.

· Airmail2 - Delivery notifications for Mailroom or Records Room workflows (type 400 messages) may be summarized and sent at predefined time(s) of day instead of sending one notification for each document.

· Refined the delivery notifications sent by Airmail2 (type 450 & 400) so they do not list all the drawer fields but may be customized as needed.

· Renamed database from KwikTag to PostmarkMaster.

Issues Resolved

· DPD-3976 - QC - The document version number would not sequence when the operator used the ‘Upload’ feature to upload a new version.

· DPD-3960 - Fixed miscellaneous issues found when registering new barcode rolls

· DPD-3938 - Postmark Console - Fixed a problem with user authentication when SSO is enabled. The login prompt might be displayed even when not required.

· DPD-3936 - Fixed a problem that could result in multiple documents being filed with the same 998-series barcode.

· DPD-3933 - APIv2 - Fixed a problem that could cause “Error trying to send Scanback Missing Barcode notification” errors to show in the log.

· DPD-3894 Postmark Console People - Fixed a problem where the properties dialog would sometimes fail to open on double-click

· DPD-3883 Fixed a problem that could cause QC to fail if the scanned page count was incorrect

· DPD-3860 Report subscriptions are delivered as Kwiktag Report Request change to Postmark Report Request

· DPD-3849 & DPD-3954 KGS Indexing Service fixes/improvements

o Fixed a problem in the indexing service that will allow the service’s log file to be written to any drive location.

o Added database indexes to tblDocSearch for both NeedsKGSFilingFields and NeedsKGSContent to improve performance

o Improved the stored procedure used to feed new documents to the indexing service

o Added a timeout value to the indexing service to overcome issues if the process is responding slowly

Prerequisites

· Windows Server 2016 or newer

· Microsoft SQL Server 2016 or later (must run in compatibility level 130 or greater)

· .NET Core 5.0.8 Hosting Bundle~~ASP.NET MVC 3 (Visual Studio 2010) ASP .NET MVC 3 Tools Update Language Packs~~

· Visual C++ x86 (2010)

· Visual C++ x64 (2010)

· Visual C++ x86 (2013)

· Visual C++ x64 (2013)

· Visual C++ x86 (2015)

· Visual C++ x64 (2015)

· Visual C++ x64 (2017)

· .NET Framework 4.8 or greater

V2.5.0 – August 2021

Note: Postmark Scan v2.5.0 requires Microsoft SQL Server 2016 or newer; do not attempt to install on older versions of SQL Server!

New Features / Enhancements

· Release of a new Postmark Client with features directed toward helpdesk and team lead users including:

o A new dashboard featuring customizable cards with drill-down capabilities for improved system monitoring.

o Tools to simplify edit of mail recipient preference presets.

o Tools to control files that fail during MM3 processing.

o System report feature supports one-time requests and subscriptions with specific time-of-day delivery.

o Access to the latest QC client with ability to QC from paper as well as from a card.

o An operator alert bell reminds the operator of significant events as they happen and this data is logged in the DB as an audit trail.

o A simple metadata search feature finds filed documents instantly without waiting for the legacy indexing service.

o Logs may be written to a Teams channel rather than just to a system file.

· Many QC client improvements for better performance and usability including:

o New faster framework.

o Improved and cleaner user interface.

o Client supports one to three QC action buttons.

· Airmail2 for the Mail Room - New features:

o Allows mail delivery via Secure Email Link in addition to existing Airmail2 delivery options: 1) Regular Email Attachment, 2) Document Management System. Secure email links allow users to view documents in their desktop browser but are only valid for the original email recipient. (May require upgrade to latest delivery service)

o A new feature writes the mailroom operator’s ID to the profile in addition to the recipient’s ID, so we can tell which operator created each profile.

o ‘To’ and ‘Cc’ fields for notification now support Outlook-style multiple address entries.

· A new Document Timeline feature has been added to track changes in QCStatus, DeliveryStatus, metadata edit, as well as profile creation.

· Postmark Scan can now support multiple iManage environments within a single system.

· A new export/import service may be used to maintain consistency between the DMS and Scan mapping for the Records Room application.

Issues Resolved

· DPD-3767 Scan - External URL links not being saved correctly which would prevent them from opening documents as expected.

· DPD-3766 QC Client - QC was not creating v2 when file was edited (No file pairs created).

· DPD-3678 AD Sync was disabling users based on group membership, the code was modified so users are only disabled if they are disabled in AD.

· DPD-3764 Fixed a DB normalization error in QC Settings.

· DPD-3758 Fixed an issue using SSL in the notification service. Fix requires changes to the Notification Service configuration “mailSettings”.

· DPD-3613 Postmark Scan - Store no Windows user credentials so service account passwords may be changed as often as desired without the need to edit IIS or the DB.

· DPD-3621 Upgrade dtSearch engine to v7.97. Note that the new Postmark Console does not need dtSearch indexing.

· DPD-3622 QC Metadata edit capability improvements.

· DPD-3711 Legacy client (PMKSClient) would not save changed entry to Expected Page Count.

· DPD-3765 Legacy client (PMKSClient) touching the ENTER key in a lookup field would cause the entire form to be submitted; modified to lookup instead of submit.

· DPD-3656 Improved Main installer:

o Support creation of LDF and MDF files on separate drives.

o Upgrade any Postmark Scan v2+ to 2.5.0 in a single step.

· tblNotificationsSent records were not being removed from the DB when tblEmailActions were being deleted. This could lead to large volumes of records being retained even after the documents were removed by the Document Lifecycle Service.

· Fixed a problem that caused the document indexing API to always run in debug mode which caused the system to write unneeded rows to tblDebug.

· Removed a number of unused database indexes from tblDocSearch, tblDocImage, and tblTagSearch.

· Airmail2 / Deliver2 - Fixed a problem that occurred when changing the recipient after a reservation is created.

Prerequisites

· Windows Server 2016 or newer

· Microsoft SQL Server 2016 or later (must run in compatibility level 130 or greater)

· .NET Core 5.0.8 Hosting Bundle

· ASP.NET MVC 3 (Visual Studio 2010)

· ASP .NET MVC 3 Tools Update Language Packs

· Visual C++ x86 (2010)

· Visual C++ x64 (2010)

· Visual C++ x86 (2013)

· Visual C++ x64 (2013)

· Visual C++ x86 (2015)

· Visual C++ x64 (2015)

· Visual C++ x64 (2017)

· .NET Framework 4.8 or greater

V2.4.1 – February 2021

New Features / Enhancements

· Completely new QC module in the Postmark Client allows simple online corrections to scanned documents. Page rotation and blank page removal may be achieved using the new QC client without the need to download or rescan. Document metadata may also edited by privileged users.

· A Records Connect feature has been added to Airmail2 / Profile2. This feature allows records staff to search a custom table to retrieve profiling details (i.e., client id, matter id, folder, etc.)

· Created a new RESTful API to allow developers the ability to download selected document pages as TIFF images.

· Airmail2/Deliver2 can be configured so the filing user is set to either the current-user (the mailroom operator) or the deliver-to user. In previous releases, the current user (the mailroom operator) owned all the document reservations they created regardless of the actual recipient (the deliver-to user.) Even if the entire firm intended to use only email delivery (no DMS delivery) we couldn’t use “Document Received” notifications to deliver mail; this change makes that possible.

Issues Resolved

· Fixed a problem with API references that omitted the final slash.

· Dropped a few unused database indexes for better performance and smaller database size.

· DMS upload success notifications were not being sent when a document was rescanned.

· Fixed a problem with external links that caused the link to be built before the document was uploaded to the DMS.

· Fixed the problem were the Lost & Found drawer was not included in the Document Lifecycle Service processing.

· Fixed a problem with the Document Manager Service that would prevent it from ingesting new documents without a preexisting reservation.

V2.4.0 – September 2020

New Features / Enhancements

· Licensing model changed - initial license count at installation will remain unchanged but actual user counts will be reported and settled at regular intervals

o AD Sync (User Group Service) has been modified to enable all active user accounts in keeping with new licensing principles. (DPD-2696)

o AD Sync (User Group Service) has been modified to pull more descriptive data about users from AD including Description/Department, Title and Office Location. (DPD-3024)

· Added new Monthly Activity by Office report to allow for Scan and Print quarterly volume reporting. (DPD-3043)

· Modified API to copy all metadata when a Scanback eCover (or reusable coversheet) is scanned. (DPD-3227)

· Added logic for reusable eCovers to file multiple distinct documents into a single DMS workspace/folder

Issues Resolved

· All connections to databases should be using integrated Windows authentication in-lieu of storing credentials in the connection strings.

· No clear text passwords are stored by the system as they were in previous versions.

· Corrected a problem in the system that could prevent filing of drawer metadata strings containing certain special characters. (DPD-2833)

· Opening large documents in PMKSClient could result in a 'Unknown file type' message instead of the correct 'Too large' message. Files that are too large for the online viewer may be downloaded. (DPD-3075)

· PMKSAdmin/Settings/AD Sync could throw out-of-memory exceptions or run very slowly in environments with many AD groups. A search parameter has been added to the system and all AD queries are limited to return a maximum of 50 rows. (DPD-3056)

· Increase maximum length for passwords (DPD-3214))

· Fixed security problem with stale user tokens (DPD-2919)

· Fixed security problem storing plaintext passwords - suggest integrated auth for SQL connections. (DPD-2921)

· Fixed problem with special characters in filepairs processed through document manager. (DPD-3048)

· Fixed installer problem that would not allow integrated auth for SQL connections. (DPD3101)

· Postmark Client fixed problem with barcode verification too early in the process even for users not using tags. (DPD-3120)

· Fixed problem with Lifecycle service that would block notifications causing notification delays of 16 minutes at unpredictable intervals. (DPD-3129) Note that the service has been modified so that it stops itself after one polling cycle. Therefore, a Powershell script needs to be scheduled to run in off hours. This script will simply start the service, the service will poll once, then go offline until the scheduled script is executed again. The Document Lifecycle Service should be scheduled to run only once per day but may be started manually, if needed. However, be aware that executing the Document Lifecycle Service during regular business hours will suspend all outgoing email for up to 16 minutes. (rev. 10/1/20 dms)

· Remove SQL references to the master database. (DPD-3193)

· Fixed problem in Document Manager when path did not include final slash. (DPD-3237)

· Fixed a problem related to the drawer field option "Use As Filename For Attachments And Delivery". The contents of any selected drawer field can be used to form the name of email attachments, which may be most useful in Airmail2 Email delivery.

· Fixed a problem when using special characters (#&) in user passwords.

· Fixed a problem when using email templates to set maximum attachment size

· Fixed a problem related to the Storage User Account (PMKSAdmin/Settings/Global) used to read/write to the document repository. The password could not be written from the UI.

· Fixed a problem that caused the system to create the external retrieval URL before the document is uploaded to the DMS.

V2.3.1 – December 2019

New Features / Enhancements

· Added new optional context-sensitive extension client for iManage Work 10 Web to create reservations and placeholders

· Added new optional web-based Postmark Client to be used for QC, Scanback and Structured Scanning (DPD-2741)

· Added ability to customize text in the Work 10 comment field when appending the Postmark barcode value using either of the client mentioned above (DPD-2357)

· Changed the final ScanTracking value to 'Processed' instead of 'Delivered'. Use the PostmasterComplete node in Document Manager's config file to customize the value. (DPD-1672)

· Improved internal security token mechanism to delete stale tokens.

Issues Resolved

· Fixed a problem preventing users from taking ownership of other user's tags (DPD-2718)

· Fixed issue when registering label rolls; problems prevented users from owning more than one roll of similar tags (DPD-2859)

· Fixed issue with NRL links for iManage Work 10 (DPD-2804)

· Fixed issue when profiling into Work 10 folders containing special characters using any of the online clients (DPD-2833)

· PMKSClient / QC document version number was not reset between documents which could cause trouble when processing documents (DPD-338)

· PMKSClient could not Veritag documents when using Stamps (DPD-2759)

· PMKSClient / QC fixed problem with Stamps prevents users from processing barcode with certain beginning letters (DPD-2781)

· Postmark Client / QC fixed issue with file upload - filepair did not contain the barcode value so the new file could not be matched with the correct profile (DPD-2803)

· Postmark Client / QC several cosmetic and workflow improvements made to UI (DPD-1835)

· Postmark Client fixed error pop-up complaining of no barcodes being registered when only QC is enabled (DPD-2834)

· PMKSClient / Tag fixed a few minor display issues and change tool tip from 'One columns' to 'One column' (DPD-2943)

· Fixed a problem found could prevent Veritag from working correctly (DPD-2958)

· Fixed problems registering new barcodes in the iManage Extension Client (DPD-2956)

· Add Scanback logic to Document Manager Service - issue could cause documents to file into L&F (DPD-2955)

· Fixed issue in Document Manager Service - the ScanTracking field was sometimes not set correctly after the document was loaded (DPD-1672)

· Fixed an issue to determine if a barcode is 'OURS'. A barcode is consider OURS if: 1) the value has been used to file a document into Postmark Scan, or 2) the barcode is part of a roll assigned to a user. (DPD-2962)

· Fixed an issue in Postmark Client QC - History field was not appending values as expected (DPD-2961)

V2.3.0 – June 2019

New Features

· Added a new web application used to control Scanback preferences by user.

· Added support for Scanback eCovers. Scanback eCovers are:

o Reusable coversheets that can be used for casual scanning in lieu of stamps/labels.

o Are identified by datamatrix barcodes whose values are 8 characters in length and always begin with 'SBAK' followed by four digits. In the form 'SBAK1234', this becomes the root number for all documents scanned with the eCover.

o When scanned, the system makes a new filing barcode for the document based on the root and a sequence number in the form 'SBAK1234_14', etc.

Issues Resolved

· None

V2.2.0 – March 2019

New Features

· Updated .NET dependency to support TLS 1.2

Issues Resolved

· Fixed problem in KGS Indexing service when running in SSL configuration

· Refined email templates. See

DPD-2114 - Scanback email notification emails Done for specific details

· Fixed tagging issue with APIV2 which led to multiple errors in log regarding mis-formatted XML

· Fixed an APIV2 error that could cause Mailman files to be put on hold status

Known Issues

· None