renamed duplicate ids. the pdf will now build.
This commit is contained in:
@@ -219,7 +219,7 @@
|
||||
<set name="flowScope.selectedHotel" value="null" />
|
||||
</programlisting>
|
||||
</sect3>
|
||||
<sect3 id="set-element-null">
|
||||
<sect3 id="set-element-literal">
|
||||
<title>Assigning a literal value</title>
|
||||
<para>
|
||||
Enclose a value within tick marks to assign a literal:
|
||||
@@ -228,7 +228,7 @@
|
||||
<set name="flowScope.status" value="'Processing Order'" />
|
||||
</programlisting>
|
||||
</sect3>
|
||||
<sect3 id="evaluate-element-result-type">
|
||||
<sect3 id="set-element-result-type">
|
||||
<title>Converting a value prior to variable assignment</title>
|
||||
<para>
|
||||
Use the <literal>type</literal> attribute to specify a desired value type:
|
||||
@@ -451,7 +451,7 @@ public interface FlowOutcome {
|
||||
</subfow-state>
|
||||
</programlisting>
|
||||
</sect3>
|
||||
<sect3 id="subflow-state-element-input">
|
||||
<sect3 id="subflow-state-element-output">
|
||||
<title>Mapping subflow output</title>
|
||||
<para>
|
||||
Simply refer to a subflow output attribute by its name within a outcome transition:
|
||||
@@ -466,7 +466,7 @@ public interface FlowOutcome {
|
||||
</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
<sect2 id="checkpoint-input-output">
|
||||
<sect2 id="checkpoint-subflow">
|
||||
<title>Checkpoint: calling subflows</title>
|
||||
<para>
|
||||
Now review the sample booking flow calling a subflow:
|
||||
|
||||
Reference in New Issue
Block a user