custom command pattern !/! drops file/folders containing blanks

(I know that its not best practice to have unix files or folders contained blanks, but that'a not my point)
I have a WINSCP custom command: somebashscript !/!
When applied to a file or path which contains a blank, the parameter is truncated at the first blank.
Could this be fixed?

Maybe it was my bad.
WINSCP custom command: somebashscript '!/!'
solved my problem