Traverse Web Application
The Traverse web application runs in a user's web browser and can interact with hardware on Windows devices to scan, sign, and virtually print documents.
Web Browser Requirements
Edge (latest version) on Windows 10 or greater
Chrome (latest version) on Windows 10 or greater
Safari (latest version) on iPadOS 13 and macOS 14 or greater
Northwoods recommends users bookmark or create a desktop shortcut to their agency's Traverse URL for quick access.
Scanner Requirements
Scanner Devices
Any Ricoh scanner that supports the PaperStream IP (TWAIN) driver should work with Traverse. Northwoods does not test all scanners, but has tested the scanner models below and confirms they work with Traverse.
Ricoh fi-7030
Ricoh fi-7160
Ricoh fi-8170
Ricoh fi-8040
Scanner Software
Ricoh PaperStream IP TWAIN driver (latest version supported for scanner device)
Dynamsoft Dynamic Web TWAIN version 17.2.1 (installed as Dynamsoft Service 1.7.1026)
TWAIN.org Twacker Utility 32-bit version
See Setting up scanners for installation and configuration instructions.
Signature Pad Requirements
Signature Pad Devices
Any Topaz Electronic Signature Pad that supports the SigWeb driver
Signature Pad Software
Topaz Systems SigWeb driver 1.7.2.7+
Traverse does not support signature pads in a Citrix environment
Traverse Virtual Printer Requirements
Required Windows Software
Microsoft Edge WebView2 Runtime (if you use Microsoft products you likely already have this installed. If not, install the Evergreen Bootstrapper)
Traverse Mobile Application
The Traverse Mobile application can run on Apple and Android devices and provides a mobile experience. Traverse Mobile allows users to complete forms, take pictures, and record audio and video while out of the office.
Devices Supported
Apple Devices
Traverse Mobile on the Apple App Store
Apple iPhone running iOS 12 or greater
Apple iPad running iPadOS 26 or greater
Android Devices
Traverse Mobile on Google Play store
Android phone or tablet running Android 16 or greater
Device must meet the following hardware specifications
128 GB of internal storage
8 GB of RAM
8 cores x 1.8 GHz CPU
64 MP camera
Traverse Mobile Northwoods recommends agency's use an Enterprise Mobility Management (EMM) system to deploy and enable automatic app updates.
Single Sign On (SSO) Authentication
Traverse is compatible with many common identity providers (IdPs) to provide an integrated authentication experience for users.
Traverse works with the following IdP solutions:
SAML
Microsoft Azure AD (Microsoft Entra ID)
Microsoft ADFS
Microsoft Entra certificate based authentication (CBA)
Okta
If you do not see an IdP listed contact Northwoods to inquire about support for your IdP.
Traverse Integration Server
Agencies that have integrations to send and or receive data from Traverse to local systems, such as 3rd party document management or case management systems, may require the installation of an integration server at the agency.
An integration agent, Tibco Scribe, will be installed on the agency integration server and handle communication to and from Traverse.
Integration Server Operating System Requirements
Windows Server 2016 or greater
Integration Server Software
Microsoft Windows Identity Foundation (WIF)
Integration Server Hardware
Quad Core CPU or better
8 GB RAM per integration agent
50 GB of available storage for integration data
24/7 business grade Internet connection
Integration Server Network Security
All ports listed in the table below will need to be opened for outbound traffic. Allow the traffic to the following domains regardless of the destination IP address:
*.amazonaws.com
api.sendgrid.com
For customers with Palo Alto firewalls, allow application identification for SendGrid. Add a custom URL category for the domains *.sendgrid.com
To retrieve integration agent instructions and update the integration provider with its current status, the following endpoints must be allowed:
The ports listed in the table below required the firewall to be stateful.
Port | Description | Endpoints |
TCP 80 | Required for outbound integration agent communication and certificate validation. This uses the Online Certificate Status Protocol to make GET requests. This port is also used by the integration agent to send email alerts through SendGrid and send integration statistics to an AWS RDS database. | api.sendgrid.com comodoca.com usertrust.com
|
TCP 443 | Required for secure outbound integration agent communication. This port is also used by the integration agent to send email alerts through SendGrid and send integration statistics to an AWS RDS database. | api.sendgrid.com *.servicebus.windows.net agent.scribesoft.com endpoint.scribesoft.com api.scribesoft.com
|
TCP 5671, TCP 5672, TCP 9350-9354 | Outbound ports used by the integration agent to communicate with the Microsoft Enterprise Service Bus (ESB). | *.servicebus.windows.net |
Integration Server Database Software
If required, the integration server may need access to a database located on the agency network that contains agency data for the integration. This database is often a staging database used by the integration to stag and transform data before being sent to Traverse.
Microsoft SQL Server Requirements
Versions
Microsoft SQL Server Enterprise, Standard, or Express* 2016 or greater
Microsoft SQL Azure
Authentication: Microsoft Windows (recommended) or Microsoft SQL Server.
Minimum access rights of public server role and db_owner database role for the staging database.
*Note: Express edition is only recommended for staging databases that do not require 10GB or more of storage.
Oracle Database Requirements
Versions
Oracle Database 18c
Oracle Database 12c
Oracle Database 11g Release 2
Authentication: Read-only access
Oracle role with Select privileges granted for intended tables in the source database