Issues with XML handling in BMC Atrium Orchestrator Development Studio


BMC Atrium Orchestrator treats the XML type identically to a string. It places the text typed into the GUI inside of the <value> tags, which otherwise should only be an artifact used for a string and other non-XML types in order to produce an XML element. This can lead to undesirable behavior in the way that the XML is handled. For example, this issue can cause a workflow to fail.

Related topics

XML-context-item-is-handled-as-a-string
Schedule-with-XML-input-item-fails-to-work
Embedded-context-items-with-XML-fail-to-resolve-properly

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*