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 77b58f5bcf Website updated to ce72275
77b58f5bcf is described below

commit 77b58f5bcf91db64cd9b04a555a2c36c180491aa
Author: jenkins <[email protected]>
AuthorDate: Tue Nov 17 10:37:22 2026 +0000

    Website updated to ce72275
---
 dev-manual/next/sdk/workflows.html                 |   6 +-
 manual/next/pipeline/transforms/joinrows.html      |  13 +++
 manual/next/pipeline/transforms/rownormaliser.html | 114 ++++++++++++++++++++-
 manual/next/pipeline/transforms/sortedmerge.html   |   3 +
 manual/next/workflow/actions/eval.html             |   2 +-
 5 files changed, 132 insertions(+), 6 deletions(-)

diff --git a/dev-manual/next/sdk/workflows.html 
b/dev-manual/next/sdk/workflows.html
index c34377afb9..1be2a06696 100644
--- a/dev-manual/next/sdk/workflows.html
+++ b/dev-manual/next/sdk/workflows.html
@@ -736,7 +736,7 @@ workflowMeta.addWorkflowHop(hop);</code></pre>
 </div>
 </li>
 <li>
-<p><strong>On Success (Conditional)</strong>: Action B executes only if Action 
A returned a successful result (<code>result.getResult() == true</code>):</p>
+<p><strong>On Success (Conditional)</strong>: Action B executes only if Action 
A returned a successful result (<code>result.isResult() == true</code>):</p>
 <div class="listingblock">
 <div class="content">
 <div class="code-lang" data-pagefind-ignore>java</div><pre class="highlightjs 
highlight is-highlighted"><code class="language-java hljs" 
data-lang="java">hop.setUnconditional(<span class="hljs-literal">false</span>);
@@ -745,7 +745,7 @@ hop.setEvaluation(<span 
class="hljs-literal">true</span>);</code></pre>
 </div>
 </li>
 <li>
-<p><strong>On Failure (Conditional)</strong>: Action B executes only if Action 
A failed (<code>result.getResult() == false</code>):</p>
+<p><strong>On Failure (Conditional)</strong>: Action B executes only if Action 
A failed (<code>result.isResult() == false</code>):</p>
 <div class="listingblock">
 <div class="content">
 <div class="code-lang" data-pagefind-ignore>java</div><pre class="highlightjs 
highlight is-highlighted"><code class="language-java hljs" 
data-lang="java">hop.setUnconditional(<span class="hljs-literal">false</span>);
@@ -789,7 +789,7 @@ Like pipeline engines, workflow engines are created via the 
<code>WorkflowEngine
 <span class="hljs-type">Result</span> <span 
class="hljs-variable">result</span> <span class="hljs-operator">=</span> 
workflowEngine.startExecution();
 
 <span class="hljs-comment">// Inspect outcome</span>
-<span class="hljs-keyword">if</span> (result.getResult() &amp;&amp; 
result.getNrErrors() == <span class="hljs-number">0</span>) {
+<span class="hljs-keyword">if</span> (result.isResult() &amp;&amp; 
result.getNrErrors() == <span class="hljs-number">0</span>) {
   System.out.println(<span class="hljs-string">&quot;Workflow 
succeeded!&quot;</span>);
 } <span class="hljs-keyword">else</span> {
   System.err.println(<span class="hljs-string">&quot;Workflow failed with 
&quot;</span> + result.getNrErrors() + <span class="hljs-string">&quot; 
errors.&quot;</span>);
diff --git a/manual/next/pipeline/transforms/joinrows.html 
b/manual/next/pipeline/transforms/joinrows.html
index 98cca7860a..39552f12e2 100644
--- a/manual/next/pipeline/transforms/joinrows.html
+++ b/manual/next/pipeline/transforms/joinrows.html
@@ -3115,6 +3115,19 @@ See <a 
href="../beam/getting-started-with-beam.html#_unsupported_transforms" cla
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
+With several copies of this transform, set the transforms of the other streams 
to Copy rows.
+Otherwise each copy only receives a part of those streams and combinations go 
missing.
+</td>
+</tr>
+</table>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
 The transform gives the same result on the <a 
href="../pipeline-run-configurations/single-threaded-pipeline-engine.html" 
class="xref page">single threaded engine</a> as on the Hop engine.
 That engine runs the previous transforms first, so all the rows of the other 
streams are there when Join Rows starts.
 </td>
diff --git a/manual/next/pipeline/transforms/rownormaliser.html 
b/manual/next/pipeline/transforms/rownormaliser.html
index 0b02d6c1da..6ef9f73d8e 100644
--- a/manual/next/pipeline/transforms/rownormaliser.html
+++ b/manual/next/pipeline/transforms/rownormaliser.html
@@ -3082,10 +3082,16 @@
 <h2 id="_normalising_every_input_field"><a class="link" 
href="#_normalising_every_input_field">Normalising every input field</a></h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>When the <strong>Fields table</strong> is empty, the transform normalises 
every field it receives. Each input field is a type of its own, named after the 
field, and its value goes into the <strong>Value field</strong>. This works 
when the input fields are only known when the pipeline runs, for example in a 
pipeline that profiles any file or table it is given.</p>
+<p>When the <strong>Fields table</strong> is empty, the transform normalises 
every field it receives, except the <strong>Key fields</strong>. Each input 
field is a type of its own, named after the field, and its value goes into the 
<strong>Value field</strong>. This works when the input fields are only known 
when the pipeline runs, for example in a pipeline that profiles any file or 
table it is given.</p>
 </div>
 <div class="paragraph">
-<p>Every input field is normalised this way, so no field is passed on 
unchanged: the output has only the type field and the value field. When the 
input fields have different data types the value field is a String, as 
described below. The value field keeps a length or precision only when all 
input fields have the same one. While you design a pipeline whose input fields 
are not known yet, the transform shows the value field to the transforms after 
it as a String.</p>
+<p>The key fields are passed on unchanged on every row, in the order they have 
in the input. Without key fields the output has only the type field and the 
value field. When the normalised fields have different data types the value 
field is a String, as described below. The value field keeps a length or 
precision only when all normalised fields have the same one. While you design a 
pipeline whose input fields are not known yet, the transform shows the value 
field to the transforms after i [...]
+</div>
+<div class="paragraph">
+<p>This is what the <code>Crosstable</code> prefix does in a Qlik Sense load 
script, with the key fields as its qualifier fields.</p>
+</div>
+<div class="paragraph">
+<p>The key fields are only used when the <strong>Fields table</strong> is 
empty. With listed fields, every field that is not listed is passed on 
unchanged anyway; <strong>Verify</strong> warns when key fields are set but not 
used.</p>
 </div>
 </div>
 </div>
@@ -3150,6 +3156,10 @@ Before Hop 2.20, a new field took the data type of the 
first input field filling
 <td class="tableblock halign-left valign-top"><p class="tableblock">The name 
of the field that holds the values when the <strong>Fields table</strong> is 
empty and every input field is normalised. The default is 
<strong>value</strong>. Give it a name other than the type field&#8217;s: 
otherwise it is renamed in the output, to <strong>value_1</strong> for 
example.</p></td>
 </tr>
 <tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Key 
fields</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The fields 
that are passed on unchanged on every row when the <strong>Fields 
table</strong> is empty. Every other input field is normalised. The names can 
contain variables.</p></td>
+</tr>
+<tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Fields 
table</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">A list of 
the fields you want to normalize. Leave it empty to normalise every input field 
into the <strong>Value field</strong>. You must set the following properties 
for each listed field:</p>
 <p class="tableblock">* Fieldname: Name of the fields to normalize, as you get 
them from the input transform.
@@ -3446,6 +3456,106 @@ Before Hop 2.20, a new field took the data type of the 
first input field filling
 </tbody>
 </table>
 </div>
+<div class="sect2">
+<h3 id="_normalized_data_example_4"><a class="link" 
href="#_normalized_data_example_4">Normalized data (example 4)</a></h3>
+<div class="paragraph">
+<p>Months as columns, kept per region and year. With this input:</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 20%;">
+<col style="width: 20%;">
+<col style="width: 20%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Region</th>
+<th class="tableblock halign-left valign-top">Year</th>
+<th class="tableblock halign-left valign-top">Jan</th>
+<th class="tableblock halign-left valign-top">Feb</th>
+<th class="tableblock halign-left valign-top">Mar</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">North</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">2026</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">10</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">20</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">30</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">South</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">2026</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">15</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">25</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">35</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>set <strong>Typefield</strong> = "Month", <strong>Value field</strong> = 
"Sales", <strong>Key fields</strong> = "Region" and "Year", and leave the 
<strong>Fields table</strong> empty. The result is:</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<colgroup>
+<col style="width: 25%;">
+<col style="width: 25%;">
+<col style="width: 25%;">
+<col style="width: 25%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Region</th>
+<th class="tableblock halign-left valign-top">Year</th>
+<th class="tableblock halign-left valign-top">Month</th>
+<th class="tableblock halign-left valign-top">Sales</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">North</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">2026</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">Jan</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">10</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">North</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">2026</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">Feb</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">20</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">North</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">2026</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">Mar</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">30</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">South</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">2026</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">Jan</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">15</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">South</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">2026</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">Feb</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">25</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">South</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">2026</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">Mar</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">35</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>A column added to the input, <code>Apr</code> for example, is normalised as 
well without changing the transform.</p>
+</div>
+</div>
 </div>
 </div>
     </article>
diff --git a/manual/next/pipeline/transforms/sortedmerge.html 
b/manual/next/pipeline/transforms/sortedmerge.html
index e69e1c434e..66e88bbcf7 100644
--- a/manual/next/pipeline/transforms/sortedmerge.html
+++ b/manual/next/pipeline/transforms/sortedmerge.html
@@ -3067,6 +3067,9 @@
 <div class="paragraph">
 <p>The Sorted Merge transform merges rows coming from multiple input 
transforms providing these rows are sorted themselves on the given key 
fields.</p>
 </div>
+<div class="paragraph">
+<p>Every input must be sorted on the key fields in the direction set for each 
field in the Fields table. The transform merges in that direction, even when a 
transform before it sorted the rows the other way. When a row of an input sorts 
before the previous row of the same input, the transform stops with an error 
naming the input and the two rows, rather than merging the rows in the wrong 
place. Verify pipeline warns when a previous transform, such as Sort rows, 
sorts a key field descendi [...]
+</div>
 </div>
 </div>
 <div class="sect1">
diff --git a/manual/next/workflow/actions/eval.html 
b/manual/next/workflow/actions/eval.html
index 586a468228..493bd5366c 100644
--- a/manual/next/workflow/actions/eval.html
+++ b/manual/next/workflow/actions/eval.html
@@ -3228,7 +3228,7 @@ In other words, it needs to end with a boolean 
expression.</p>
 </thead>
 <tbody>
 <tr>
-<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code><code>previous_result.getResult()</code></code></p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code><code>previous_result.isResult()</code></code></p></td>
 <td class="tableblock halign-left valign-top"></td>
 <td class="tableblock halign-left valign-top"><p 
class="tableblock">boolean</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">true if 
the previous workflow action was executed successfully, false if there was some 
error.</p></td>

Reply via email to