Task Flow – XML Runtime (Magic xpa 3.x)
In Runtime, Magic xpa carries out the following steps when working with an XML data source:
-
XML document reading – Loads the XML source into the view when the task opens, after the Task Prefix. Magic xpa loads the entire XML. If the task calls a subtask that is working on a different view that is related to the same XML schema as the previous view, the XML is already loaded (and is not loaded again). In this scenario, Magic xpa only has to populate the XML views.
Note that an empty XML cannot be opened with Access=R (since it is not a valid XML document).
-
Populates the records in the view based on the data fetched from the XML document.
-
The task execution continues until completion.
-
XML document updating – If changes are made to the XML views (in Step 3) and the Access=W, then Magic xpa writes (saves) a new/updated XML document to the output source (BLOB or file), when closing the task. The updated/created XML document is written once when the first task that accessed the XML document is completed.
|
Note:
|
-
For XML data sources, only non-inherited default values are considered when writing the element to the XML. Therefore, in order to send zero ('0') as a default value, you need to break the inheritance of the Default Value property.
-
A CDATA section value can be read, but when updated, the value will be escaped and not written into a CDATA section.
|
Initial Task Modes - XML
