diff --git a/v12/en/data.json b/v12/en/data.json
index 8193309..eb554ab 100644
--- a/v12/en/data.json
+++ b/v12/en/data.json
@@ -184,7 +184,7 @@
"type": "unordered",
"details": [
{
- "details": "Click the Flow Exerciser icon 
to start testing the flow (if asked, agree to the question about deploying the whole application which contains the flow)."
+ "details": "Click the Flow Exerciser icon to start testing the flow (click OK to agree to the question about deploying the owning application which contains the flow)."
},
{
"details": "Click the Send Message icon 
. Two saved messages are provided."
@@ -193,7 +193,7 @@
"details": "The input message which is named Valid XML contains this data:
<Problem>
<Description>This is a short summary description</Description>
</Problem>
This XML message matches with the XML message model which is provided in the file ModelXML.xsd inside the application TreeTransformApplication. Select this input message and click Send and the message will be sent to the HTTPInput node. You will receive the same data echoed back to you as a reply."
},
{
- "details": "The input message which is named Invalid XML contains this data:
<ThisFieldIsNotInTheSchema>
<Description>This is a short summary description</Description>
</ThisFieldIsNotInTheSchema>
This XML message does not match with the XML message model which is provided in the file ModelXML.xsd inside the application TreeTransformApplication because the root tag name is incorrect. Select this input message and click Send and the message will be sent to the HTTPInput node. You will receive a reply message telling you that validation failed. Click the button to Return the message flow to edit mode."
+ "details": "The input message which is named Invalid XML contains this data:
<ThisFieldIsNotInTheSchema>
<Description>This is a short summary description</Description>
</ThisFieldIsNotInTheSchema>
This XML message does not match with the XML message model which is provided in the file ModelXML.xsd inside the application TreeTransformApplication because the root tag name is incorrect. Select this input message and click Send and the message will be sent to the HTTPInput node. You will receive a reply message telling you that validation failed. Click the button to Return the message flow to edit mode (click OK to agree to the warning about clearing the test data)."
}
]
}
@@ -204,7 +204,7 @@
"type": "unordered",
"details": [
{
- "details": "Click the Flow Exerciser icon to start testing the flow (if asked, agree to the question about deploying the whole application which contains the flow)."
+ "details": "Click the Flow Exerciser icon to start testing the flow (agree to the confirmation about redeploying the application which will occur if you have previously deployed the application. Also agree to the question about deploying the owning application which contains the flow)."
},
{
"details": "Click the Send Message icon . Two saved messages are provided."
@@ -230,13 +230,13 @@
"details": "Take a look at the Trace message flow node. The node has been configured for you to write to an output file. By default this has been configured for writing to the location of C:\\temp\\TreeTransform\\Trace.txt on a Windows file system. If you are using a MacOS or Linux platform then you will need to change the File path accordingly. The trace node's Pattern property has been set up to record both the traditional logical tree structure which is passed in to the trace node as well as the new v13 context tree."
},
{
- "details": "Click the Flow Exerciser icon to start testing the flow (if asked, agree to the question about deploying the whole application which contains the flow)."
+ "details": "Click the Flow Exerciser icon to start testing the flow (agree to the question about deploying the owning application which contains the flow)."
},
{
"details": "Click the Send Message icon . A single saved message is provided."
},
{
- "details": "The input message which is named Input contains this XML data:
<Problem>
<Description>This is a short summary description</Description>
</Problem>
Select this input message and click Send and the message will be sent to the HTTPInput node. You will receive a reply message in XML format. Click Close on the Progress Information dialog and the path which the message took through the message flow will be displayed."
+ "details": "The input message which is named Input contains this XML data:
<Problem>
<Description>This is a short summary description</Description>
</Problem>
Select this input message and click Send and the message will be sent to the HTTPInput node. You will receive a reply message in JSON format. Click Close on the Progress Information dialog and the path which the message took through the message flow will be displayed."
},
{
"details": "Navigate to the location where the Trace node was configured to write its file output and open the trace file. You will find the trace of the logical message tree and the context tree will look like this:
==================================================
== The traditional Logical Tree structure is as follows ...
==================================================
( ['GENERICROOT' : 0x28f0ed9ddf0]
(0x01000000:Object):JSON = ( ['json' : 0x28f4e5c2fe0]
(0x01000000:Object):Data = (
(0x01000000:Object):Problem = (
(0x03000000:NameValue):Description = 'This is a short summary description' (CHARACTER)
)
)
)
)
==================================================
== The Context Tree new with v13 is as follows ...
==================================================
( ['MQROOT' : 0x28f0ed9b6f0]
(0x01000000:Name):node-output =
)
"
@@ -253,22 +253,20 @@
"details": "Drag and drop a Jira Request node on to the wire between the Trace node and the HTTP Reply node. This is a quick and easy way to wire the node in the message flow (the output wire from the Trace node will connect to the input terminal of the Jira Request, and the output terminal of the Jira Request will connect to the input terminal of the HTTP Reply). Save the message flow. From the Jira Request node Properties panel, click the Launch Connector Discovery button. "
},
{
- "details": "The Launch Connector Discovery wizard will launch. Next to the Policy Project field, click the New button to create a new Policy Project. In the Create a Policy project pop-up, type the name JiraPolicyProject and click Finish and you will be returned to the Launch Connector Discovery wizard, where the new Policy Project will now be selected. The next set of properties relating to the External directory vault will already be filled out. Click Launch Discovery and Connector Discovery will launch. Select Create issue. Select a Jira Project from the drop down. Scroll down and in the section labelled Issue type for the Name property, choose the value of Task from the enumerated drop down. The next property down is also mandatory and is named Summary. Click your cursor into this field and press Ctrl-Space. A panel with Available mappings will pop up. Expand the section labelled Map inputs / TreeTransform and you will see a small message hierarchy of Issue > Problem > Description. Click on the leaf field named Description at the bottom of this hierarchy. Scroll back up to the top of the Connector Discovery page and click the Save button and then close the Connector Discovery window and you will be returned back to the Toolkit. Save the message flow. This step has demonstrated how easy it is to map fields automatically. Note that there was no need to tell the Jira Request node about the JSON data format being passed in to the node. This happened automatically due to intelligence in the message flow based upon the JSON schemas which were provided earlier in the flow as part of the TreeTransform node."
+ "details": "The Launch Connector Discovery wizard will launch. Next to the Policy Project field, click the New button to create a new Policy Project. In the Create a Policy project pop-up, type the name JiraPolicyProject and click Finish and you will be returned to the Launch Connector Discovery wizard, where the new Policy Project will now be selected. The next set of properties relating to the External directory vault will already be filled out. Click Launch Discovery and Connector Discovery will launch. Unless you have previously connected your Toolkit to Jira (in which case you can reuse your connection properties if you wish), at this stage Jira will be shown as Not connected. Click on Jira Not connected and some options will appear for available Jira objects. Expand the Issues twistie and select Create issue. The display will change to show a Connect button, which you should click. You will now need to fill out your personal properties for accessing Jira for the following three fields:
Jira host and port
User name
Password (Jira Server) or API token (Jira Cloud). Click the Connect button and after waiting for a few seconds, the connection should be made and a Project dropdown should appear. Select a suitable Jira project from your choices. Select a Jira Project from the drop down. Scroll down and in the section labelled Issue type for the Name property, choose the value of Task from the enumerated drop down. The next property down is also mandatory and is named Summary. Click your cursor into this field and press Ctrl-Space. A panel with Available mappings will pop up. Note that at this stage you will not see anything to represent the input message which is going to drive this message flow. For now we will type a hardcoded value of WE WILL REPLACE THIS IN A MOMENT!. Scroll back to the top of the window and hit save and then close the Connector Discovery session. Back in the Toolkit view, save the message flow changes which have just been made. Return to the TreeTransform node and on its properties, change the value of the Output message location dropdown to be Context. Save the flow, return to the Jira Request node properties and once again click Launch Connector Discovery. You won't have to repeat any of the connection instructions ... simply scroll down to where you typed WE WILL REPLACE THIS IN A MOMENT! and delete this text and with your cursor in the field press Ctrl-space again. This time you will see a section of the Map inputs pop up labelled with Map inputs / TreeTransform and you will see a small message hierarchy of Issue > Problem > Description. Click on the leaf field named Description at the bottom of this hierarchy. Scroll back up to the top of the Connector Discovery page and click the Save button and then close the Connector Discovery window and you will be returned back to the Toolkit. Save the message flow. This step has demonstrated how easy it is to map fields automatically. Note that there was no need to tell the Jira Request node about the JSON data format being passed in to the node. This happened automatically due to intelligence in the message flow based upon the JSON schemas which were provided earlier in the flow as part of the TreeTransform node."
},
{
- "details": "Finally, we will add an extra node into the flow. Drag and drop a Compute node from the Transformation drawer of the palette on to the wire between the Jira Request node and the HTTP Reply node. Save the message flow. Double click the Compute node and next we will edit the ESQL which the Compute node uses. Uncomment the line:
CALL CopyMessageHeaders()
On the next line, type the following ESQL which will copy the id which is returned from Jira (which identifies the task which should be created in Jira)
SET OutputRoot.XMLNSC.OutputMessage.JiraId = InputRoot.JSON.Data.id;
"
+ "details": "Finally, we will add an extra node into the flow. Drag and drop a Compute node from the Transformation drawer of the palette on to the wire between the Jira Request node and the HTTP Reply node. Save the message flow. Double click the Compute node and next we will edit the ESQL which the Compute node uses. Uncomment the line:
CALL CopyMessageHeaders();
On the next line, type the following ESQL which will copy the id which is returned from Jira (which identifies the task which should be created in Jira)
SET OutputRoot.XMLNSC.OutputMessage.JiraId = InputRoot.JSON.Data.id;
"
},
{
"details": "Next we will type the following line of ESQL which takes the same description field which was sent to the Jira Request node and also copy it into the output message at the end of the flow. In order to have the opportunity to experience the new v13 ESQL Content Assist feature, as you type the right hand side of this expression, after each . character press Ctrl-space and using the provided drop downs, construct the expression one level at a time:
SET OutputRoot.XMLNSC.OutputMessage.JiraTaskDescription =
Context."node-output"."TreeTransform".payload.Data.Problem.Description;
Save the ESQL file, and return to the message flow diagram where we will use the Flow Exerciser to send data through the message flow."
},
{
- "details": "Click the Flow Exerciser icon to start testing the flow (if asked, agree to the question about deploying the whole application which contains the flow). Agree to also deploy the policy project."
+ "details": "Drag and drop deploy the policy project which you created named JiraPolicyProject. In the message flow click the Flow Exerciser icon to start testing the flow (as before, agree to the conformation question)."
},
+
{
- "details": "Click the Send Message icon . Use the same structure of input message which we used for the previous test. If you would like you can change the text of the message before clicking send."
- },
- {
- "details": "The input message which is named Input contains this XML data:
<Problem>
<Description>This is a short summary description</Description>
</Problem>
Select this input message and click the Send Message icon and the message will be sent to the HTTPInput node. You should receive a reply message in XML format which looks like this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<OutputMessage>
<JiraId>10009</JiraId>
<JiraTaskDescription>This is a short summary description</JiraTaskDescription>
</OutputMessage>
Click Close on the Progress Information dialog and the path which the message took through the message flow will be displayed."
+ "details": "The input message which is named Input contains this XML data:
<Problem>
<Description>This is a short summary description</Description>
</Problem>
Select this input message and click the Send Message icon and the message will be sent to the HTTPInput node. You should receive a reply message in XML format which looks like this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<OutputMessage>
<JiraId>10009</JiraId>
<JiraTaskDescription>This is a short summary description</JiraTaskDescription>
</OutputMessage>
Click Close on the Progress Information dialog and the path which the message took through the message flow will be displayed. If you log in to your Jira system you should also see that the task has been created successfully."
}
]
}