I'm having some trouble with the WorkspaceRunner transformer in FME 2018 windows 32 bit.
Say Workspace B contains a FeatureReader transformer. In Workspace B, create a published parameter called FileList with a filename (Multiple) and set this as the dataset field in the FeatureReader to read txt files. Set the value of FileList to C:\\temp\\a.txt,C:\\temp\\b.txt. I have no errors running workspace B as is.
Using FME 2018, I trigger workspace B using a WorkspaceRunner in Workspace A, I get an error which highlights the paths in the Filename (Multiple) parameter are not valid. It is using the same value as FileList (C:\\temp\\a.txt,C:\\temp\\b.txt) that is used in workspace b published parameter.
It seams that the WorkspaceRunner doesn't send through the FileList value correctly in FME 2018. I have examined the log files and can see that in 2012, the Command line arguments are different. See below for differences (notice the qutation marks missing in 2018):
FME 2012 log file:`--FileList' `""C:\\temp\\a.txt" "C:\\temp\\b.txt""'
FME 2018 log file: `--FileList' `C:\\temp\\a.txt,C:\\temp\\b.txt'
---
I also tried the following with abnormal results.
Open the WorkspaceRunner in FME 2018. In the FileList field set C:\\temp\\a.txt,C:\\temp\\b.txt as the value. Highlight the value (ctr-a) and then copy and paste it straight back in to the field. It then turns into "C:\\temp\\a.txt,C:\\temp\\b.txt".
Is this a bug or am I missing something here?
