Is there standard functionality that allows you to create an xml file of selected data?
I have a function that returns an xml variable.
This variable contains all the text that I need.
Is there an easy way to put that in an xml file and give it back to the user so that he/he can store it locally??
Best answer by Mark Jongeling
Hey,
If you can capture the XML data in a variable, you can also use that data in a Download file process action. This will prompt the user to download the XML data as a file with a name of your/their choice. This is similar to how the Export model task works in the Software Factory.
That particular process flow part looks like this:
Start task, output of that is in my case the JSON data. The data is given to the Download file, which will prompt the user to Download the file
If you can capture the XML data in a variable, you can also use that data in a Download file process action. This will prompt the user to download the XML data as a file with a name of your/their choice. This is similar to how the Export model task works in the Software Factory.
That particular process flow part looks like this:
Start task, output of that is in my case the JSON data. The data is given to the Download file, which will prompt the user to Download the file
Creating a varbinary variable, and passing that to the download functionality worked very well.
The only thing I need to tackle is that the browser (chrome) likes to open the file content directly into the browser window. (which actually is not desired for this)
However, I think that has to do with the browser itself since if I change the extension, the browser provides me with a download popup form.
In the Download file process action, you can specify whether Universal should force the download of the file rather than previewing it.
However, as of now the parameter is not supported. But you can already set it up. In an upcoming version of the Universal GUI, the setting will be respected and the file will be a download: 2025.1 | Thinkwise Documentation
Even though this seems like a Universal GUI feature, the implementation is actually fully in Indicium. The input parameter that was introduced in 2025.1 will work as intended as of the next Indicium release, 2025.1.13.0. The release would normally be May 5th, but since this is a public holiday, the release will most likely be May 6th.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.