Prodoc 3.24.1 available

Posted onAuthorCustomer Success

Prodoc version 3.24.1 is available now. Prodoc Cloud customers will be upgraded to this version over the coming weeks.

Highlights from the Release notes below (full release notes for all version available at https://tradewindow.io/about-us/release-notes/ )

3.24.1
Released 20/03/2024

What’s new?

  • Push new address and health certificate data to Prodoc via an expansion of the Prodoc API
  • New dedicated data fields for health certificate purposes
  • Improved MPI AP E-cert certificate number matching when raising certificates
  • Enabled emails matching to Shipments based on EDI references
  • Attach inbound emails to Prodoc Shipments as PDF files
  • Use Signee email address in form setup

What’s fixed?

  • Printer column in Paper Locations too wide
  • RFP Certificate Location showing too many unwanted results

Prodoc on prem customers.

Please note the below and pass on to your IT team. If your current version of SQL is below Microsoft SQL Server 2014 then updates are no longer supported.

SQL instance requirements

Server requirements

Due to its 10GB database size limit, SQL Express should NOT be used for any customer submitting more than 700 shipments per year or submitting shipments with supporting ePhyto documentation.

Prodoc supports Microsoft SQL Server 2014 or later, both Full and Express.

A standard size Prodoc SQL database generally consumes approximately 2-8 GB of hard-disk space, but will grow over time as shipments/submissions are generated.

Prodoc does not require an isolated instance, and the database can exist alongside existing hosted SQL databases.

Connections can be made either with TCP/IP or named pipe using the standard Microsoft setup.

Database permissions/rights

The account running Prodoc EDI Service will require ‘dbo’ access to the database

Users will require read/write access to the database as their logged-in user; we recommend the creation of a security principal mapped to an AD group to grant this access to Prodoc users.

Latency

Both the Prodoc III Client and Server components communicate directly with the database, and will do so frequently during normal operations. As such, care should be taken when placing the Prodoc database to avoid potential latency or bandwidth issues.