2022.2
Table Of Contents
- Table of Contents
- What is Connect Send?
- Installation
- Printer driver
- Workflow Plugins
- Connect Send database cleanup service
- Moving Workflow to another machine
- Prerequisites
- System Requirements
- Installing OL Connect Send Printer Driver
- Printer driver properties and advanced settings
- Mass deployment of the OL Connect Send Printer Driver
- Using API Keys
- OLCS Notifier
- Known Issues
- Existing OL Connect Send Upgrade Issue
- Installing OL Connect Send on Windows Server 2016
- Installing OL Connect Send on a machine with Connect installed
- OL Connect Send issues under Microsoft Edge browser
- Printing PDF files with Adobe Acrobat Reader
- Paper Size vs Printer Page Size
- Passthrough Printing not supported
- License modes
- OL Connect Send in Workflow
- Using the Printer Driver
- Log files
- Troubleshooting
- OL Connect Send 2.1.2 Printer Driver Release Notes
- Overview
- Important Notes
- OL Connect Send 2.1.2 Printer Driver
- OL Connect Send 2.1.1 Printer Driver
- OL Connect Send 1.8.0 Printer Driver
- OL Connect Send 1.7.0 Printer Driver
- OL Connect Send 1.6.6 Printer Driver
- OL Connect Send 1.4.5 Printer Driver
- OL Connect Send 1.3.5 Printer Driver
- OL Connect Send 1.2.5 Printer Driver
l
Domain / Workgroup Indicator: This domain name is the real domain name or only a
workgroup name. For explanations about domains, domain names, users, user names,
user domains, logged on users vs. application running users, machine names etc. please
refer to the respective Windows help pages or ask your system administrator.
l
Machine name: The name of the machine the Printer Driver is running on as retrieved by
the respective Windows API.
l
Machine GUID: The unique machine ID (see "Job Origin" on page52) of the machine on
which the job was produced. It can be used as an additional identification mark to validate
the origin of the job.
On Error Tab
Please refer to the Using the On Error tab in the Workflow documentation.
Miscellaneous Tab
Please refer to the Miscellaneous tab in the Workflow documentation.
Verifying an API Key
If a print service provider has provided users of the printer driver with API keys, the Workflow
process that receives print jobs will need to verify the API key. This topic shows how to do that.
The API key in the HTTP headers
If the printer driver was configured with an APIkey, it will include the API key in its HTTP headers
as a bearer token when sending a print job. Bearer token authorization looks like this:
Authorization: Bearer «token»
where «token» will be the API key.
The Workflow process
The Workflow process will begin with a Server Input task.
Page 63