Kais, Off the top of my head maybe the form information, such as indexes, fields in results list and the fields itself (Label, DB Name, data type, entry mode, input length and where an enum the actual enum options). It comes in useful when you have a seperate team doing reporting and need to provide a data dictionary of some sort.
Regards, Saby ________________________________ From: Joe Martin D'Souza <[email protected]> To: [email protected] Sent: Tuesday, June 19, 2012 10:48 AM Subject: Re: Export definitions to CSV file ** Kais, Got you.. I should have guessed you were aiming it at management. But since meta data reports are generally more useful to developers, I was wondering what value it would serve a developer who may already be capable of reading XML. In reference to the new version, assuming that I was management incapable of reading XML, I might have found a report of overlaid objects compared with its original useful to see what may have been changed on a excel sheet.. This actually would be useful to a developer too as once an object has been overlaid and changes have been made, even a developer looses visibility of the original object – unless he deletes the overlay... This is my most spontaneous thought that came to mind given your explanation on grounds you wish to cover... Cheers Joe From: Support Sent: Tuesday, June 19, 2012 10:41 AM Newsgroups: public.remedy.arsystem.general To: [email protected] Subject: Re: Export definitions to CSV file ** 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 >Sent: Tuesday, June 19, 2012 10:17 AM >Newsgroups: public.remedy.arsystem.general >To: [email protected] >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 >[email protected]_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"
