
Scheduled processes: next steps
Once a workflow arrives to a scheduled process, the user will finish the interaction with the control panel, and
the workflow will continue in the background without any interaction with the screen. For this reason, any
node following a scheduled process should also be a process, and like this until the end of the workflow. If
there is a screen, HP Embedded Capture will not display it and stop the workflow at that point.
Performance considerations
Devices have limited resources. Accumulating scheduled processes to the same execution time may slow
down device performance during the transfer. In this situation, a user trying to execute a standard operation
on the device may see delays or unexpected behavior.
The recommendation is:
Schedule your workflows in an asynchronous mode (immediate or delayed) to balance the network load and
device workload. If this is not possible, use the scheduled operations with common sense by balancing the
execution to different predefined times, when possible.
1.5.1.4 Navigation options (custom buttons)
At Metadata, Dialog, or Scan options screens, navigation options can be defined with custom buttons. The
definition of a custom button just requires typing the destination nodeID.
WARNING! It is a restriction that the destination nodeID is a sibling of the current node;
As an example, the following graph portion is correctly built:
Figure 1-10 Navigation options — correct build
The next graph portion is not correct, as it contains a navigation option that is not possible — the Dialog will
never be able to see the Navigation Option 11 node while navigating through screen buttons.
28 Chapter 1 Introduction
Commentaires sur ces manuels