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
printer driver, you don't have to do that again.) Add a Connect Send printer with the given
settings and print the provided Word file to that printer. The printer will trigger an interactive
process on demo.objectiflune.com.
l
Download the sample files from OL's Resource Center:
http://help.objectiflune.com/en/#csend.
Job transfer process
The Workflow process that handles the job transfer is small and straightforward. It starts with an
HTTP Input task. The action name of this HTTP Input task must match the last part of the URL
for print job submission, set in the printer driver installer (by default: olcs_transfer). The Job
Processor plugin is the only other task in this Workflow process.
For more information about the configuration of this process, see "Job Processor plugin" on
page49.
Using the NodeJS Input task instead of the HTTP Input task requires adding an Advanced
Search & Replace task immediately before the Job Processor task.
Set the String to search parameter to: (<file name="[^"]*" original="[^"]*">)\n\s*
(.*\..{3})\n\s*(.*). Then set the Replace with parameter to $1$2$3, and make sure the
options Search whole file and Treat as regular expressions are ticked.
This is necessary because of an issue in the Job Processor plugin, which will be fixed in version
2019.1.
Interactive process
The core business of the interaction process(es) is: serving web pages to the customer and
handling the customer's response, which comes down to changing (the settings for) the print job
that has been received from that customer. As it has to be tailored to the situation in which it is
used, several Workflow processes may be needed and they may be long and complex. It is
therefore impossible to give a detailed instruction on how to configure the interactive process
(es).
It is however possible to name a few of the key components in such a process.
l
Just as the job transfer process, the interactive process start with an HTTP Server Input
plugin. The action name of this HTTP Input task must match the HTTP action for
interaction given in the printer driver installer (by default: olcs_interaction). (For information
about this plugin, see the Workflow Help: HTTP Server Input.)
Page 47