still some example or explanation will be very helpful.For all of us!
My assumption was that the URL should return XML in the same form as the default string supplied in the property XML string of the select widget.
As I use eXist-db which provides a handy REST webservice, I provided a URL complete with an XQUERY to generate the XML
| Code: : |
http://demo.exist-db.org/exist/rest/db/shakespeare?_query=%3Cdata%3E{for%20$V%20in%20/PLAY/TITLE%20return%20%3Crecord%20jsxid=%22{data($V)}%22%20jsxtext=%22{data($V)}%22/%3E}%3C/data%3E
|
This also runs on the default distribution of exist-db from exist.org to give a list of 3 play titles
| Code: : |
<exist:result xmlns:exist="http://exist.sourceforge.net/NS/exist" exist:hits="1" exist:start="1" exist:count="1">
<data>
<record jsxid="The Tragedy of Macbeth" jsxtext="The Tragedy of Macbeth"/>
<record jsxid="The Tragedy of Romeo and Juliet" jsxtext="The Tragedy of Romeo and Juliet"/>
<record jsxid="The Tragedy of Hamlet, Prince of Denmark" jsxtext="The Tragedy of Hamlet, Prince of Denmark"/>
</data>
</exist:result>
|
If you supply a url like this to the XML URL property of the select widget you will see the result displayed as the select options in the Intalioi|AJAX form design window. The outer exist:result seems to be accepted happily.
Getting this to work in real life requires getting around the javascript restrictions so I think you will need to set up proxy'ing from the tomcat webserver or running the webserver at the same location as the intalio BPMS
My assumtion was that you could also supply an XML file of the same form within the XML Documents folder of Intalio|AJAX. This also works in designer to produce an appropriate select list but does not appear to deploy the file to the BPMS server for you.