...
- Enabling Implicit Recovery
- Using Checkpoints
- Using Human Workflow activity
| Anchor |
|---|
| _Toc315524816 |
|---|
| _Toc315524816 |
|---|
|
| Anchor |
|---|
| _Toc317062402 |
|---|
| _Toc317062402 |
|---|
|
| Anchor |
|---|
| _Toc344890326 |
|---|
| _Toc344890326 |
|---|
|
| Anchor |
|---|
| _Toc385441671 |
|---|
| _Toc385441671 |
|---|
|
| Anchor |
|---|
| _Toc387747510 |
|---|
| _Toc387747510 |
|---|
|
| Anchor |
|---|
| _Toc387748783 |
|---|
| _Toc387748783 |
|---|
|
| Anchor |
|---|
| _Toc401309080 |
|---|
| _Toc401309080 |
|---|
|
Enabling Implicit Recovery
Implicit Recovery is a unique feature which means that the execution state of the process flow is recovered automatically in case the process flow is not executed completely due to some reasons. Now, when the kernel restarts, the process flow resumes execution from the point where it leaves.
...
| Info |
|---|
- Only, Synchronous activities are implicitly recoverable in the process flow. If asynchronous activities are used in process flow, they are made recoverable explicitly using check points. To know how to add checkpoint refer to the section Using Actions in Process Flow
- Actions such as Delay, Put Context Var do not have Implicit Recovery Implementation.
Implicit recovery is supported for any level of parent-child relationship in the process flow. For a recoverable parent process flow, all its child process flows are implicitly made recoverable irrespective of whether the child process flow is configured as recoverable or not.
|
| Anchor |
|---|
_Toc315524817 | _Toc315524817 | | Anchor |
|---|
_Toc317062403 | _Toc317062403
| Anchor |
|---|
| _Toc344890327 |
|---|
| _Toc344890327 |
|---|
|
| Anchor |
|---|
| _Toc385441672 |
|---|
| _Toc385441672 |
|---|
|
| Anchor |
|---|
| _Toc387747511 |
|---|
| _Toc387747511 |
|---|
|
| Anchor |
|---|
| _Toc387748784 |
|---|
| _Toc387748784 |
|---|
|
| Anchor |
|---|
| _Toc401309081 |
|---|
| _Toc401309081 |
|---|
|
Using Checkpoints| Anchor |
|---|
| _Toc315524817 |
|---|
| _Toc315524817 |
|---|
|
| Anchor |
|---|
| _Toc317062403 |
|---|
| _Toc317062403 |
|---|
|
Process flows, which have checkpoints, are recoverable. Checkpoint is an action which can be used in a process flow during it creation. There can be any number of checkpoints in a process flow. Checkpoints should not be used after an asynchronous activity which is generating a source stream. Otherwise after recovery the source stream generated by asynchronous activity will not available for the target activity which will be consuming this stream. To know how to add checkpoint refer to the section Using Actions in Process Flow .
| Anchor |
|---|
| _Toc315524818 |
|---|
| _Toc315524818 |
|---|
|
| Anchor |
|---|
| _Toc317062404 |
|---|
| _Toc317062404 |
|---|
|
| Anchor |
|---|
| _Toc344890328 |
|---|
| _Toc344890328 |
|---|
|
| Anchor |
|---|
| _Toc385441673 |
|---|
| _Toc385441673 |
|---|
|
| Anchor |
|---|
| _Toc387747512 |
|---|
| _Toc387747512 |
|---|
|
| Anchor |
|---|
| _Toc387748785 |
|---|
| _Toc387748785 |
|---|
|
| Anchor |
|---|
| _Toc401309082 |
|---|
| _Toc401309082 |
|---|
|
Using Human Workflow Activity
Process flows which use Human Work Flow activities, are recoverable. Human work flow activity itself acts as a checkpoint. To know how to add Human Workflow Activity in the process flow, refer to the section Creating Workflow Task section.
