All nodes now return a value - including the JavaScript, decision tables and adaptors - the value can be used in conditional tests immediately without the need to have an interim GET node:
The result value is shown in the testing console:
If the result is a JavaScript object then it will be shown as an expandable Object:
Errors from nodes are returned into a static piece of the schema called the Metadata. The Metadata includes the error message, as reported in the testing console, the name of the node the time and the state of the schema and public variables when the error occured.
{
"Error": {
"Message": "",
"Node": {
"Name": "",
"Type": ""
},
"Time": "",
"TransactionState": {
"PublicVariables": "",
"Schema": ""
}
}
} |
This allows the message to be tested in a graph like any other schema or public variable value. For example the graph below catches a HTTP 400 error message and returns true and returns error for other non-200 HTTP error codes.
The testing console shows the full error message and this is also held in the Metadata part of the schema.
The Metadata is shown in the console under the Expand All button. The Display JSON button shows all of the schema minus the Metadata.
You can now reference the entire schema in listeners (where the output is written to), nodes as arguments and connections (write the entire schema out).
When creating a new graph form a custom graph template in the Create New Item screen a tool tip displays the contents of the custom graph template. This shows the graphs, scripts, nodes and adaptors in graph template.
When creating a new item from a graph template, any existing graphs, nodes, adaptors and schema will not be duplicated. A screen will identify any potential duplicates and if the continue button is shown then it is okay to proceed without creating duplicates. If however there is a node, graph or adaptor that exists with the same name, but not the same type, then the Continue button will not be available. The node that exists with the same name should be renamed before trying to use the graph template successfully.
A new node type that allows integration to Acquia Lift. The node allows integration to the Content, Capture and Decide Acquia Lift function on the Lift Decision endpoint.
The Adaptor Action dropdown has Content (GET method), Capture (POST menthod) and Decide (POST method). Further details on each of the actions can be found in the Acquia Lift API documentation.
A new addiition for Kitewheel OEM partners is the capability to customize a large majority of the Kitewheel interface using a Cascading Style Sheet (CSS) / LESS extension. This is appended to the standard Kitewheel stylesheet.
Also available to OEM partners is the ability to create child and grand-child organizations. Previously this was only available to the Kitewheel organization.
Our Partners on the Hub now have the ability to create child organizations/ sub organizations. This option is available on the Admin screen to all Hub Owners in the Parent Organization.
With these Child Organizations in place, Owner users can also move a project to a different organization. The interface will prompt the user to confirm the move. If there are any deployed graphs in the Project, they will have to be stopped before moving the Project to another Organization.
