Hi Joe,
Most managers and non-technical people do not read XML.
Also, we are thinking of exporting in CSV format such things as the
result of a Search or the result of a Compare operation.
Finally, we would like to offer the possibility to export only some
properties of the objects.
Maybe an example will clear things up: a customer wanted a list of all
the notifications sent by a Remedy application, and wanted to know in
what circumstances these notifications were sent. We produced a CSV
file, with the name of the Filters, the Run If condition, and the
Notification details.
Kaïs
On 19/06/2012 16:22, Joe Martin D'Souza wrote:
**
Just curious as to why an output to a CSV would this be useful when we
can already output the definition files to XML and pretty much see all
we need to in a fairly decent ‘human readable format’?
Joe
*From:* Support <mailto:supp...@arsmarts.com>
*Sent:* Tuesday, June 19, 2012 10:17 AM
*Newsgroups:* public.remedy.arsystem.general
*To:* arslist@ARSLIST.ORG <mailto:arslist@ARSLIST.ORG>
*Subject:* Export definitions to CSV file
** Hello List,
At ARSmarts, we are currently developing an « Export definitions to
CSV » functionality. In version 2.8.1 (just released), we implemented
a basic version of this functionality that allows to export the
content of a grid to a CSV file.This is a start, but certainly not enough.
Now, here is where we can use your input: in order to build a really
useful functionality, we need to know what objects you would like to
see in the CSV file? What properties of what objects ...? In what
situations would you like to use CSV documentation? In short: what
are your needs.
Looking forward to hear from you all.
Kaïs
kais.albas...@arsmarts.com
_attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
