Difference between revisions of "Context XML Nodes"
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
== Context XML Nodes == | == Context XML Nodes == | ||
− | These Nodes allow you to save and restore the [[Presence Context]]. This is exceptionally useful if you wish to send the state of your Task to the Presence support staff for investigation, or if you want to preserve your data for later use. | + | These Nodes allow you to save and restore the [[Presence Context]]. This is exceptionally useful if you wish to send the state of your Task to the Presence support staff for investigation, or if you want to preserve your data for later use. Another more useful feature of being able to export the context is parallel processing with multiple Presence Servers. Say you had a very large dataset to number crunch, you would simply chunk the data into separate parts and invoke the processing task(s) on separate servers. |
=== Write Context To XML === | === Write Context To XML === | ||
Line 7: | Line 7: | ||
This Node saves the current Presence Context to an XML file of your choosing. | This Node saves the current Presence Context to an XML file of your choosing. | ||
− | + | [[file:write_xml_dialog.png]] | |
Enter the file location in the field provided, or alternatively specify a variable to save the context to. You can opt to store global variables, task variables, local variables and the data table. | Enter the file location in the field provided, or alternatively specify a variable to save the context to. You can opt to store global variables, task variables, local variables and the data table. | ||
Line 15: | Line 15: | ||
This Node loads the Presence Context from an XML file or from a variable. | This Node loads the Presence Context from an XML file or from a variable. | ||
− | + | [[file:read_xml_dialog.png]] | |
Again you can specify a file name for the XML or a variable name (if the context was saved to a variable). Local and task variables can either be ignored, appended to the existing variables in the context (or ignored if present) or can replace all existing variables in the Context. Global variables can be ignored (do not read) or appended as Task variables. | Again you can specify a file name for the XML or a variable name (if the context was saved to a variable). Local and task variables can either be ignored, appended to the existing variables in the context (or ignored if present) or can replace all existing variables in the Context. Global variables can be ignored (do not read) or appended as Task variables. | ||
− | |||
== See Also == | == See Also == | ||
− | |||
{{DataAccess}} | {{DataAccess}} |
Latest revision as of 13:28, 21 August 2015
Context XML Nodes
These Nodes allow you to save and restore the Presence Context. This is exceptionally useful if you wish to send the state of your Task to the Presence support staff for investigation, or if you want to preserve your data for later use. Another more useful feature of being able to export the context is parallel processing with multiple Presence Servers. Say you had a very large dataset to number crunch, you would simply chunk the data into separate parts and invoke the processing task(s) on separate servers.
Write Context To XML
This Node saves the current Presence Context to an XML file of your choosing.
Enter the file location in the field provided, or alternatively specify a variable to save the context to. You can opt to store global variables, task variables, local variables and the data table.
Read Context from XML
This Node loads the Presence Context from an XML file or from a variable.
Again you can specify a file name for the XML or a variable name (if the context was saved to a variable). Local and task variables can either be ignored, appended to the existing variables in the context (or ignored if present) or can replace all existing variables in the Context. Global variables can be ignored (do not read) or appended as Task variables.
See Also
Task Elements : Data Accesss Task Elements : Context XML Nodes