This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hop-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 004a768887 Website updated to b04100c
004a768887 is described below
commit 004a768887e609ae21e6d5e3a3225364cb002dd6
Author: jenkins <[email protected]>
AuthorDate: Wed Nov 4 17:37:18 2026 +0000
Website updated to b04100c
---
.../next/apache-release/creating-a-release.html | 3 ++
dev-manual/next/hopweb/index.html | 4 +-
dev-manual/next/writing-documentation.html | 59 +++++++++++++++++++++
.../_images/hop-gui/pipeline/logging-pipeline.png | Bin 20143 -> 285408 bytes
.../_images/hop-gui/pipeline/problems-pipeline.png | Bin 0 -> 107134 bytes
.../pipeline/transform-metrics-pipeline.png | Bin 12135 -> 144214 bytes
manual/next/pipeline/beam/beam-samples-flink.html | 2 +-
.../next/pipeline/run-preview-debug-pipeline.html | 57 +++++++++++++++++---
.../next/pipeline/transforms/simple-mapping.html | 10 ++--
manual/next/workflow/actions/deletefiles.html | 4 +-
manual/next/workflow/actions/evalfilesmetrics.html | 2 +-
manual/next/workflow/actions/movefiles.html | 2 +-
.../workflow/actions/processresultfilenames.html | 2 +-
manual/next/workflow/actions/waitforfile.html | 2 +-
manual/next/workflow/actions/xmlwellformed.html | 4 +-
manual/next/workflow/actions/zipfile.html | 8 +--
manual/next/workflow/run-debug-workflow.html | 5 +-
17 files changed, 137 insertions(+), 27 deletions(-)
diff --git a/dev-manual/next/apache-release/creating-a-release.html
b/dev-manual/next/apache-release/creating-a-release.html
index e8b1f30ecf..ac0cfcdb2c 100644
--- a/dev-manual/next/apache-release/creating-a-release.html
+++ b/dev-manual/next/apache-release/creating-a-release.html
@@ -1232,6 +1232,9 @@ Cheers,
<div class="paragraph">
<p>Remove the <code>prerelease</code> and <code>display_version</code>
attributes</p>
</div>
+<div class="paragraph">
+<p>Check that the version attributes under <code>asciidoc.attributes</code> in
both files still match the poms, see <a
href="../writing-documentation.html#_version_attributes" class="xref
page">Version attributes</a>.</p>
+</div>
</div>
</div>
</div>
diff --git a/dev-manual/next/hopweb/index.html
b/dev-manual/next/hopweb/index.html
index 63b9b72d5f..414eda0026 100644
--- a/dev-manual/next/hopweb/index.html
+++ b/dev-manual/next/hopweb/index.html
@@ -704,7 +704,7 @@ This should get you started to make modifications or create
your own version ent
<p>We’ll use Apache Tomcat in this example. If you use another
application server, the process should be similar.</p>
</div>
<div class="paragraph">
-<p>Hop 2.x is built with Java 21, so you’ll need to <a
href="https://tomcat.apache.org/download-10.cgi" rel="noopener"
target="_blank">download the latest Tomcat 10</a> (or use the official Tomcat
10 Docker image).</p>
+<p>This version of Hop is built with Java 21, so you’ll need to <a
href="https://tomcat.apache.org/download-10.cgi" rel="noopener"
target="_blank">download the latest Tomcat 10</a> (or use the official Tomcat
10 Docker image).</p>
</div>
<div class="paragraph">
<p>Copy or extract the following files from your Hop build, where
<code>$CATALINA_HOME</code> is your Tomcat installation folder.</p>
@@ -926,7 +926,7 @@ Open <a href="http://localhost:8080/ui" class="bare"
rel="noopener" target="_bla
<p><strong>Check Tomcat logs</strong>:
<code>$CATALINA_HOME/logs/catalina.out</code> for errors</p>
</li>
<li>
-<p><strong>Verify Java 21</strong>: Run <code>java -version</code> (should
show version 17)</p>
+<p><strong>Verify Java 21</strong>: Run <code>java -version</code> (should
show version 21)</p>
</li>
<li>
<p><strong>Check port availability</strong>: <code>lsof -i :8080</code>
(Linux/Mac) - port 8080 must be free</p>
diff --git a/dev-manual/next/writing-documentation.html
b/dev-manual/next/writing-documentation.html
index 97639ecdd2..e4370785e9 100644
--- a/dev-manual/next/writing-documentation.html
+++ b/dev-manual/next/writing-documentation.html
@@ -717,6 +717,65 @@ The pull request build rejects cross-manual xrefs without
a version.</p>
</div>
</div>
<div class="sect1">
+<h2 id="_version_attributes"><a class="link"
href="#_version_attributes">Version attributes</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The versions of Java, Apache Beam, Spark and Flink that Hop uses are
attributes in the <code>antora.yml</code> of the manual, so a page
doesn’t repeat the number:</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<colgroup>
+<col style="width: 25%;">
+<col style="width: 25%;">
+<col style="width: 50%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Attribute</th>
+<th class="tableblock halign-left valign-top">Manual</th>
+<th class="tableblock halign-left valign-top">Comes from</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>{java-version}</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">user and
dev manual</p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>target.jdk.version</code> in the root
<code>pom.xml</code></p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>{beam-version}</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">user
manual</p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>apache-beam.version</code> in the root
<code>pom.xml</code></p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>{beam-spark-version}</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">user
manual</p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>spark.version</code> in
<code>plugins/engines/beam/pom.xml</code> (the Spark of the Beam Spark
runner)</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>{spark-version}</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">user
manual</p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>spark.version</code> in
<code>plugins/engines/spark/pom.xml</code> (the native Spark engine)</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>{flink-version}</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">user
manual</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">the
<code>beam-runners-flink-<version></code> dependency in
<code>plugins/engines/beam/pom.xml</code></p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>Use an attribute where the text means the version Hop uses now: <code>Hop
requires Java {java-version}</code>.
+Keep the number where it shouldn’t change with an upgrade: a past
version (<code>since 2.15.0</code>), a measurement or a log example, a table
with a row per release, or the behaviour of one specific version of a library.
+A code block only replaces attributes when it has
<code>subs="attributes+"</code>:
<code>[source,bash,subs="attributes+"]</code>.</p>
+</div>
+<div class="paragraph">
+<p>When a pull request changes one of these versions in a pom, it also updates
the attribute in the <code>antora.yml</code> files listed above, so the
<code>next</code> documentation shows the new version.
+A comment next to each of them in the poms says so.
+A new Java version also changes the JRE that <code>docker/Dockerfile</code>
installs, which <a href="docker-build.html" class="xref page">Building the
Docker images</a> and the Docker container page of the user manual describe
with <code>{java-version}</code>.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
<h2 id="_previewing_the_documentation_locally"><a class="link"
href="#_previewing_the_documentation_locally">Previewing the documentation
locally</a></h2>
<div class="sectionbody">
<div class="paragraph">
diff --git a/manual/next/_images/hop-gui/pipeline/logging-pipeline.png
b/manual/next/_images/hop-gui/pipeline/logging-pipeline.png
index 5e41578f2d..4042dbab52 100644
Binary files a/manual/next/_images/hop-gui/pipeline/logging-pipeline.png and
b/manual/next/_images/hop-gui/pipeline/logging-pipeline.png differ
diff --git a/manual/next/_images/hop-gui/pipeline/problems-pipeline.png
b/manual/next/_images/hop-gui/pipeline/problems-pipeline.png
new file mode 100644
index 0000000000..e0d7fa03af
Binary files /dev/null and
b/manual/next/_images/hop-gui/pipeline/problems-pipeline.png differ
diff --git
a/manual/next/_images/hop-gui/pipeline/transform-metrics-pipeline.png
b/manual/next/_images/hop-gui/pipeline/transform-metrics-pipeline.png
index 1c15d49cac..0a44d4c6cc 100644
Binary files
a/manual/next/_images/hop-gui/pipeline/transform-metrics-pipeline.png and
b/manual/next/_images/hop-gui/pipeline/transform-metrics-pipeline.png differ
diff --git a/manual/next/pipeline/beam/beam-samples-flink.html
b/manual/next/pipeline/beam/beam-samples-flink.html
index e8f974bbc1..57360df5d8 100644
--- a/manual/next/pipeline/beam/beam-samples-flink.html
+++ b/manual/next/pipeline/beam/beam-samples-flink.html
@@ -2985,7 +2985,7 @@
<p>Check the <a href="getting-started-with-beam.html#supportedversions"
class="xref page">Supported Versions</a> on the Getting Started With Beam page
to find the latest supported Flink version for your Hop version.</p>
</div>
<div class="paragraph">
-<p>For example, for Hop 1.2, the latest currently supported version is 1.13.
Make sure to download Flink for a recent and JDK 8 compatible Scale version.
For Flink 1.3.6, this is Scala 2.11.</p>
+<p>For example, this version of Hop supports Flink 1.19: download a Flink
1.19.x release.</p>
</div>
<div class="paragraph">
<p>Download your selected Flink version and unzip to a convenient location.</p>
diff --git a/manual/next/pipeline/run-preview-debug-pipeline.html
b/manual/next/pipeline/run-preview-debug-pipeline.html
index b5973d8391..359c09044c 100644
--- a/manual/next/pipeline/run-preview-debug-pipeline.html
+++ b/manual/next/pipeline/run-preview-debug-pipeline.html
@@ -3068,26 +3068,48 @@ Hover your mouse over the red error triangle to take a
quick peek at the error m
<img src="../_images/hop-gui/pipeline/failed-pipeline.png" alt="Failed
pipeline" width="75%">
</div>
</div>
-<div class="paragraph">
+<div id="execution-results" class="paragraph">
<p>After each run the execution results are displayed in the panel on the
bottom of your window.
-The Execution Results contains two tabs:</p>
+The panel has these tabs:</p>
</div>
<div class="ulist">
<ul>
<li>
-<p>Transform Metrics</p>
+<p><strong>Logging</strong>: the log of the pipeline.</p>
+</li>
+<li>
+<p><strong>Metrics</strong>: the metrics of each transform.</p>
</li>
<li>
-<p>Logging</p>
+<p><strong>Problems</strong>: the results of the checks of the pipeline and of
the linter.</p>
+</li>
+<li>
+<p><strong>Revisions</strong>: the git history of the pipeline file, when Git
is enabled.</p>
</li>
</ul>
</div>
<div class="paragraph">
-<p>The Transform Metrics tab displays metrics per transform.</p>
+<p>The same tabs are shown for a workflow, see <a
href="../workflow/run-debug-workflow.html" class="xref page">Run and Debug a
Workflow</a>.</p>
+</div>
+<div class="sect2">
+<h3 id="_logging"><a class="link" href="#_logging">Logging</a></h3>
+<div class="paragraph">
+<p>The Logging tab displays the log of the pipeline according to the log level
chosen on execution.</p>
</div>
<div class="imageblock text-left">
<div class="content">
-<img src="../_images/hop-gui/pipeline/transform-metrics-pipeline.png"
alt="Transform Metrics pipeline" width="75%">
+<img src="../_images/hop-gui/pipeline/logging-pipeline.png" alt="Logging
pipeline" width="75%">
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_metrics"><a class="link" href="#_metrics">Metrics</a></h3>
+<div class="paragraph">
+<p>The Metrics tab displays metrics per transform.</p>
+</div>
+<div class="imageblock text-left">
+<div class="content">
+<img src="../_images/hop-gui/pipeline/transform-metrics-pipeline.png"
alt="Metrics pipeline" width="75%">
</div>
</div>
<div class="paragraph">
@@ -3184,12 +3206,31 @@ The <a
href="pipeline-run-configurations/native-local-pipeline-engine.html" clas
</tr>
</tbody>
</table>
+</div>
+<div class="sect2">
+<h3 id="_problems"><a class="link" href="#_problems">Problems</a></h3>
<div class="paragraph">
-<p>The logging tab displays the log of the pipeline according to the log level
chosen on execution.</p>
+<p>When the <a href="../linting/index.html" class="xref page">linter</a> is
installed and switched on, the Problems tab lists its findings for the file as
soon as the file has been linted: when you open it, when you save it, and
shortly after you stop editing.
+<strong>Verify this pipeline</strong> on the toolbar adds the remarks of
Hop’s own checks next to them.
+Double-click a remark to open the transform it is about.
+The toolbar of the tab can collapse and expand all remarks, and <strong>Force
refresh</strong> clears the database cache and checks the pipeline again.</p>
</div>
<div class="imageblock text-left">
<div class="content">
-<img src="../_images/hop-gui/pipeline/logging-pipeline.png" alt="Logging
pipeline" width="75%">
+<img src="../_images/hop-gui/pipeline/problems-pipeline.png" alt="Problems
pipeline" width="75%">
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_revisions"><a class="link" href="#_revisions">Revisions</a></h3>
+<div class="paragraph">
+<p>The Revisions tab lists the commits of the pipeline file, with the columns
<strong>Message</strong>, <strong>Author</strong>, <strong>Date</strong> and
<strong>Commit</strong>.
+It is shown when <strong>Enable the git plugin</strong> is on (see <a
href="../hop-gui/hop-gui-git.html#_git_configuration_options" class="xref
page">Git Configuration options</a>) and Hop has found a git repository for the
project, see <a href="../hop-gui/hop-gui-git.html" class="xref page">Working
with git</a>.
+For a file that isn’t saved yet, that is outside the git repository, or
that has no commit yet, the tab shows a message instead of the list.</p>
+</div>
+<div class="paragraph">
+<p>Select a commit and use <strong>Show text diff</strong> or <strong>Show
visual diff</strong> on the toolbar of the tab to compare that version with the
file as it is saved now; double-clicking a commit also shows the text diff.
+When the pipeline has changes that aren’t saved yet, Hop warns that the
comparison is made with the last saved version.</p>
</div>
</div>
</div>
diff --git a/manual/next/pipeline/transforms/simple-mapping.html
b/manual/next/pipeline/transforms/simple-mapping.html
index b1de2b1df6..6419e3bffa 100644
--- a/manual/next/pipeline/transforms/simple-mapping.html
+++ b/manual/next/pipeline/transforms/simple-mapping.html
@@ -3083,10 +3083,14 @@ It is always executed with a standard local Hop
pipeline run configuration since
</li>
<li>
<p>Input tab: specify which fields to pass to the <a href="mapping-input.html"
class="xref page">Mapping input</a> transform in the mapping.
-You can map (hence the name) field names.</p>
+You can map (hence the name) field names.
+Enable <strong>There is no input for this mapping.</strong> when the mapping
sub-pipeline acts as a data source and does not require a Mapping Input
transform.
+Remove any incoming hop before enabling the option.</p>
</li>
<li>
-<p>Output tab: specify how to rename output fields retrieved from the <a
href="mapping-output.html" class="xref page">Mapping output</a> transform.</p>
+<p>Output tab: specify how to rename output fields retrieved from the <a
href="mapping-output.html" class="xref page">Mapping output</a> transform.
+Enable <strong>There is no output for this mapping.</strong> when the mapping
sub-pipeline acts as a data target and does not require a Mapping Output
transform.
+Remove any outgoing hop before enabling the option.</p>
</li>
</ul>
</div>
@@ -3101,7 +3105,7 @@ You can map (hence the name) field names.</p>
<div class="ulist">
<ul>
<li>
-<p>Top-level: <code>filename</code>, <code>runConfiguration</code>,
<code>INPUT_SOURCE_TRANSFORM</code>, <code>INPUT_TARGET_TRANSFORM</code>,
<code>INPUT_DESCRIPTION</code>, <code>INPUT_MAIN_PATH</code>,
<code>INPUT_RENAME_ON_OUTPUT</code>, and the matching <code>OUTPUT_*</code>
keys, plus <code>PARAMETERS_INHERIT_ALL_VARIABLES</code></p>
+<p>Top-level: <code>filename</code>, <code>runConfiguration</code>,
<code>NO_INPUT</code>, <code>NO_OUTPUT</code>,
<code>INPUT_SOURCE_TRANSFORM</code>, <code>INPUT_TARGET_TRANSFORM</code>,
<code>INPUT_DESCRIPTION</code>, <code>INPUT_MAIN_PATH</code>,
<code>INPUT_RENAME_ON_OUTPUT</code>, and the matching <code>OUTPUT_*</code>
keys, plus <code>PARAMETERS_INHERIT_ALL_VARIABLES</code></p>
</li>
<li>
<p>Group <code>INPUT_FIELDS</code>: <code>INPUT_SOURCE_FIELD</code>,
<code>INPUT_TARGET_FIELD</code></p>
diff --git a/manual/next/workflow/actions/deletefiles.html
b/manual/next/workflow/actions/deletefiles.html
index 625b24d96a..b260d6dead 100644
--- a/manual/next/workflow/actions/deletefiles.html
+++ b/manual/next/workflow/actions/deletefiles.html
@@ -3039,7 +3039,7 @@ For example to delete all files ending in .dat, the
regular expression would be
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Result
rows</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Passed on
unchanged. With <strong>Copy previous results to args</strong>, the action
takes the path from the first field and the wildcard from the second field of
each result row, and ignores the list in the dialog, also when there are no
result rows. A row with fewer than two fields stops the action: the remaining
rows are not processed, and the action is still true.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Passed on
unchanged. With <strong>Copy previous results to args</strong>, the action
takes the path from the first field and the wildcard from the second field of
each result row, and ignores the list in the dialog, also when there are no
result rows. A row with fewer than two fields stops the action before anything
is deleted: nothing is deleted, and the action is false.</p></td>
</tr>
</tbody>
</table>
@@ -3050,7 +3050,7 @@ For example to delete all files ending in .dat, the
regular expression would be
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
-An invalid regular expression in <strong>Wildcard</strong> deletes nothing,
and the action is still true.
+An invalid regular expression in <strong>Wildcard</strong> deletes nothing,
and the action is false.
</td>
</tr>
</table>
diff --git a/manual/next/workflow/actions/evalfilesmetrics.html
b/manual/next/workflow/actions/evalfilesmetrics.html
index 58dda3eaac..8e07e96106 100644
--- a/manual/next/workflow/actions/evalfilesmetrics.html
+++ b/manual/next/workflow/actions/evalfilesmetrics.html
@@ -3195,7 +3195,7 @@
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
-With <strong>Filenames result</strong>, an invalid regular expression in
<strong>Wildcard</strong> stops the workflow with an error, and no hop is
followed.
+With <strong>Filenames result</strong>, an invalid regular expression in
<strong>Wildcard</strong> makes the action false with 1 error.
</td>
</tr>
</table>
diff --git a/manual/next/workflow/actions/movefiles.html
b/manual/next/workflow/actions/movefiles.html
index a416b6e3b9..ceb8ffb363 100644
--- a/manual/next/workflow/actions/movefiles.html
+++ b/manual/next/workflow/actions/movefiles.html
@@ -3254,7 +3254,7 @@ The default is yyyyMMdd'_'HHmmss</p>
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
-With <strong>Success when number of errors lesser than</strong>, the action
stops and is false as soon as the number of errors reaches <strong>Nr errors
lesser than</strong>, but when the last file brings it to that number, the
action is still true. With <strong>If destination file exists</strong> set to
<strong>Fail</strong>, a file that already exists counts as two errors.
+With <strong>Success when number of errors lesser than</strong>, the action
stops and is false as soon as the number of errors reaches <strong>Nr errors
lesser than</strong> (strictly fewer errors than the limit is required for
success).
</td>
</tr>
</table>
diff --git a/manual/next/workflow/actions/processresultfilenames.html
b/manual/next/workflow/actions/processresultfilenames.html
index 0a4c79ba36..7a6723df7c 100644
--- a/manual/next/workflow/actions/processresultfilenames.html
+++ b/manual/next/workflow/actions/processresultfilenames.html
@@ -3129,7 +3129,7 @@
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
-With <strong>Success when number of errors lesser than</strong>, the action is
still true when the number of errors equals <strong>Nr errors lesser
than</strong>. An invalid regular expression in <strong>Wildcard
(RegExp)</strong> or <strong>Exclude wildcard (RegExp)</strong> stops the
workflow with an error, and no hop is followed, also when <strong>Limit action
to</strong> is not selected.
+With <strong>Success when number of errors lesser than</strong>, the action is
still true when the number of errors equals <strong>Nr errors lesser
than</strong>. With <strong>Limit action to</strong> selected, an invalid
regular expression in <strong>Wildcard (RegExp)</strong> or <strong>Exclude
wildcard (RegExp)</strong> makes the action false with 1 error.
</td>
</tr>
</table>
diff --git a/manual/next/workflow/actions/waitforfile.html
b/manual/next/workflow/actions/waitforfile.html
index 762c3e7b06..c12883974b 100644
--- a/manual/next/workflow/actions/waitforfile.html
+++ b/manual/next/workflow/actions/waitforfile.html
@@ -3057,7 +3057,7 @@ This is useful in cases where a file is created in the
final place, and another
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p
class="tableblock">False</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">The
timeout is reached without the file and <strong>Success on timeout</strong> is
not selected, no file name is set, the path cannot be read (for example a
<code>zip:</code> path into a file that is not a zip), or the workflow is
stopped while waiting. The number of errors is always 0.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The
timeout is reached without the file and <strong>Success on timeout</strong> is
not selected, no file name is set, the path cannot be read (for example a
<code>zip:</code> path into a file that is not a zip), or the workflow is
stopped while waiting. When the path cannot be read, the action is false with 1
error.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Result
files</p></td>
diff --git a/manual/next/workflow/actions/xmlwellformed.html
b/manual/next/workflow/actions/xmlwellformed.html
index b37380acf0..7fd6c94da4 100644
--- a/manual/next/workflow/actions/xmlwellformed.html
+++ b/manual/next/workflow/actions/xmlwellformed.html
@@ -2998,7 +2998,7 @@
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Wildcard
(RegExp)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">A regular
expression matched against the whole path of each file in the folder, for
example <code>.*\.xml</code> (see <a href="#_result">Result</a>).</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A regular
expression matched against the file name (basename) of each file in the folder,
for example <code>.*\.xml</code> or <code>orders\.xml</code> (see <a
href="#_result">Result</a>).</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p
class="tableblock">Files/Folders</p></td>
@@ -3125,7 +3125,7 @@ You can use the Add button to add a line to the
Files/Folders list.
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
-A result row with fewer than two fields stops the workflow with an error, and
no hop is followed. The wildcard is matched against the whole path of each file
(for example <code><a href="file:///data/in/orders.xml"
class="bare">file:///data/in/orders.xml</a></code>), not its name:
<code>.*\.xml</code> matches, <code>orders\.xml</code> matches nothing, and the
action is still true.
+With <strong>Copy previous results to args</strong>, a result row with only
one field uses an empty wildcard (the whole file or folder is checked). The
wildcard is matched against the file name (basename), not the full path:
<code>orders\.xml</code> and <code>.*\.xml</code> both match
<code>orders.xml</code>.
</td>
</tr>
</table>
diff --git a/manual/next/workflow/actions/zipfile.html
b/manual/next/workflow/actions/zipfile.html
index 04b89fe4e4..507109fba1 100644
--- a/manual/next/workflow/actions/zipfile.html
+++ b/manual/next/workflow/actions/zipfile.html
@@ -3170,11 +3170,11 @@ This is what will be taken from the rows.</p>
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><p
class="tableblock">True</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">The zip
file was created or updated. It is also true when the zip exists and <strong>If
zip file exists</strong> is <strong>Do Nothing</strong>, which leaves it
unchanged, and when no file matches the wildcard with <strong>Include
sub-folders</strong> off, which creates an empty zip. With <strong>Include
sub-folders</strong> on, no match makes the action false and creates no
zip.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The zip
file was created or updated. It is also true when the zip exists and <strong>If
zip file exists</strong> is <strong>Do Nothing</strong>, which leaves it
unchanged, and when no file matches the wildcard with <strong>Include
sub-folders</strong> off, which creates an empty zip. With <strong>Include
sub-folders</strong> on, no match makes the action false and creates no zip.
With <strong>Get arguments from previous< [...]
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p
class="tableblock">False</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">The source
doesn’t exist, the zip exists and <strong>If zip file exists</strong> is
<strong>Fail</strong>, the zip can’t be written, or a source file
can’t be deleted with <strong>After zipping</strong>; the zip is already
created then. With <strong>After zipping</strong> set to <strong>Move
files</strong>, it is also false when the folder to move to doesn’t exist
and <strong>Create folder</strong [...]
+<td class="tableblock halign-left valign-top"><p class="tableblock">The source
doesn’t exist, <strong>Source directory/file</strong> is empty, the zip
exists and <strong>If zip file exists</strong> is <strong>Fail</strong>, the
zip can’t be written, or a source file can’t be deleted or moved
with <strong>After zipping</strong>; the zip is already created then. With
<strong>After zipping</strong> set to <strong>Move files</strong>, it is also
false when the folder to mov [...]
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Result
files</p></td>
@@ -3182,7 +3182,7 @@ This is what will be taken from the rows.</p>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Result
rows</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Passed on
unchanged. With <strong>Get arguments from previous</strong>, every result row
gives the source (first field), the include wildcard (second), the exclude
wildcard (third) and the zip file name (fourth). A row with an empty source or
zip file name is skipped. The first row that fails ends the action, which is
then false; the zips of the earlier rows stay, and are in the result files.
When every row is zipped, th [...]
+<td class="tableblock halign-left valign-top"><p class="tableblock">Passed on
unchanged. With <strong>Get arguments from previous</strong>, every result row
gives the source (first field), the include wildcard (second), the exclude
wildcard (third) and the zip file name (fourth). A row with an empty source or
zip file name is skipped: if at least one other row is zipped the action is
true, and if every row is skipped the action is false. The first row that fails
ends the action, which is [...]
</tr>
</tbody>
</table>
@@ -3193,7 +3193,7 @@ This is what will be taken from the rows.</p>
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
-With an empty <strong>Source directory/file</strong>, or with <strong>Get
arguments from previous</strong> and no result rows, nothing is zipped and the
result of the previous action is passed on. A source file that can’t be
moved with <strong>After zipping</strong> set to <strong>Move files</strong> is
only logged: the action is still true, and the zip is in the result files.
+With an empty <strong>Source directory/file</strong>, nothing is zipped and
the action is false. With <strong>Get arguments from previous</strong> and no
result rows, nothing is zipped and the action is false. A source file that
can’t be moved with <strong>After zipping</strong> set to <strong>Move
files</strong> makes the action false; the zip stays in the result files when
<strong>Add Zip file to result</strong> is selected.
</td>
</tr>
</table>
diff --git a/manual/next/workflow/run-debug-workflow.html
b/manual/next/workflow/run-debug-workflow.html
index c396fd34f7..f59fddb38d 100644
--- a/manual/next/workflow/run-debug-workflow.html
+++ b/manual/next/workflow/run-debug-workflow.html
@@ -3040,7 +3040,10 @@
</div>
<div class="paragraph">
<p>This workflow with our very basic pipeline should execute in less than one
second.
-You’ll now have the execution results pane which again looks very
similar to the pipeline execution results.</p>
+You’ll now have the execution results pane, with the same tabs as for a
pipeline: <strong>Logging</strong>, <strong>Metrics</strong>,
<strong>Problems</strong> and <strong>Revisions</strong>.
+On the Metrics tab a workflow shows a row for each action that ran, with among
others its <strong>Result</strong>, <strong>Reason</strong> and
<strong>Duration</strong>.
+The Problems tab lists the findings of the linter, when it is installed and
switched on, and <strong>Verify this workflow</strong> adds the remarks of
Hop’s own checks.
+See <a href="../pipeline/run-preview-debug-pipeline.html#execution-results"
class="xref page">the execution results of a pipeline</a> for the four tabs.</p>
</div>
</div>
</div>