The customer runs a JOBF from Windows to Linux. The source file name contains german Umlauts but the resulting file name on Linux unfortunately special characters instead.
I did some tests and reproduce the issue.
1) JOBF performs an incorrect conversation of Umlauts
2) JOBS (doing an "echo > blablaÜÖÄ.txt) also performs an incorrect conversation
3) only a JOBS.FTP (protocol SFTP) creates a correct file name
in general: Linux uses UTF-8 codeset, Windows is different (usually MSWIN8859...)
-> is seems that JOBF doesn't recognize the UTF-8 code set on Linux.
Note: this issue is not about the file content but the file name
Release : 12.3
Component : AUTOMATION ENGINE
The observed behaviour is correct, as stated in the expectations:
Expected behavior: The Linux file should be created with the same name
The filename is indeed created with the same name as the source, but since the source does use Windows-1252 and the target uses UTF-8, the presentation is different (single-byte vs- 2 byte conversions). Since our agents are not Unicode-aware, we do recommend not using umlauts in filenames.
We will enhance our documentation to reflect this more clearly.