This is a very good forum where gurus can relate to newbies so you are in good hands. The only silly questions are ones not asked.
- I recommend not focusing on the filenaming convention as the primary issue and go straight to making your EPDM template create not only the new folder with serial number but also a blank .sldprt & .pdf with serial number.
- Then you can create a dispatch to do a filename check against the data card variable value upon checkin and if they don't match, cancel the epdm checkin command.
Option B (#1 below is what we do)
- Let all files get checked in to an "initiated" state, allow users to rename, delete, add, check out/in but this "initiated" state is not part of a workflow cycle but once the file enters the cycle, can't be deleted or renamed without admin intervention.
- Then you can put conditions on the workflow transition to disallow any files to transition through unless they begin with 12345 or whatever. This one gets a little tricky if you have to match every file dynamically against their specific data card variable values.
- Create an addin to manage this part of your workflow
Are any of these even remotely close to a concept you are hunting for?
I thought about trying to set up Option B, but I wasn't sure how to set the transition Conditions to check the FilePath against a variable. Will you give me some detail on that?
With Option B #2 "This one gets a little tricky if you have to match every file dynamically against their specific data card variable values."
The variable value would have to be static or constant. Will that variable value always be static?
If it is dynamic, then an addin or dispatch will be your path. Probably Dispatch because you can store variable values and path names then compare.
The variable will be constant within a folder. It is set by a template variable once, then stays the same after that. However, there will be a different variable for each folder. Will that still work? It isn't a fixed number of characters. It may be 6, 7, or 8 characters. I haven't gotten into Dispatch yet. I guess it's time! I can't get to the Admin guide because our network at work is down this evening for updating. I might be able to tomorrow if it is fixed.
Maybe there is a solution if folder name contains the project number. If that I think you could combine Tim solution B with a dispatch action.
In dispatch you can read "Name of current folder" and you can create a variable with this and ca obtain with a left function, let's say, the first for characters from folder name. With the same method but using "Name of selected file" you van obtain the first n characters from file name. Compare those two variables and if it's false you can send a message to the user. I know that it is not an elegant solution but otherwise I think that you need an addin to resolve that.
It isn't in the name of the folder we are saving into, but it is in the name of the parent folder of the folder we are saving into. Is that still workable? If I have to, I guess I could change the name of this folder to include the variable. However, the variable is not a fixed number of characters. It may be 6, 7, or 8 with the last 3 being the important ones regardless of length. I haven't looked at Dispatch yet. It may be time.