What tasks are you automating (or would like to) using EPDM?
How about overwriting an existing version.
We've just purchased EPDM and haven't gotten it intalled yet. One of the things that we want to automate is the creation of a complete drawing package. This package needs to have eDrawings, eParts, eAssemblies, PDF's, and DXF's. This package is sent to vendors for manufacture, where they can use the file type they need/want.
The ability to rename a file based on serial number is common.
I'm working on an implementation now that requires this, and sorting of files into a logical directory structure. Our VAR wrote something that works, but isn't usable in the real world. (It renames the file, but if you have it referenced in any open files those files get broken.) I can't believe this isn't a built-in task, or at least something so common the VAR's wouldn't all know how to do it.
We use tasks for printing, dxf export and pdf creation.
The only problem with printing task is batch printing: selected files do no print in alphanumerical order.
We also have an integration (xml export) with Axepta when a drawing is approved.
Maybe some linking to Proarc or similar system for documentation made in PDM could be automatic.
#1 on my list: An ECO/ECN form that follows a file through release! More sophisticated than a data card, please.
We currently automate:
DataCard Variables, Printing, Text file creation (of BOM).
I would like to see a more userfriendly way of automating things:
-Make the DataCard Editor behave more like Visual Basic please.
-Hability to use more robust Forms to run Tasks, dispatch and Templates.
An auto setup for the reporting tool so that you dont have to use sql to set up a reporting query.
cards based on filenames..
Task server, update the notification in the task server to include:
auto send a e-mail to admin when there is more than a choosen number of files in the "pending task list" or when a file has been too long time in the "pending task list" .
We would like to see batch printing of edrawings, auto PDF generation of AutoCAD and MS Office files, and an improved ECO/ECN process.
We are currently using automated edrawing and AutoCAD drawing generation of SWx drawings and printing of edrawings.
Invoking Templates as transition Tasks i.e, Like a product structure be created once the enquiry is confirmed.
Need a better way to vote on transition to proceed, its a spagetti nightmare getting it to work right.
We currently automate via the api:
Jason Capriotti wrote: Clear local cache and cache latest options: This is a pain. We just wrote a clear cache option that hooks to the checkin event, not ideal but covers most cases. We also need to cache library type files with the latest version, still gotta write that one. Need a login/logoff hook.
Jason Capriotti wrote:
I believe that IEdmAddIn5.GetAddInInfo can be used as a login hook.
Thanks Jim. It's very usefull and Great idea.
Some automation for deleted files still in the PDM system that isent destroyd.
Could be a trigger that after a specific date or x week/x month old deleted files automatically could be destroyd. similar to cold storage settings.
The main issue with EPDM is that it does not check if you have the latest version of a file before opening it. If you don't have a file checked out and also nobody else has one checked out, then depending on your settings, you will get a prompt asking you to check out files, which could be a way that users load the latest before the file is opened. However, you can see that is a limited set of open cases.
The basic functionality needed on every file open operation is to indicate to the user that an older version is going to be loaded (when applicable) and then provide the ability to load the latest file instead. A dialog similar to the handy "get" dialog with a list and options would work well. Also, the dialog should be as consitent as possible and have the same interface even if the model has references or not, files are checked out or not, etc. When files that are not latest or have references that are not latest are requested to open, the user is prompted and given the option to get latest. And obviously there would be some intelligence to prevent a user from overriding files that they have checked out, grab required dependencies, etc.
There is a setting an Admin can turn on that says to always work with the latest version. But there is a limitation in SEPDM in that the recent list usage in SW does not have a hook into that such that SEPDM does not know that you are opening and therefore does not serve up the latest version.
I don't think the setting you are referring to will work as I need. It does not allow a user to access an older file. Consider the case of needing to revert a part back to a previous check-in point. The steps are: (1) check the part out, (2) do a get version on the version to rever to, (3) check in. This is not possible if the setting for "always use latest" is selected because the get version action would not be possible.
Also, I don't think that a user can see the document history when the always work with latest option is enabled. Also, I don't know what SEPDM is and your statement is confusing, so I am not sure if the limitation you are indicating is relevant.
Thanks for the suggestion though. It indicates that EPDM does not provide the needed functionality, which is when you turn to custom solutions, etc.
SEPDM = Solidworks Enterprise Product Data Management (the software has changed names a few times)
we have the always use latest setting that Wayne refers to, and you can view the history, and "view" the previous versions (using e-drawings etc.)
but you are right, to take a previous version and make it the next version requires the vault admin's help in our set-up.
Retrieving data ...