Difference between revisions of "Data Table"

From PresenceWiki
Jump to: navigation, search
 
(One intermediate revision by one other user not shown)
Line 3: Line 3:
 
The Data Table is an object stored in memory as part of the [[Presence Context]]. It consists of a series of rows divided into named columns:
 
The Data Table is an object stored in memory as part of the [[Presence Context]]. It consists of a series of rows divided into named columns:
  
http://www.international-presence.com/wikidocs/images/data_table_view.png
+
[[file:data_table_view.png]]
  
 
=== Populating the Data Table ===
 
=== Populating the Data Table ===
Line 13: Line 13:
 
You can dynamically make references to data columns with the following syntax:
 
You can dynamically make references to data columns with the following syntax:
  
: ''':var{COLUMN_NAME}'''
+
<pre>:var{COLUMN_NAME}</pre>
  
 
This will automatically replace the token above with the value of the column '''COLUMN_NAME''' in the current row of the Data Table. Where multiple rows of Data are present this may cause whatever Task Element references the column to be repeated for each row, if this is appropriate (see iteration below).
 
This will automatically replace the token above with the value of the column '''COLUMN_NAME''' in the current row of the Data Table. Where multiple rows of Data are present this may cause whatever Task Element references the column to be repeated for each row, if this is appropriate (see iteration below).
Line 45: Line 45:
 
We would reference this Column by placing the following value in the Email Subject field:
 
We would reference this Column by placing the following value in the Email Subject field:
  
: :var{EMAIL_SUBJECT}
+
<pre>:var{EMAIL_SUBJECT}</pre>
  
 
As a result of this a separate email with a unique subject will be generated for each value of EMAIL_SUBJECT in the Data Table.
 
As a result of this a separate email with a unique subject will be generated for each value of EMAIL_SUBJECT in the Data Table.
Line 51: Line 51:
 
Note that where the Task Element can only produce one result - for example in a [[Set Variable]] Node - Presence will not bother to iterate over values. So the following pseudo instruction:
 
Note that where the Task Element can only produce one result - for example in a [[Set Variable]] Node - Presence will not bother to iterate over values. So the following pseudo instruction:
  
SET ${surname} = :var{SURNAME}
+
SET <pre>${surname}</pre> = <pre>:var{SURNAME}</pre>
  
 
Will only pick up the FIRST value of SURNAME from the data table, since it would be pointless to use any others (there can only be one value for ${surname} ).
 
Will only pick up the FIRST value of SURNAME from the data table, since it would be pointless to use any others (there can only be one value for ${surname} ).

Latest revision as of 06:40, 20 August 2015

Data Table

The Data Table is an object stored in memory as part of the Presence Context. It consists of a series of rows divided into named columns:

Data table view.png

Populating the Data Table

The Data Table is automatically populated and appended by Query Task Elements. For example the SQL Query Node will populate the Data Table with the results of the database query, using the Column names and values that are returned in the record set.

Referencing the Data Table

You can dynamically make references to data columns with the following syntax:

:var{COLUMN_NAME}

This will automatically replace the token above with the value of the column COLUMN_NAME in the current row of the Data Table. Where multiple rows of Data are present this may cause whatever Task Element references the column to be repeated for each row, if this is appropriate (see iteration below).

Viewing the Data Table

While a Task is being debugged you can view the contents of the Data Table on the left hand panel, which presents a tree structure of the Data organised by row then column.

Merging Data Tables

The Merge Results Node will merge one ore more Data Tables with either horizontal, vertical or cross-reference strategy.

Joining New Results

If a Data Table is already present in the Presence Context and a new query is performed, the results will be appended to the existing Data Table. If the results of the current (incoming) Data Table are referenced in the new query, the new results will be joined in a logical fashion. For example:

Query A creates a Data Table with the columns 'A', 'B' and 'C'.

This joins to Query B, which returns a Data Table with the columns 'D' and 'E'.

If Query B contains a reference to Column 'A' (for example in the WHERE clause), the query will be repeated for each possible value of 'A' and the subset will be joined to the correct records.

Iteration Strategies

Implicit Iteration

Presence tends to use implicit iteration. This means that if a Task Element's settings contain a reference to one or more column names, the Task Element's functionality will be repeated for each unique value for the column(s) referenced.

For example, the Send Email node allows you to use a Column reference to form the subject (as well as the message body, attachments and recipients). Imagine we have a Data Table which contains a Column named 'EMAIL_SUBJECT' and has five rows of data, each with a distinct value for EMAIL_SUBJECT.

We would reference this Column by placing the following value in the Email Subject field:

:var{EMAIL_SUBJECT}

As a result of this a separate email with a unique subject will be generated for each value of EMAIL_SUBJECT in the Data Table.

Note that where the Task Element can only produce one result - for example in a Set Variable Node - Presence will not bother to iterate over values. So the following pseudo instruction:

SET
${surname}
=
:var{SURNAME}

Will only pick up the FIRST value of SURNAME from the data table, since it would be pointless to use any others (there can only be one value for ${surname} ).

Explicit Iteration

Sometimes it can be useful to explicitly iterate over the Data Table. To achieve this you can use the Dataset Splitter, which breaks the Data Table up based on differences in a column value and calls the next Node in the Task repeatedly for each subset of data.

Storing and Retrieving the Data Table

Two options are available for storing and retrieving the Data Table:

  • Saving it to file and reloading it
  • Saving it to a Variable and reloading it

To store the Data Table to a file, use the Write Context to XML Node. This will store the Data Table along with any local, task or global variables in existence. You can then read it back again (in the same Task, or in a separate Task, or on a separate environment) using the Read Context from XML Node.

To temporarily store a Data Table in memory (for later retrieval) use the Store Data Table and Retrieve Data Table Nodes. These store the Data Table in a Presence variable.

Manipulating the Data Table

Presence provides the following Nodes to manipulate the contents of the Data Table: