8.3.12 Plug-ins that cannot be interrupted or skipped during debugging
Some plug-ins cannot be interrupted even if you attempt to interrupt step execution during debugging. If one of these plug-ins is encountered during debugging, the flow automatically advances to the succeeding step.
No. |
Plug-in name |
Can be interrupted |
Can be skipped |
|
|---|---|---|---|---|
1 |
Basic plug-ins |
General command plug-in |
Y |
Y |
2 |
File-transfer plug-in |
Y |
Y |
|
3 |
Repeated Execution Plug-in |
Y |
Y |
|
4 |
Email Notification Plug-in |
Y |
Y |
|
5 |
User-Response Wait Plug-in |
Y |
Y |
|
6 |
Standard Output Plug-in |
Y |
Y |
|
7 |
Terminal connect plug-in |
Y |
Y |
|
8 |
Terminal command plug-in |
Y |
Y |
|
9 |
Terminal disconnect plug-in |
Y |
Y |
|
10 |
Flow plug-in |
C |
N |
|
11 |
Interval plug-in |
Y |
Y |
|
12 |
Branch by returncode plug-in |
C |
N |
|
13 |
Test value plug-in |
Y |
Y |
|
14 |
Abnormal-end plug-in |
Y |
Y |
|
15 |
Branch by property value plug-in |
C |
N |
|
16 |
JavaScript plug-in |
Y |
Y |
|
17 |
File Export Plug-in |
Y |
Y |
|
18 |
Web Client Plug-in |
Y |
Y |
|
19 |
Content plug-ins |
Y |
Y |
|
20 |
Service component |
C |
N# |
|
21 |
Incompatible steps in service templates created in versions of JP1/AO earlier than 10-10 |
N |
N |
|
- Legend:
Y: Can be interrupted or skipped. N: Cannot be interrupted or skipped. C: Can be interrupted before the plug-in processing is performed, but cannot be interrupted after the plug-in is executed.
- #
A step that contains service components cannot be skipped. However, whether steps in the subordinate flow can be skipped is determined by plug-ins contained in each step.