WORKABLES tab

You have the following example workflow with the following parameters:

You run the following XML file through the workflow:

<?xml version="1.0" encoding="UTF-8"?>
<root>
   <entries>
      <element jobid="12345">
    	 <id>12345</id>
         <company>Hybrid Software</company>
         <address1>Guldensporenpark 18 block B</address1>
         <address2>--</address2>
         <zip>9820</zip>
         <city>Merelbeke</city>
         <country>Belgium</country>
         <phone>+32 9 329 57 53</phone>
         <email>info-eur@hybridsoftware.com</email>
         <description>PACKZ Green Tea Lemon</description>
         <asm>Jack Sparrow</asm>
      </element>
   </entries>
   <tablename>main</tablename>
</root>

• If you select the Start From Kiosk node, you see an example of a reference output type:

  [
  {
  pass: 1,
  references: {
  files: [
  "cloudflow://PP_FILE_STORE/12345.xml"
  ]
  }
  }
  ]

• If you select the Set name node, you see an example of a variables output type:

  [
  {
  pass: 1,
  variables: {
  name: "MC"
  }
  }
  ]

• If you select the XML to JSON node, you see an example of a data output type:

  [
  {
  pass: 1,
  data: [
  {
  type: "com.nixps.quantum.data_provider.0",
  url: "cfqworkdata:///4c7aa1d5-545e-4d47-92c9-309e49cdb3f4/"
  }
  ]
  }
  ]

The resolved output is calculated but it is not stored in the workable. It is accessible for File from node and Data in Container from previous. You can also define the node name in stead of previous, but it will use what is available as resolved output from that node. This means that references and data are kept when a node does not generate either files or data. In the example above, the output and resolved output from the Start from Kiosk node will always be the same, as this node is the first one. If you select the Set name node, the resolved output looks like this:

[
{
references: {
files: [
"cloudflow://PP_FILE_STORE/12345.xml"
]
}
,
pass: 1,
variables: {
name: "MC"
}
}
]

This node didn't generate any references, however they are still available, so resolved means what is available at that time. It will also combine the output with the output which the node created, this is the variable name. This is rather redundant as variables are always direct accessible. The XML to JSON node will use that reference, as the XML Data is set to use the full file URL from the previous node. The XML to JSON node only generates data, but the resolved output shows this:

[
{
references: {
files: [
"cloudflow://PP_FILE_STORE/12345.xml"
]
}
,
data: [
{
type: "com.nixps.quantum.data_provider.0",
url: "cfqworkdata:///4c7aa1d5-545e-4d47-92c9-309e49cdb3f4/"
}
]
,
pass: 1
}
]

The reference doesn't change as no new reference is generated. However, the resolved output and the content of the data in the container are shown:

[
{
url: "cfqworkdata:///4c7aa1d5-545e-4d47-92c9-309e49cdb3f4/",
data: {
entries: {
element: {
jobid: 12345,
id: "12345",
company: "Hybrid Software",
address1: "Guldensporenpark 18 block B",
address2: "--",
zip: "9820",
city: "Merelbeke",
country: "Belgium",
phone: "+32 9 329 57 53",
email: "info-eur@hybridsoftware.com",
description: "PACKZ Green Tea Lemon",
asm: "Jack Sparrow"
}
}
,
tablename: "main"
}
}
]