This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 8cdaacf Automated deployment: 1565eac1a8bb05f5922a68f984981f89db7fbf1d
8cdaacf is described below
commit 8cdaacff3d066f826420b5843c83d8819dcb08ef
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu Mar 10 03:05:51 2022 +0000
Automated deployment: 1565eac1a8bb05f5922a68f984981f89db7fbf1d
---
.../dev/user_doc/guide/project/project-list.html | 10 +--
.../dev/user_doc/guide/project/project-list.json | 2 +-
.../dev/user_doc/guide/project/task-instance.html | 4 +-
.../dev/user_doc/guide/project/task-instance.json | 2 +-
.../guide/project/workflow-definition.html | 74 +++++++++++-----------
.../guide/project/workflow-definition.json | 2 +-
.../user_doc/guide/project/workflow-instance.html | 32 +++++-----
.../user_doc/guide/project/workflow-instance.json | 2 +-
.../guide/project/workflow-definition.html | 2 +-
.../guide/project/workflow-definition.json | 2 +-
10 files changed, 66 insertions(+), 66 deletions(-)
diff --git a/en-us/docs/dev/user_doc/guide/project/project-list.html
b/en-us/docs/dev/user_doc/guide/project/project-list.html
index d834dda..516c22f 100644
--- a/en-us/docs/dev/user_doc/guide/project/project-list.html
+++ b/en-us/docs/dev/user_doc/guide/project/project-list.html
@@ -10,7 +10,7 @@
<link rel="stylesheet" href="/build/vendor.23870e5.css">
</head>
<body>
- <div id="root"><div class="md2html docs-page" data-reactroot=""><header
class="header-container header-container-dark"><div class="header-body"><span
class="mobile-menu-btn mobile-menu-btn-dark"></span><a
href="/en-us/index.html"><img class="logo" src="/img/hlogo_white.svg"/></a><div
class="search search-dark"><span class="icon-search"></span></div><span
class="language-switch language-switch-dark">中</span><div
class="header-menu"><div><ul class="ant-menu whiteClass ant-menu-light ant-
[...]
+ <div id="root"><div class="md2html docs-page" data-reactroot=""><header
class="header-container header-container-dark"><div class="header-body"><span
class="mobile-menu-btn mobile-menu-btn-dark"></span><a
href="/en-us/index.html"><img class="logo" src="/img/hlogo_white.svg"/></a><div
class="search search-dark"><span class="icon-search"></span></div><span
class="language-switch language-switch-dark">中</span><div
class="header-menu"><div><ul class="ant-menu whiteClass ant-menu-light ant-
[...]
<h2>Create Project</h2>
<ul>
<li>
@@ -23,16 +23,16 @@
<h2>Project Home</h2>
<ul>
<li>
-<p>Click the project name link on the project management page to enter the
project home page, as shown in the figure below, the project home page contains
the task status statistics, process status statistics, and workflow definition
statistics of the project. The introduction for those metric:</p>
+<p>Click the project name link on the project management page to enter the
project home page, as shown in the figure below, the project home page contains
the task status statistics, process status statistics, and workflow definition
statistics of the project. The introduction for those metrics:</p>
</li>
<li>
-<p>Task status statistics: within the specified time range, count the number
of task instances as successful submission, running, ready to pause, pause,
ready to stop, stop, failure, success, fault tolerance, kill, and waiting
threads</p>
+<p>Task status statistics: within the specified time range, count the number
of task instances status as successful submission, running, ready to pause,
pause, ready to stop, stop, failure, success, need fault tolerance, kill and
waiting threads</p>
</li>
<li>
-<p>Process status statistics: within the specified time range, count the
number of the status of the workflow instance as submission success, running,
ready to pause, pause, ready to stop, stop, failure, success, fault tolerance,
kill, and waiting threads</p>
+<p>Process status statistics: within the specified time range, count the
number of workflow instances status as submission success, running, ready to
pause, pause, ready to stop, stop, failure, success, need fault tolerance, kill
and waiting threads</p>
</li>
<li>
-<p>Workflow definition statistics: Count the workflow definitions created by
this user and the workflow definitions granted to this user by the
administrator</p>
+<p>Workflow definition statistics: count the workflow definitions created by
this user and granted by the administrator</p>
<p align="center">
<img src="/img/project_home_en.png" width="80%" />
</p>
diff --git a/en-us/docs/dev/user_doc/guide/project/project-list.json
b/en-us/docs/dev/user_doc/guide/project/project-list.json
index 1ceabbc..b0ac67c 100644
--- a/en-us/docs/dev/user_doc/guide/project/project-list.json
+++ b/en-us/docs/dev/user_doc/guide/project/project-list.json
@@ -1,6 +1,6 @@
{
"filename": "project-list.md",
- "__html": "<h1>Project</h1>\n<h2>Create Project</h2>\n<ul>\n<li>\n<p>Click
"Project Management" to enter the project management page, click the
"Create Project" button, enter the project name, project description,
and click "Submit" to create a new project.</p>\n<p
align=\"center\">\n <img src=\"/img/create_project_en1.png\" width=\"80%\"
/>\n</p>\n</li>\n</ul>\n<h2>Project Home</h2>\n<ul>\n<li>\n<p>Click the project
name link on the project management [...]
+ "__html": "<h1>Project Management</h1>\n<h2>Create
Project</h2>\n<ul>\n<li>\n<p>Click "Project Management" to enter the
project management page, click the "Create Project" button, enter the
project name, project description, and click "Submit" to create a new
project.</p>\n<p align=\"center\">\n <img
src=\"/img/create_project_en1.png\" width=\"80%\"
/>\n</p>\n</li>\n</ul>\n<h2>Project Home</h2>\n<ul>\n<li>\n<p>Click the project
name link on the project [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/project/project-list.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/project/task-instance.html
b/en-us/docs/dev/user_doc/guide/project/task-instance.html
index 81cfe56..bf1fff7 100644
--- a/en-us/docs/dev/user_doc/guide/project/task-instance.html
+++ b/en-us/docs/dev/user_doc/guide/project/task-instance.html
@@ -13,13 +13,13 @@
<div id="root"><div class="md2html docs-page" data-reactroot=""><header
class="header-container header-container-dark"><div class="header-body"><span
class="mobile-menu-btn mobile-menu-btn-dark"></span><a
href="/en-us/index.html"><img class="logo" src="/img/hlogo_white.svg"/></a><div
class="search search-dark"><span class="icon-search"></span></div><span
class="language-switch language-switch-dark">中</span><div
class="header-menu"><div><ul class="ant-menu whiteClass ant-menu-light ant-
[...]
<ul>
<li>
-<p>Click Project Management -> Workflow -> Task Instance to enter the
task instance page, as shown in the figure below, click the name of the
workflow instance, you can jump to the workflow instance DAG chart to view the
task status.</p>
+<p>Click Project Management -> Workflow -> Task Instance. Enter the task
instance page, as shown in the figure below, click workflow instance name, you
can jump to the workflow instance DAG chart to view the task status.</p>
<p align="center">
<img src="/img/task-list-en.png" width="80%" />
</p>
</li>
<li>
-<p><span id=taskLog>View log：</span>Click the "view log" button in
the operation column to view the log of task execution.</p>
+<p><span id=taskLog>View log：</span>Click the "view log" button in
the operation column to view task execution log.</p>
<p align="center">
<img src="/img/task-log2-en.png" width="80%" />
</p>
diff --git a/en-us/docs/dev/user_doc/guide/project/task-instance.json
b/en-us/docs/dev/user_doc/guide/project/task-instance.json
index 6371b7d..8d277fa 100644
--- a/en-us/docs/dev/user_doc/guide/project/task-instance.json
+++ b/en-us/docs/dev/user_doc/guide/project/task-instance.json
@@ -1,6 +1,6 @@
{
"filename": "task-instance.md",
- "__html": "<h2>Task Instance</h2>\n<ul>\n<li>\n<p>Click Project Management
-> Workflow -> Task Instance to enter the task instance page, as shown in
the figure below, click the name of the workflow instance, you can jump to the
workflow instance DAG chart to view the task status.</p>\n <p
align=\"center\">\n <img src=\"/img/task-list-en.png\" width=\"80%\" />\n
</p>\n</li>\n<li>\n<p><span id=taskLog>View log：</span>Click the "view
log" button in the operation c [...]
+ "__html": "<h2>Task Instance</h2>\n<ul>\n<li>\n<p>Click Project Management
-> Workflow -> Task Instance. Enter the task instance page, as shown in
the figure below, click workflow instance name, you can jump to the workflow
instance DAG chart to view the task status.</p>\n <p align=\"center\">\n
<img src=\"/img/task-list-en.png\" width=\"80%\" />\n
</p>\n</li>\n<li>\n<p><span id=taskLog>View log：</span>Click the "view
log" button in the operation column to view [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/project/task-instance.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/project/workflow-definition.html
b/en-us/docs/dev/user_doc/guide/project/workflow-definition.html
index 8a55bed..d93afd2 100644
--- a/en-us/docs/dev/user_doc/guide/project/workflow-definition.html
+++ b/en-us/docs/dev/user_doc/guide/project/workflow-definition.html
@@ -14,31 +14,31 @@
<h2><span id=creatDag> Create Workflow Definition</span></h2>
<ul>
<li>
-<p>Click Project Management -> Workflow -> Workflow Definition to enter
the workflow definition page, and click the "Create Workflow" button
to enter the <strong>workflow DAG edit</strong> page, as shown in the following
figure:</p>
+<p>Click Project Management -> Workflow -> Workflow Definition, enter
the workflow definition page, and click the "Create Workflow" button
to enter the <strong>workflow DAG edit</strong> page, as shown in the following
figure:</p>
<p align="center">
<img src="/img/dag5.png" width="80%" />
</p>
</li>
<li>
-<p>Drag in the toolbar <img src="/img/tasks/icons/shell.png" width="15"/> Add
a Shell task to the drawing board, as shown in the figure below:</p>
+<p>Drag from the toolbar <img src="/img/tasks/icons/shell.png" width="15"/> to
the canvas, to add a shell task to the canvas, as shown in the figure below:</p>
<p><img src="/img/tasks/demo/shell.jpg" alt="demo-shell-simple"></p>
</li>
<li>
-<p><strong>Add parameter settings for this shell task:</strong></p>
+<p><strong>Add parameter settings for shell task:</strong></p>
</li>
</ul>
<ol>
-<li>Fill in the "Node Name", "Description", and
"Script" fields;</li>
-<li>Check “Normal” for “Run Flag”. If “Prohibit Execution” is checked, the
task will not be executed when the workflow runs;</li>
-<li>Select "Task Priority": When the number of worker threads is
insufficient, high-level tasks will be executed first in the execution queue,
and tasks with the same priority will be executed in the order of first in,
first out;</li>
-<li>Timeout alarm (optional): Check the timeout alarm, timeout failure, and
fill in the "timeout period". When the task execution time exceeds
<strong>timeout period</strong>, an alert email will be sent and the task
timeout fails;</li>
-<li>Resources (optional). Resource files are files created or uploaded on the
Resource Center -> File Management page. For example, the file name is
<code>test.sh</code>, and the command to call the resource in the script is
<code>sh test.sh</code>;</li>
+<li>Fill in the "Node Name", "Description" and
"Script" fields;</li>
+<li>Check “Normal” for “Run Flag”. If “Prohibit Execution” is checked, the
task will not execute when the workflow runs;</li>
+<li>Select "Task Priority": when the number of worker threads is
insufficient, high priority tasks will execute first in the execution queue,
and tasks with the same priority will execute in the order of first in, first
out;</li>
+<li>Timeout alarm (optional): check the timeout alarm, timeout failure, and
fill in the "timeout period". When the task execution time exceeds
<strong>timeout period</strong>, an alert email will send and the task timeout
fails;</li>
+<li>Resources (optional). Resources are files create or upload in the Resource
Center -> File Management page. For example, the file name is
<code>test.sh</code>, and the command to call the resource in the script is
<code>sh test.sh</code>;</li>
<li>Custom parameters (optional), refer to <a
href="#UserDefinedParameters">Custom Parameters</a>;</li>
<li>Click the "Confirm Add" button to save the task settings.</li>
</ol>
<ul>
<li>
-<p><strong>Increase the order of task execution:</strong> Click the icon in
the upper right corner <img src="/img/line.png" width="35"/> to connect the
task; as shown in the figure below, task 2 and task 3 are executed in parallel,
When task 1 finished executing, tasks 2 and 3 will be executed
simultaneously.</p>
+<p><strong>Set dependencies between tasks:</strong> Click the icon in the
upper right corner <img src="/img/line.png" width="35"/> to connect the task;
as shown in the figure below, task 2 and task 3 execute in parallel, When task
1 finished execution, tasks 2 and 3 will execute simultaneously.</p>
<p align="center">
<img src="/img/dag6.png" width="80%" />
</p>
@@ -50,7 +50,7 @@
</p>
</li>
<li>
-<p><strong>Save workflow definition:</strong> Click the "Save"
button, and the "Set DAG chart name" pop-up box will pop up, as shown
in the figure below. Enter the workflow definition name, workflow definition
description, and set global parameters (optional, refer to <a
href="#UserDefinedParameters"> Custom parameters</a>), click the
"Add" button, and the workflow definition is created successfully.</p>
+<p><strong>Save workflow definition:</strong> Click the "Save"
button, and the "Set DAG chart name" window pops up, as shown in the
figure below. Enter the workflow definition name, workflow definition
description, and set global parameters (optional, refer to <a
href="#UserDefinedParameters">Custom parameters</a>), click the "Add"
button to finish workflow definition creation.</p>
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
@@ -66,14 +66,14 @@
</p>
The operation functions of the workflow definition list are as follows:
<ul>
-<li><strong>Edit:</strong> Only "offline" workflow definitions can
be edited. Workflow DAG editing is the same as <a href="#creatDag">Create
Workflow Definition</a>.</li>
-<li><strong>Online:</strong> When the workflow status is "Offline",
used to online workflow. Only the workflow in the "Online" state can
run, but cannot be edited.</li>
-<li><strong>Offline:</strong> When the workflow status is "Online",
used to offline workflow. Only the workflow in the "Offline" state
can be edited, but not run.</li>
+<li><strong>Edit:</strong> Only "Offline" workflow definitions can
be edited. Workflow DAG editing is the same as <a href="#creatDag">Create
Workflow Definition</a></li>
+<li><strong>Online:</strong> When the workflow status is "Offline",
used to make workflow online. Only the workflow in the "Online" state
can run, but cannot edit</li>
+<li><strong>Offline:</strong> When the workflow status is "Online",
used to make workflow offline. Only the workflow in the "Offline"
state can be edited, but cannot run</li>
<li><strong>Run:</strong> Only workflow in the online state can run. See <a
href="#runWorkflow">2.3.3 Run Workflow</a> for the operation steps</li>
-<li><strong>Timing:</strong> Timing can only be set in online workflows, and
the system automatically schedules the workflow to run on a regular basis. The
status after creating a timing is "offline", and the timing must be
online on the timing management page to take effect. See <a
href="#creatTiming">2.3.4 Workflow Timing</a> for timing operation steps.</li>
-<li><strong>Timing Management:</strong> The timing management page can be
edited, online/offline, and deleted.</li>
-<li><strong>Delete:</strong> Delete the workflow definition.</li>
-<li><strong>Download:</strong> Download workflow definition to local.</li>
+<li><strong>Timing:</strong> Timing can only set to online workflows, and the
system automatically schedules to run the workflow on time. The status after
creating a timing setting is "offline", and the timing must set
online on the timing management page to make effect. See <a
href="#creatTiming">2.3.4 Workflow Timing</a> for timing operation steps</li>
+<li><strong>Timing Management:</strong> The timing management page can edit,
online or offline and delete timing</li>
+<li><strong>Delete:</strong> Delete the workflow definition</li>
+<li><strong>Download:</strong> Download workflow definition to local</li>
<li><strong>Tree Diagram:</strong> Display the task node type and task status
in a tree structure, as shown in the figure below:<p align="center">
<img src="/img/tree_en.png" width="80%" />
</p>
@@ -82,61 +82,61 @@ The operation functions of the workflow definition list are
as follows:
<h2><span id=runWorkflow>Run the Workflow</span></h2>
<ul>
<li>
-<p>Click Project Management -> Workflow -> Workflow Definition to enter
the workflow definition page, as shown in the figure below, click the "Go
Online" button <img src="/img/online.png" width="35"/>，Go online
workflow.</p>
+<p>Click Project Management -> Workflow -> Workflow Definition to enter
the workflow definition page, as shown in the figure below, click the "Go
Online" button <img src="/img/online.png" width="35"/>to make workflow
online.</p>
<p align="center">
<img src="/img/work_list_en.png" width="80%" />
</p>
</li>
<li>
-<p>Click the "Run" button to pop up the startup parameter setting
pop-up box, as shown in the figure below, set the startup parameters, click the
"Run" button in the pop-up box, the workflow starts running, and the
workflow instance page generates a workflow instance.</p>
+<p>Click the "Run" button to pop up the startup parameter setting
window, as shown in the figure below, set the startup parameters, click the
"Run" button in the pop-up box, the workflow starts running, and the
workflow instance page generates a workflow instance.</p>
<p align="center">
<img src="/img/run_work_en.png" width="80%" />
</p>
<span id=runParamers>Description of workflow operating parameters:</span>
-<pre><code>* Failure strategy: When a task node fails to execute, other
parallel task nodes need to execute the strategy. "Continue" means:
after a certain task fails, other task nodes execute normally; "End"
means: terminate all tasks being executed, and terminate the entire process.
-* Notification strategy: When the process is over, the process execution
information notification email is sent according to the process status,
including any status is not sent, successful sent, failed sent, successful or
failed sent.
-* Process priority: The priority of process operation, divided into five
levels: highest (HIGHEST), high (HIGH), medium (MEDIUM), low (LOW), and lowest
(LOWEST). When the number of master threads is insufficient, high-level
processes will be executed first in the execution queue, and processes with the
same priority will be executed in a first-in first-out order.
-* Worker group: The process can only be executed in the specified worker
machine group. The default is Default, which can be executed on any worker.
-* Notification group: select notification strategy||timeout alarm||when fault
tolerance occurs, process information or email will be sent to all members in
the notification group.
-* Recipient: Select notification policy||Timeout alarm||When fault tolerance
occurs, process information or alarm email will be sent to the recipient list.
-* Cc: Select the notification strategy||Timeout alarm||When fault tolerance
occurs, the process information or warning email will be copied to the CC list.
-* Startup parameter: Set or overwrite global parameter values when starting a
new process instance.
-* Complement: Two modes including serial complement and parallel complement.
Serial complement: Within the specified time range, the complements are
executed from the start date to the end date and N process instances are
generated in turn; parallel complement: within the specified time range,
multiple days are complemented at the same time to generate N process instances.
+<pre><code>* Failure strategy: When a task node fails to execute, other
parallel task nodes need to execute this strategy. "Continue" means:
after a certain task fails, other task nodes execute normally; "End"
means: terminate all tasks execution, and terminate the entire process
+* Notification strategy: When the process is over, send the process execution
result notification email according to the process status, options including no
send, send if sucess, send of failure, send whatever result
+* Process priority: The priority of process operation, divide into five
levels: highest (HIGHEST), high (HIGH), medium (MEDIUM), low (LOW), and lowest
(LOWEST). When the number of master threads is insufficient, high priority
processes will execute first in the execution queue, and processes with the
same priority will execute in the order of first in, first out;
+* Worker group: The process can only be executed in the specified worker
machine group. The default is `Default`, which can execute on any worker
+* Notification group: select notification strategy||timeout alarm||when fault
tolerance occurs, process result information or email will send to all members
in the notification group
+* Recipient: select notification policy||timeout alarm||when fault tolerance
occurs, process result information or alarm email will be sent to the recipient
list
+* Cc: select notification policy||timeout alarm||when fault tolerance occurs,
the process result information or warning email will be copied to the CC list
+* Startup parameter: Set or overwrite global parameter values when starting a
new process instance
+* Complement: two modes including serial complement and parallel complement.
Serial complement: within the specified time range, the complements are
executed from the start date to the end date and N process instances are
generated in turn; parallel complement: within the specified time range,
multiple days are complemented at the same time to generate N process instances.
</code></pre>
<ul>
-<li>For example, you need to fill in the data from May 1 to May 10.</li>
+<li>You can select complement time range (only support continuous date) when
executing a timing workflow definition. For example, need to fill in the data
from 1st May to 10th May, as shown in the figure below:</li>
</ul>
<p align="center">
<img src="/img/complement_en1.png" width="80%" />
</p>
<blockquote>
-<p>Serial mode: The complement is executed sequentially from May 1 to May 10,
and ten process instances are generated on the process instance page;</p>
+<p>Serial mode: the complement execute sequentially from 1st May to 10th May,
and the process instance page generates 10 process instances;</p>
</blockquote>
<blockquote>
-<p>Parallel mode: The tasks from May 1 to may 10 are executed simultaneously,
and 10 process instances are generated on the process instance page.</p>
+<p>Parallel mode: The tasks from 1st May to 10th May execute simultaneously,
and the process instance page generates 10 process instances;</p>
</blockquote>
</li>
</ul>
<h2><span id=creatTiming>Workflow Timing</span></h2>
<ul>
-<li>Create timing: Click Project Management->Workflow->Workflow
Definition, enter the workflow definition page, go online the workflow, click
the "timing" button <img src="/img/timing.png" width="35"/> ,The
timing parameter setting dialog box pops up, as shown in the figure below:<p
align="center">
+<li>Create timing: Click Project Management->Workflow->Workflow
Definition, enter the workflow definition page, make the workflow online, click
the "timing" button <img src="/img/timing.png" width="35"/> , the
timing parameter setting dialog box pops up, as shown in the figure below:<p
align="center">
<img src="/img/time_schedule_en.png" width="80%" />
</p>
</li>
-<li>Choose the start and end time. In the start and end time range, the
workflow is run at regular intervals; not in the start and end time range, no
more regular workflow instances are generated.</li>
-<li>Add a timing that is executed once every day at 5 AM, as shown in the
following figure:<p align="center">
+<li>Choose the start and end time. In the time range, the workflow runs at
regular intervals; If not in the time range, no regular workflow instances
generate.</li>
+<li>Add a timing that execute once a day at 5 AM, as shown in the following
figure:<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
</li>
<li>Failure strategy, notification strategy, process priority, worker group,
notification group, recipient, and CC are the same as <a
href="#runParamers">workflow running parameters</a>.</li>
-<li>Click the "Create" button to create the timing successfully. At
this time, the timing status is "<strong>Offline</strong>" and the
timing needs to be <strong>Online</strong> to take effect.</li>
-<li>Timing online: Click the "timing management" button <img
src="/img/timeManagement.png" width="35"/>, enter the timing management page,
click the "online" button, the timing status will change to
"online", as shown in the below figure, the workflow takes effect
regularly.<p align="center">
+<li>Click the "Create" button to create the timing. Now the timing
status is "<strong>Offline</strong>" and the timing needs to be
<strong>Online</strong> to make effect.</li>
+<li>Timing online: Click the "Timing Management" button <img
src="/img/timeManagement.png" width="35"/>, enter the timing management page,
click the "online" button, the timing status will change to
"online", as shown in the below figure, the workflow makes effect
regularly.<p align="center">
<img src="/img/time-manage-list-en.png" width="80%" />
</p>
</li>
</ul>
<h2>Import Workflow</h2>
-<p>Click Project Management -> Workflow -> Workflow Definition to enter
the workflow definition page, click the "Import Workflow" button to
import the local workflow file, the workflow definition list displays the
imported workflow, and the status is offline.</p>
+<p>Click Project Management -> Workflow -> Workflow Definition to enter
the workflow definition page, click the "Import Workflow" button to
import the local workflow file, the workflow definition list displays the
imported workflow and the status is offline.</p>
</div></section><footer class="footer-container"><div
class="footer-body"><div><h3>About us</h3><h4>Do you need feedback? Please
contact us through the following ways.</h4></div><div
class="contact-container"><ul><li><a
href="/en-us/community/development/subscribe.html"><img class="img-base"
src="/img/emailgray.png"/><img class="img-change"
src="/img/emailblue.png"/><p>Email List</p></a></li><li><a
href="https://twitter.com/dolphinschedule";><img class="img-base"
src="/img/twittergray.png [...]
<script
src="//cdn.jsdelivr.net/npm/[email protected]/dist/react-with-addons.min.js"></script>
<script
src="//cdn.jsdelivr.net/npm/[email protected]/dist/react-dom.min.js"></script>
diff --git a/en-us/docs/dev/user_doc/guide/project/workflow-definition.json
b/en-us/docs/dev/user_doc/guide/project/workflow-definition.json
index e46e2f9..c9cc893 100644
--- a/en-us/docs/dev/user_doc/guide/project/workflow-definition.json
+++ b/en-us/docs/dev/user_doc/guide/project/workflow-definition.json
@@ -1,6 +1,6 @@
{
"filename": "workflow-definition.md",
- "__html": "<h1>Workflow Definition</h1>\n<h2><span id=creatDag> Create
Workflow Definition</span></h2>\n<ul>\n<li>\n<p>Click Project Management ->
Workflow -> Workflow Definition to enter the workflow definition page, and
click the "Create Workflow" button to enter the <strong>workflow DAG
edit</strong> page, as shown in the following figure:</p>\n<p
align=\"center\">\n <img src=\"/img/dag5.png\" width=\"80%\"
/>\n</p>\n</li>\n<li>\n<p>Drag in the toolbar <img src=\" [...]
+ "__html": "<h1>Workflow Definition</h1>\n<h2><span id=creatDag> Create
Workflow Definition</span></h2>\n<ul>\n<li>\n<p>Click Project Management ->
Workflow -> Workflow Definition, enter the workflow definition page, and
click the "Create Workflow" button to enter the <strong>workflow DAG
edit</strong> page, as shown in the following figure:</p>\n<p
align=\"center\">\n <img src=\"/img/dag5.png\" width=\"80%\"
/>\n</p>\n</li>\n<li>\n<p>Drag from the toolbar <img src=\" [...]
"link":
"/dist/en-us/docs/dev/user_doc/guide/project/workflow-definition.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/docs/dev/user_doc/guide/project/workflow-instance.html
b/en-us/docs/dev/user_doc/guide/project/workflow-instance.html
index 1fdd698..b672b4f 100644
--- a/en-us/docs/dev/user_doc/guide/project/workflow-instance.html
+++ b/en-us/docs/dev/user_doc/guide/project/workflow-instance.html
@@ -13,59 +13,59 @@
<div id="root"><div class="md2html docs-page" data-reactroot=""><header
class="header-container header-container-dark"><div class="header-body"><span
class="mobile-menu-btn mobile-menu-btn-dark"></span><a
href="/en-us/index.html"><img class="logo" src="/img/hlogo_white.svg"/></a><div
class="search search-dark"><span class="icon-search"></span></div><span
class="language-switch language-switch-dark">中</span><div
class="header-menu"><div><ul class="ant-menu whiteClass ant-menu-light ant-
[...]
<h2>View Workflow Instance</h2>
<ul>
-<li>Click Project Management -> Workflow -> Workflow Instance to enter
the Workflow Instance page, as shown in the figure below: <p align="center">
+<li>Click Project Management -> Workflow -> Workflow Instance, enter the
Workflow Instance page, as shown in the figure below: <p align="center">
<img src="/img/instance-list-en.png" width="80%" />
</p>
</li>
-<li>Click the workflow name to enter the DAG view page to view the task
execution status, as shown in the figure below.<p align="center">
+<li>Click the workflow name to enter the DAG view page, and check the task
execution status, as shown in the figure below:<p align="center">
<img src="/img/instance-runs-en.png" width="80%" />
</p>
</li>
</ul>
<h2>View Task Log</h2>
<ul>
-<li>Enter the workflow instance page, click the workflow name, enter the DAG
view page, double-click the task node, as shown in the following figure: <p
align="center">
+<li>Enter the workflow instance page, click the workflow name, enter the DAG
view page, double-click the task node, as shown in the figure below: <p
align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
</li>
-<li>Click "View Log", a log pop-up box will pop up, as shown in the
figure below, the task log can also be viewed on the task instance page, refer
to <a href="#taskLog">Task View Log</a>。 <p align="center">
+<li>Click "View Log", a log window pops up, as shown in the figure
below, you can also view the task log on the task instance page, refer to <a
href="#taskLog">Task View Log</a> <p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
</li>
</ul>
<h2>View Task History</h2>
<ul>
-<li>Click Project Management -> Workflow -> Workflow Instance to enter
the workflow instance page, and click the workflow name to enter the workflow
DAG page;</li>
+<li>Click Project Management -> Workflow -> Workflow Instance, enter the
workflow instance page, and click the workflow name to enter the workflow DAG
page;</li>
<li>Double-click the task node, as shown in the figure below, click "View
History" to jump to the task instance page, and display a list of task
instances running by the workflow instance <p align="center">
<img src="/img/task_history_en.png" width="80%" />
</p>
</li>
</ul>
-<h2>View Operating Parameters</h2>
+<h2>View Operation Parameters</h2>
<ul>
-<li>Click Project Management -> Workflow -> Workflow Instance to enter
the workflow instance page, and click the workflow name to enter the workflow
DAG page;</li>
+<li>Click Project Management -> Workflow -> Workflow Instance, enter the
workflow instance page, and click the workflow name to enter the workflow DAG
page;</li>
<li>Click the icon in the upper left corner <img
src="/img/run_params_button.png" width="35"/>，View the startup parameters of
the workflow instance; click the icon <img src="/img/global_param.png"
width="35"/>，View the global and local parameters of the workflow instance, as
shown in the following figure: <p align="center">
<img src="/img/run_params_en.png" width="80%" />
</p>
</li>
</ul>
<h2>Workflow Instance Operation Function</h2>
-<p>Click Project Management -> Workflow -> Workflow Instance to enter
the Workflow Instance page, as shown in the figure below:</p>
+<p>Click Project Management -> Workflow -> Workflow Instance, enter the
workflow instance page, as shown in the figure below:</p>
<p align="center">
<img src="/img/instance-list-en.png" width="80%" />
</p>
<ul>
-<li><strong>Edit：</strong> Only terminated processes can be edited. Click the
"Edit" button or the name of the workflow instance to enter the DAG
edit page. After edit, click the "Save" button to pop up the Save DAG
pop-up box, as shown in the figure below. In the pop-up box, check
"Whether to update to workflow definition" and save After that, the
workflow definition will be updated; if it is not checked, the workflow
definition will not be updated. <p al [...]
+<li><strong>Edit：</strong> only can edit terminated processes. Click the
"Edit" button or the workflow instance name to enter the DAG edit
page. After the edit, click the "Save" button to confirm, as shown in
the figure below. In the pop-up box, check "Whether to update to workflow
definition" to update the workflow definition; if not checked, no effect
on the workflow definition <p align="center">
<img src="/img/editDag-en.png" width="80%" />
</p>
</li>
-<li><strong>Rerun：</strong> Re-execute the terminated process.</li>
-<li><strong>Recovery failed：</strong> For failed processes, you can perform
recovery operations, starting from the failed node.</li>
-<li><strong>Stop：</strong> To <strong>stop</strong> the running process, the
background will first <code>kill</code>worker process, and then execute
<code>kill -9</code> operation</li>
-<li><strong>Pause:</strong> Perform a <strong>pause</strong> operation on the
running process, the system status will change to <strong>waiting for
execution</strong>, it will wait for the end of the task being executed, and
pause the next task to be executed.</li>
-<li><strong>Resume pause:</strong> To resume the paused process, start running
directly from the <strong>paused node</strong></li>
-<li><strong>Delete:</strong> Delete the workflow instance and the task
instance under the workflow instance</li>
-<li><strong>Gantt chart:</strong> The vertical axis of the Gantt chart is the
topological sorting of task instances under a certain workflow instance, and
the horizontal axis is the running time of the task instances, as shown in the
figure: <p align="center">
+<li><strong>Rerun：</strong> re-execute the terminated process</li>
+<li><strong>Recovery failed：</strong> for failed processes, you can perform
failure recovery operations, starting from the failed node</li>
+<li><strong>Stop：</strong> to <strong>stop</strong> the running process, the
background code will first <code>kill</code> the worker process, and then
execute <code>kill -9</code> operation</li>
+<li><strong>Pause:</strong> Perform a <strong>pause</strong> operation on the
running process, the system status will change to <strong>waiting for
execution</strong>, it will wait for the task to finish, and pause the next
sequence task.</li>
+<li><strong>Resume pause:</strong> to resume the paused process, start running
directly from the <strong>paused node</strong></li>
+<li><strong>Delete:</strong> delete the workflow instance and the task
instance under the workflow instance</li>
+<li><strong>Gantt chart:</strong> the vertical axis of the Gantt chart is the
topological sorting of task instances of the workflow instance, and the
horizontal axis is the running time of the task instances, as shown in the
figure below: <p align="center">
<img src="/img/gantt-en.png" width="80%" />
</p>
</li>
diff --git a/en-us/docs/dev/user_doc/guide/project/workflow-instance.json
b/en-us/docs/dev/user_doc/guide/project/workflow-instance.json
index bcad5ab..cff2393 100644
--- a/en-us/docs/dev/user_doc/guide/project/workflow-instance.json
+++ b/en-us/docs/dev/user_doc/guide/project/workflow-instance.json
@@ -1,6 +1,6 @@
{
"filename": "workflow-instance.md",
- "__html": "<h1>Workflow Instance</h1>\n<h2>View Workflow
Instance</h2>\n<ul>\n<li>Click Project Management -> Workflow -> Workflow
Instance to enter the Workflow Instance page, as shown in the figure below:
<p align=\"center\">\n <img src=\"/img/instance-list-en.png\"
width=\"80%\" />\n </p>\n</li>\n<li>Click the workflow name to enter the DAG
view page to view the task execution status, as shown in the figure below.<p
align=\"center\">\n <img src=\"/img/instance-runs-e [...]
+ "__html": "<h1>Workflow Instance</h1>\n<h2>View Workflow
Instance</h2>\n<ul>\n<li>Click Project Management -> Workflow -> Workflow
Instance, enter the Workflow Instance page, as shown in the figure below: <p
align=\"center\">\n <img src=\"/img/instance-list-en.png\" width=\"80%\"
/>\n </p>\n</li>\n<li>Click the workflow name to enter the DAG view page, and
check the task execution status, as shown in the figure below:<p
align=\"center\">\n <img src=\"/img/instance-runs- [...]
"link": "/dist/en-us/docs/dev/user_doc/guide/project/workflow-instance.html",
"meta": {}
}
\ No newline at end of file
diff --git a/zh-cn/docs/dev/user_doc/guide/project/workflow-definition.html
b/zh-cn/docs/dev/user_doc/guide/project/workflow-definition.html
index 2b2aff7..b230e85 100644
--- a/zh-cn/docs/dev/user_doc/guide/project/workflow-definition.html
+++ b/zh-cn/docs/dev/user_doc/guide/project/workflow-definition.html
@@ -36,7 +36,7 @@
</ol>
</li>
<li>
-<p><strong>增加任务执行的先后顺序：</strong> 点击右上角图标<img src="/img/line.png"
width="35"/>连接任务；如下图所示，任务2和任务3并行执行，当任务1执行完，任务2、3会同时执行。</p>
+<p><strong>配置任务之间的依赖关系：</strong> 点击右上角图标<img src="/img/line.png"
width="35"/>连接任务；如下图所示，任务2和任务3并行执行，当任务1执行完，任务2、3会同时执行。</p>
<p align="center">
<img src="/img/dag2.png" width="80%" />
</p>
diff --git a/zh-cn/docs/dev/user_doc/guide/project/workflow-definition.json
b/zh-cn/docs/dev/user_doc/guide/project/workflow-definition.json
index 2ecd13a..ccbb57f 100644
--- a/zh-cn/docs/dev/user_doc/guide/project/workflow-definition.json
+++ b/zh-cn/docs/dev/user_doc/guide/project/workflow-definition.json
@@ -1,6 +1,6 @@
{
"filename": "workflow-definition.md",
- "__html": "<h1>工作流定义</h1>\n<h2><span
id=creatDag>创建工作流定义</span></h2>\n<ul>\n<li>\n<p>点击项目管理->工作流->工作流定义，进入工作流定义页面，点击“创建工作流”按钮，进入<strong>工作流DAG编辑</strong>页面，如下图所示：</p>\n
<p align=\"center\">\n <img src=\"/img/dag0.png\" width=\"80%\" />\n
</p> \n</li>\n<li>\n<p>工具栏中拖拽 <img src=\"/img/tasks/icons/shell.png\"
width=\"15\"/> 到画板中，新增一个Shell任务,如下图所示：\n<img src=\"/img/tasks/demo/shell.jpg\"
alt=\"demo-shell-simple\"></p>\n</li>\n<li>\n<p><strong>添加shell任务的参数设置：</strong></p>\n<ol
[...]
+ "__html": "<h1>工作流定义</h1>\n<h2><span
id=creatDag>创建工作流定义</span></h2>\n<ul>\n<li>\n<p>点击项目管理->工作流->工作流定义，进入工作流定义页面，点击“创建工作流”按钮，进入<strong>工作流DAG编辑</strong>页面，如下图所示：</p>\n
<p align=\"center\">\n <img src=\"/img/dag0.png\" width=\"80%\" />\n
</p> \n</li>\n<li>\n<p>工具栏中拖拽 <img src=\"/img/tasks/icons/shell.png\"
width=\"15\"/> 到画板中，新增一个Shell任务,如下图所示：\n<img src=\"/img/tasks/demo/shell.jpg\"
alt=\"demo-shell-simple\"></p>\n</li>\n<li>\n<p><strong>添加shell任务的参数设置：</strong></p>\n<ol
[...]
"link":
"/dist/zh-cn/docs/dev/user_doc/guide/project/workflow-definition.html",
"meta": {}
}
\ No newline at end of file
