You are correct, there is no need for a prefix. The conditions for a file getting into any given workflow are completely user (well Administrator) defined, as well as each transition within that workflow.
To specify any file in a certain folder would be the condition type: filepath, argument: %\[foldername]\%
These pages spell out the options:
Thanks so much. I can't hardly believe any PDM system would have such a restriction on sending anything through a workflow.
It's enough having an incompatibility between CREO and Solidworks PDM, let alone on top of it a restriction on file naming.
I'll keep everyone informed of my final outcome in case something comes out that I can share.
Thanks again !!
It is all a matter of choice... Using a prefix in all filenames to assign the Workflow has its benefits as it simplifies the rules. It reduces the complexity of ensuring files enter the correct workflow when basing it on combinations of rules - Caterory, Folder Path (folder, filename and filetype), Variables...
You should not be seeking to change what works without understanding why it has been set up in the way it has.
PS: I see that you have posted this exact same Question in a separate thread... please keep it tidy
So our admin setup a test workflow for the folder I'm testing in. She did not create a category for it and the only condition she has is the filepath.
Yet, when I try and check in a file from the path below it gives the no workflow conditions met error.
This is a snapshot she sent of the workflow properties and my folder location...so I'm wondering why it won't go in....thoughts ?