19 Replies Latest reply on Sep 5, 2013 5:15 PM by Kip Speck

    Ways to jump revisions in EPDM

    Pete Yodis

      We have been discussing migration of our WorkGroup data to EPDM with our VAR.  We have many documents in WorkGroup that never entered the WorkGroup vault at the initial revision in the revision scheme list.  Our list is -, A, B, C, D, E, F....etc...  We are a 76 year old company that has a lot of hand drawings that were replaced by electronic files at later revision dates.  For example, a hand drawing existed at B and then someone created an electronic drawing at C.  The electronic file at C never had a rev history of -, A, or B.  We still have the need to do this function after migration of the data as well.  With WorkGroup this was no problem, you could just select "other" in the drop down list for revision in the check in dialogue and type in the rev letter you needed to jump to (provided it was in the list of acceptable rev letters and moving forward and not backward).  Apparently EPDM can't do this because the counter underlying the rev scheme always defaults to a fixed value.  Our VAR is suggesting custom programming through the API to accomplish this?  Yuck!! Is there another way around to accomplish was is being referred to as "revision jumping"? 

        • Re: Ways to jump revisions in EPDM
          Jeremy Feist

          when we do this, we just cycle the file(s) through the workflow enough times to catch up to the intended rev.


          alternately, if you set up a migration workflow for when you move the files into EPDM that reads the file properties and assigns the correct rev, you could use that when you add tehse special files.


          also, you could leave you admin with the power to "increment rev" and they could cycle it up to the needed rev.

            • Re: Ways to jump revisions in EPDM
              Pete Yodis

              Because we have been around for a long time, there are a lot of revisions to account for.  The migration workflow would contain 553 possible state changes (don't know if state changes is the correct term).  SolidWorks supposedly told the VAR they would not recommend that, but would recommend the custom programing through the API.  I am pretty shocked the migration tool can't handle this and it seems rooted in the fact the revision counter always defaults to the same initial value.  For being as flexible as EPDM is supposed to be, it doesn't seem to flexible here on this major issue for us.  I do not like the idea of custom programming through the API, especially for upgrades down the road.


              On the "increment rev", that sounds like the answer going forward for us on new files we place in EPDM after the migration.

            • Re: Ways to jump revisions in EPDM
              Michael Dekoning



              Look at Solution S-09541, "Is it possible to import legacy SolidWorks files in PDMWorks® Enterprise vault and maintain their existing revision numbers?", in the knowledgebase on the customer portal.

                • Re: Ways to jump revisions in EPDM
                  Pete Yodis



                       Thanks for S-09541.  That could work for migration, however I saw that in order to read the revision for document being set there needs to be a custom file property for revision on the file.  We have a large amount of PDF files to migrate and I beleive there aren't any custom file properties written to them.  PDMWorks WorkGroup knows their revision in the text file stored for each PDF, but the PDF does not have any metadata containing revision information.  It sounds like this method needs to see metadata on the file in order for it to work.  Any thoughts?

                    • Re: Ways to jump revisions in EPDM
                      Michael Dekoning

                      My recollection is that this is a post-migration process that reads the custom file property value and then sets the revision to that value. Prior to migration, you need to add a variable to your vault to store the workgroup revision value and add it to the data card for PDF files. During the migration, you will need to write the workgroup revision value for each PDF file. When the files have been added, then you use the process described in S-09541.

                  • Re: Ways to jump revisions in EPDM
                    Charles Espinola



                    We migrated from Unigraphics and have many files with later revisions. Our method of handling this includes a custom properties on the data card and revision control workflow that holds all of our revisions.


                    It looks monstrous and took a few days to put together and test, but it automatically sets the files at the revision defined.


                    Here's the break down for the Custom properties. We define New, Legacy or Revised.


                         New will always start at revision A and does not pass through the "Revision Control" workflow.


                         When Legacy is selected a revision drop down opens for the user to select revision the file will be at the time of release. The legacy      selection tells the file to leave the workflow prior to release to have it's revision set by the "Revision Control" workflow at the time of      Release. When this process is complete the file has the revision the user defined and the Legacy value is set to Revised, so this      file will not go through the the "Revision Control" workflow again.


                         Revised will stay within the normal workflow and increased the revision by 1 alpha character.


                    Setting it up can be trick, so I've included a some of screen shots of revision A, B and C.

                    revision control workfllow.jpgRev A actions.jpgRev A State.jpgRev B actions.jpgRev B State.jpgRev C actions.jpgRev C State.jpg


                    I hope this is of some help.





                    It was Tammy Kolick at Cadd Edge that sent me in this direction.

                    • Re: Ways to jump revisions in EPDM
                      Kip Speck



                      Let me ask this for clarification please

                      1. You have 2 seperate documents that represent the same drawing, one is older and may be a scanned PDF, and the other may be a CAD drawing.  In the pdf your revision may be B and the CAD file it is C. 
                        • In Workgroup are the files Seperate? 
                        • In EPDM they will be seperate files.
                        • What are your expectations for this? 
                        • You can have the PDF and CAD at seperate States so that only certain people can see the older PDF. 
                      2. Are the File Names of the PDF and CAD the exact same except the .xxx extension?
                      3. Workgroup does store the Revision of the file in a text document, but onlly if it was set.  For the PDF's does Workgroup have the correct Revision stored with it in the Workgroup properties?
                      4. Do you have multiple revision schems (A,B,C, etc.. 1,2,3, etc.. REV1, REV2, etc..) from over the years?


                      The main issue with the API is dealing with the multitude of ways that Workgroup applies a Revision, When it is Work, or Checked out, it assigns a different value,


                      The API is quite capable of assigning the Rev as long as the Work Flow State has the Revision Scheme applied to it.


                      This really is not that difficult, it just require planning, and testing


                      If you need help, we do offer service to do this.


                      Kip Speck



                        • Re: Ways to jump revisions in EPDM
                          Pete Yodis




                            1.  Yes, in Workgroup the files are separate.  Yes in EDPM they will be separate files.  We expect the legacy drawing to get moved to a folder with limited access outside vault admins, just like we do now with WorkGroup.


                          2.  Yes, the filenames are the same except for the extension.  We really don't want to rename the files as that would cause work in our ERP system.


                          3.  Yes, workgroup has the correct revision stored for it according to the PDF file.  This was a manual process we underwent as PDFs were added to the vault.  We used the "revision jumping" capability in WorkGroup to set the revision to what the rev level on the PDF drawing was.


                          4.  All our drawings have a major rev scheme of -, A, B, C, ...  We have allowed SolidWorks part and assembly files only to have a secondary optional minor revision level of .01, .02, .03.... so they could be A.01, or A.02, or B.05.  This is only for part and assembly files as a way of providing a pseudo versioning functionality.  We maintain a rule that model and drawing revisions must match at the major level.  For example a drawing is at rev B and its model could move to B.01, then B.02, etc... until a change required a revision of the drawing.  At that point in time both were checked back in at rev C.  This allows to to capture changes to the models as needed that wouldn't impact the drawing.  We made a rule years ago that the rev level of the model and drawing are the same for simplicity sake.  (KISS).  The process we have been talking about in this discussion wouldn't really pertain to solidworks parts and assemblies, but I wanted to mention them to give a fuller picture of what we are doing.