Minor formatting changes

ot4i · Jun 24, 2024 · a6d9c67 · a6d9c67
1 parent b37deca
commit a6d9c67
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/v12/en/data.json b/v12/en/data.json
@@ -253,13 +253,13 @@
                                                     "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 <span class='application'>Launch Connector Discovery</span> 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 <code>JiraPolicyProject</code> 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 <code>Jira Not connected</code> and some options will appear for available Jira objects. Expand the <code>Issues</code> twistie and select <code>Create issue</code>. 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:<br><code>Jira host and port</code><br><code>User name</code><br><code>Password (Jira Server) or API token (Jira Cloud)</code>. Click the Connect button and after waiting for a few seconds, the connection should be made and a <code>Project</code> 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 <code>Issue type</code> for the <code>Name</code> property, choose the value of <code>Task</code> 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 <code>WE WILL REPLACE THIS IN A MOMENT!</code>. 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 <code>Output message location</cod> dropdown to be <code>Context</code>. 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 <code>WE WILL REPLACE THIS IN A MOMENT!</code> 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 <code>Map inputs / TreeTransform</code> and you will see a small message hierarchy of <code>Issue > Problem > Description</code>. Click on the leaf field named <code>Description</code> 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 <span class='application'>Launch Connector Discovery</span> 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 <code>JiraPolicyProject</code> 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 <code>Jira Not connected</code> and some options will appear for available Jira objects. Expand the <code>Issues</code> twistie and select <code>Create issue</code>. 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:<br><br><code>Jira host and port</code><br><code>User name</code><br><code>Password (Jira Server) or API token (Jira Cloud)</code><br><br>Click the Connect button and after waiting for a few seconds, the connection should be made and a <code>Project</code> 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 <code>Issue type</code> for the <code>Name</code> property, choose the value of <code>Task</code> 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 <code>WE WILL REPLACE THIS IN A MOMENT!</code>. 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 <code>Output message location</code> dropdown to be <code>Context</code>. 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 <code>WE WILL REPLACE THIS IN A MOMENT!</code> 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 <code>Map inputs / TreeTransform</code> and you will see a small message hierarchy of <code>Issue > Problem > Description</code>. Click on the leaf field named <code>Description</code> 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:<br><code>CALL CopyMessageHeaders();</code><br>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)<br><code>SET OutputRoot.XMLNSC.OutputMessage.JiraId = InputRoot.JSON.Data.id;</code><br>"
+						    "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:<br><code>CALL CopyMessageHeaders();</code><br>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)<br><br><code>SET OutputRoot.XMLNSC.OutputMessage.JiraId = InputRoot.JSON.Data.id;</code><br>"
 						},
 						{
-						    "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 <code>.</code> character press Ctrl-space and using the provided drop downs, construct the expression one level at a time:<br><code>SET OutputRoot.XMLNSC.OutputMessage.JiraTaskDescription = <br>&nbsp;&nbsp;Context.&quot;node-output&quot;.&quot;TreeTransform&quot;.payload.Data.Problem.Description;<br></code>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": "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 <code>.</code> character press Ctrl-space and using the provided drop downs, construct the expression one level at a time:<br><br><code>SET OutputRoot.XMLNSC.OutputMessage.JiraTaskDescription = <br>&nbsp;&nbsp;Context.&quot;node-output&quot;.&quot;TreeTransform&quot;.payload.Data.Problem.Description;<br><br></code>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": "Drag and drop deploy the policy project which you created named <code>JiraPolicyProject</code>. In the message flow click the Flow Exerciser icon <img src='http://ot4i.github.io/ot4i.tutorials//dist/images/icons/iib/startFlowExerciser.png' alt='' /> to start testing the flow (as before, agree to the conformation question)."