destination folder in Composition Server

I have run into an odd thing with the destination folder in Composition Server, in trying to send the rendition to a subfolder of the source folder.

 If the PDF subfolder exists, this works ok, but if I check the “Create folder if it does not exist” option, PW doesn’t create the folder in the right place – it creates the whole tree using descriptions as names (!)

For example, if my file is in the path

by name

pw:\\PWSRV.ad.m.dk:Metro\Documents\L3DT\TMP - L3\COMP - Composition Server\IN -- no environment\

by description

pw:\\PWSRV.ad.m.dk:Metro\Documents\L3 -- Ring 3 Light-Rail - Design and Tender\TMP - L3 Testarea - Open for experiments\COMP - Composition Server\IN -- no environment\

 and I want it to appear in the subfolder ..\ IN -- no environment\PDF

so I have Place rendition in the relative folder from source file set to PDF

if I create the folder myself, ICS places the PDF file in the folder, as expected.

But if the folder does not exist, it creates the folder and all the folders above it using the descriptions as names, creating a completely different tree

pw:\\PWSRV.ad.m.dk:Metro\Documents\L3 -- Ring 3 Light-Rail - Design and Tender\TMP - L3 Testarea - Open for experiments\COMP - Composition Server\IN -- no environment\PDF

rather than
pw:\\PWSRV.ad.m.dk:Metro\Documents\L3DT\TMP - L3\COMP - Composition Server\IN -- no environment\PDF

It seems the logic to create folders is using Descriptions, while the logic to place the file uses Names.