Transformation Filename

[patrick]

Hi,

if I configure the transformation to not ask for a filename but use an filename like ${cfn}-xsl.xml, an existing file with this name will be overwritten.

There should be an option to prevent that an exising file gets automatically overwritten. Either a popup could appear that asks If the user want to overwrite the existing file or the filename could be extended by (0)...(n), e.g.

Thanks,
Patrick

[adrian]

Hello,

I've logged a request on our issue tracking tool to show a confirmation dialog before overwriting an existing file. This will be analyzed and if found appropriate it will be implemented in a future version of Oxygen.

Regarding the unique output filename. You could use:

1. The ${timeStamp} editor variable: ${cfn}-xsl${timeStamp}.xml
This expands to the current date and time down to the millisecond.
e.g.
personal-xsl20111118103056992.xml
The downside is that the filename is too long and somewhat difficult to read.

2. The ${uuid} editor variable: ${cfn}-xsl${uuid}.xml
This expands to an universally unique identifier(UUID).
e.g.
personal-xsl317d5b2f-4589-4105-b1f1-b8558f14bbc3.xml
This is even messier that the timestamp, even less readable, so I'm not sure if it helps.

3. The ${id} editor variable: ${cfn}-xsl${id}.xml
Generates an application-level unique identifier.
e.g.
personal-xsldp4_1sj_32.xml
Somewhat shorter but not very readable.

4. The ${date(pattern)} editor variable: ${cfn}-xsl${date(yyyy-MM-dd HH-mm-ss)}.xml
Expands to the current date and time using the specified pattern. The pattern is of Java flavor, as documented here:
http://download.oracle.com/javase/1.4.2 ... ormat.html
e.g.
personal-xsl2011-11-18 11-06-40.xml
This is the most useful of the four because you can customize it.

Regards,
Adrian