Page Comparison

...

If you have an external system and need to use it's 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 be try to download schema and store in "External Xml Schema Sets" to use. If schema is not accessible from network you can manually add (with basic copy and paste) XSD file content to "External Xml Schema Sets".

Scripting Namespaces

You can access data model elements as usual in process namespace even you define a namespace. For example following script will continue run as usual.

var customers = $Xml.Select('Customers/Customer');

If you need to access other namespaces you need merge prefix and element names with <prefix>:<elementname> format. For example you can access external elements with following script:

var orders = $Xml.Select('Customers/Customer//ext:Order');

Registered Namespaces

Emakin provides couple of namespaces to make easier process development. 

...

Emakin form designer recognizes this data type and proposes to use discussion control.

Scripting with Namespaces

You can access data model elements as usual in process namespace even you define a namespace. For example following script will continue run as usual.

var customers = $Xml.Select('Customers/Customer');

If you need to access other namespaces you need merge prefix and element names with <prefix>:<elementname> format. For example you can access external elements with following script:

var orders = $Xml.Select('Customers/Customer//ext:Order');