
NOTE: After scheduling a process, it cannot be removed or cancelled by the user. It will be executed at the
specified time regardless of user cancellations on the control panel, or if the device is restarted.
WARNING! A scheduled or asynchronous process will never be followed by any summary or UI interaction
screen, as they are executed in the background on the device. It will be treated as a separate thread without
UI control. At this point, as it is not possible to interact with the user anymore, all nodes requiring UI
information display will be discarded.
1.4.9.1 Scheduling options
Time delay
This method allows the user to schedule a process execution delaying it a specified amount of time (.net
timespan) while the user gets control of the UI immediately.
If the device is unplugged and reconnected once the process execution time is passed, it will execute
immediately in the background.
Parameters: Timespan (https://msdn.microsoft.com/en-us/library/system.timespan.aspx)
Asynchronous/immediate
An asynchronous or immediate process execution is a process that is programmed with a time delay = 0
seconds. It behaves in exactly the same way as the time delay, but starts the execution immediately.
Time (daily)
The process will start execution once the specified Time arrives at the current day.
In Time scheduled processes, the time counter is reset at 23:59h. Any process scheduled at a certain time of
day will execute immediately if the time has already passed.
Examples:
●
A process will execute at 09:00h, but the device was powered off before the planned time, and it is
started before 23:59h of that day, the process will execute immediately.
●
If the device is started after 23:59h and before 09:00 of another day, it will not execute until 09:00h is
reached again.
●
If the device was started and working all day, and the scheduled process (scheduled at 09:00h) was
initiated at 16:00h, it will execute immediately since the 9:00h already passed.
1.4.9.2 Scheduled processes lifecycle
Scheduled nodes execution
A scheduled process is considered part of a session. The session will be completely finished once all the
processes and scheduled processes are in a final state. A process can reach a final state because it is done,
failed, or cancelled.
Retries to certain processes (mainly digital send) can be set up. If this is done, the process will not arrive to a
final state unless all retries are finished.
Chained — scheduled process
It is possible to chain processes, but they will be processed sequentially. Until the first process completes,
the process nodes which follow it will not be evaluated. Once the evaluation is done, all nodes with conditions
== true will be chained on the scheduler again with the schedule parameters being effective since that time.
Section 1.4 HP Embedded Capture (HP EC) functionality 23
Komentáře k této Příručce