There is probably a good reason for this but this pattern is not valid in workspace rules:
MyFile.zip > \
But this is (at least as far as the validator is concerned):
MyFile.zi? > \
Is the validator incorrect in allowing the second example through? For my practical purposes, the second example is as good as specifiying the specific filename - just seemed a bit odd to have to do it this way when they are so close to eachother.
Is it never possible to put specific filenames in workspace rules (i.e. always require at least 1 wildcard)?
We are looking into this at the moment. I suspect the bug is in the validation, I certainly can’t think of a reason why the source side of rule can not be a single file (the destination cannot though).
The first problem which I just picked up on after testing this out was that the file extension validation message you got was being treated as an error rather than a warning. Treating it as an error caused it to not save which is incorrect… warnings are just that and shouldn’t stop you from saving it.
There’s no reason why you can’t specify a file as the source pattern, we just messed up the validation code. The destination pattern is the only one that should be checked for a file extension.