...
A simple example would be to consider an XML instance that contained references to a customer and an ordered product. Both the customer element and the product element can have a child element named id. References to the id element would therefore be ambiguous; but placing them in different namespaces would remove the ambiguity.
...
If you have an external system and need to use it its data types in your model; you can add it as a new namespace and provide XML Schema Location to load. If you specified a schema location, Emakin will try to download a schema and store it in the "External Xml Schema Sets" to use. If schema is not accessible from the network, you can manually add (with basic copy and paste) XSD file content to the "External Xml Schema Sets".
...
Emakin form designer recognizes this data type proposes to use , and proposes the using of an identity picker control.
Scripting with Namespaces
You can access data model elements as usual in process namespace, even if you define defined a namespace. For example, the following script will continue to run as usual.
| Code Block | ||
|---|---|---|
| ||
var customers = $Xml.Select('Customers/Customer'); |
If you need to access the other namespaces you need merge prefix and element names with <prefix>:<elementname> format. For example you can access external elements with following script:
...