
Figure 1-7 Chained — scheduled processes
Once a process is scheduled (Destination3), all processes following it will be executed after this one, also in
background, even if they do not have defined scheduling parameters (Destination4, Destination5).
It is also possible to schedule/delay the execution of the following processes, but it is important to consider
that they will be scheduled since the finalization of the previous one.
TIP: When scheduling multiple processes, it is recommended that you just schedule the first one.
1.4.10 Garbage collector
Information generated by HP Embedded Capture is stored temporarily on the device until all processes
complete. Once sessions are finished, the device keeps them in a “quarantine” period until the garbage
collector collects them after a specified amount of time.
The default garbage collection time period is predefined as 24 hours. Garbage collection time period may be
modified through API.
1.4.10.1 Session data deletion concepts
Standard workflows
A session is finished when the user exits the application and returns to the device control panel. At this point,
all scans and processes will be in a final status (SUCCESS or FAIL).
The workflow is a candidate for deletion once the garbage expiration time arrives.
Asynchronous and scheduled workflows
A scheduled workflow session and all its information/scanned documents are active until all scheduled
processes have completed. With scheduled sessions, the user may exit the application once scheduled
processes are executed, but the scheduled tasks will remain on the system, in the background, waiting for
execution time and completion. Once completed (final state), they will enter the same deletion policy as
standard workflows.
1.4.10.2 API & Scan2local
Local scans (only accessible via API calls) will remain on the system the specified garbage time as a normal
workflow according to the Session data deletion concepts section of this guide.
Once a document is scanned and sent to a local destination (device), it may be retrieved by an API call during
the quarantine period. After that time it will be removed.
24 Chapter 1 Introduction
Komentarze do niniejszej Instrukcji