Effects of warm boot on control steps

A warm restart (boot) of the
eProcedure
Server has the following effects on control steps:
  • Reactivated steps
    are not active after a warm boot. Instead, the previously active control step is active. The left column in Past instructions contains the usual information (the reactivation number is remembered). The middle column displays
    Reactivated Control Step Terminated by
    eProcedure
    Server shutting down
    and the right column has a check mark. An InstructionComplete event record containing the step’s HTML is created. In addition, a ControlStepStop event record is added. These control steps are not eligible for reactivation.
  • Control steps
    that were active during a warm boot of the
    eProcedure
    Server are still active when the server starts again, but the control step is restarted with a new reactivation number. All signatures and previously-entered values associated with the control step due to parameter deviation or canceled step verification signatures are removed. A Past control step is added, which states
    Control Step Terminated by
    eProcedure
    Server shutting down
    .
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal