2022.1

Capture OnTheGo Workflow processes
A Capture OnTheGo solution requires no less than three basic processes in a Workflow
configuration:
l One process that generates a document (most often, a form), stores it and notifies the
COTG app of the document's existence. Note that this process doesn't send the actual
document. It sends a ticket to the Capture OnTheGo Server so that when the intended
user logs in, the name of the document will appear in the app's Repository, signaling to
the user that the document can be downloaded.
The key task in this process is the Output to Capture OnTheGo plugin.
l One process that authenticates and replies to document requests from COTG users. This
process returns the actual document directly to the app. It starts with a Server Input task
(the NodeJS Server Input task or the older HTTP Server Input task), which returns the
final output of the process to the caller.
l One process that receives and handles the data when a COTG user submits a form. This
process starts with a Server Input task as well.
The three basic processes are described in more detail in the Capture OnTheGo manual: Basic
processes involved in COTG
Tip
An easy way to create a COTG solution, including the Workflow configuration and other
files that it needs, is to use the COTG Timesheets Sample Project. See "Sample
Project: COTG Timesheets" on page150.
Email processes with OL Connect tasks
Sending out emails, based on a Connect template, via an automated process requires you to
design a Connect email process in the Workflow configuration tool.
This topic explains which tasks and files are used in a Connect email process.
Page 188