Anyone know where this option is in the Administration set-up for EPDM. I remember I had this turned on in the last system.
Are you talking about Save and Check in as shown in the image?if that is what you are looking for, that comes by default in web2 to edit data card by checking it out and then save and check it in back
Thanks for the reply its not that, as we create new files in EPDM they are not checked in immediately after. They actually become private state until we check-in the files then they are vaulted and assigned a state. Anyone know where the setting is in EPDM to save and check-in in one step?
In your templates under admin:
Files and folders -->
Craig, this only works if you are creating new files via the template function. If you are dragging and dropping files into the system to add them, they do not get checked in automatically, they are just "added" to the private state (Which you can turn on now for the users to see).
You can setup the "Dispatch" add-in to auto check-in the files on the "ADD" operation. The only catch is it does give an error if you do a "Save as" on the file from within the application as it can't check the file in with the file open in the application, so this only works well with mass drag and drop operations. You can limit the Dispatch to only run on certain file types like .BMP or .JPG files though.
This Dispatch script checks in all files in any folder with \Projects\ in the path. It also check the file back out assuming that the user still wants to work on them. This was created since users couldn't view private files at the time. Just remove the "Check out file" line if you don't want it checked back out.
Just going to the KISS principle to solve "we create new files in EPDM they are not checked in immediately after".
My brain can't wrap itself around the KISS principle.
Thank-you very much Jason!
I will have to try this, is this the best way to migrate a lot of SolidWorks data into the vault or is pack and go the better option?
You might also want to add into dispatch to add the file name to your card variable. I don't know the rhyme or reason as to why it sometimes doesn't add/change the variable to the correct text, but dispatch forces it to change.
For migration purpose of SolidWorks files,.we dumped all SolidWorks files into a single PDM folder. Then checked in all files. Then move them to the final folder destination which will update the file references automatically.
Drag and drop, or copy paste is typically the best way to do it. Pack and Go is good because it'll ensure you get all the references for a particular assembly, but if you're looking to move large batches of data, I found it's best to create a folder specifically designed around migrating data into the vault. This means the data cards were adjusted to handle the data properly, typically meaning turning off all the 'default overwrites', and workflows/categories were adjusted to put those files into a migration specific workflow, which then had workflow links to hop anything in that folder to the workflows needed.
What are you looking to migrate though? If you're moving stuff from a network folder location, your VAR has access to a tool called the Migration Assistant, which can migrate network folder locations, and handle all the metadata transfer and all that, but it's not as simple as loading up the tool and hitting to "GO" button. You'll need to do some iterations, variable block/attribute mapping, workflow adjustments, and other things to make sure all the data gets captured properly, but the Migration Assistant tool would be your best bet.
Other than that, your only options for migration are drag and drop, copy/paste, or pack and go.
thanks very much!
that's what I was looking for thanks Charley.
Unfortunately, our VAR says the migration assistant tool is good when you are moving files from PDM workgroup to EPDM professional. they tell use we should use a script vs. using Pack and Go.
I'm a PDM Consultant, the tool can be used for network folder locations AND Workgroup to PDM professional. It's not exclusively for Workgroup to PDM Pro/Standard migrations.
If you're only looking to move single assemblies at a time, it may be best to do pack and go. If you're looking to move an entire folder, probably a drag and drop operation (after a pack and go? You'll have to strategize). If you're looking to move multiple folders, the migration assistant would be the way to go.
A script could work too though, if you're skilled at that.
Retrieving data ...