AutoStore tasks specify a sequence of components for a process starting with a capture component and ending with a route component.
A task is part of the script defined by a configuration. Each task in a configuration defines a process with a capture component, optional process components, and a route component. The capture and route components in a task define the beginning and end points for all of the workflows in a task. The capture component captures the input data stream for a task. The route component provides connectivity, routing, and information storage. The chain of components in a task creates an AutoStore process. To create a viable process, you must include one capture component and one route component in a task.
You may also insert one or more process components between the capture and route components to process captured documents or their content. Process components perform tasks such as manipulating data, extracting information, or scanning and converting images to text. Components in a process may act autonomously without depending on results of other processes, or they may depend on output from earlier components in the process chain.
The following figure shows a process that includes a capture component, three processing components, and a route component. The capture component is always the first component in a process and the route component is always the last component in a process.
Settings for all components in a workflow are always configured in the properties for the capture component. A component list in the capture component configuration dialog box allows you to access settings for process and route components in a workflow. If you try to open settings for process or route component, AutoStore prompts that you need to configure that component from the capture component. A script can simultaneously handle many different tasks, which are prioritized by configuring scheduling and frequency settings in task properties.