{"id":2,"date":"2013-07-08T14:55:00","date_gmt":"2013-07-08T18:55:00","guid":{"rendered":"https:\/\/example.org\/how-to-roll-back-a-revision-in-enterprise-pdm"},"modified":"2013-07-22T16:08:55","modified_gmt":"2013-07-22T16:08:55","slug":"how-to-roll-back-a-revision-in-enterprise-pdm","status":"publish","type":"post","link":"https:\/\/blogs.solidworks.com\/solidworksblog\/2013\/07\/how-to-roll-back-a-revision-in-enterprise-pdm.html","title":{"rendered":"How to Roll Back a Revision in SolidWorks Enterprise PDM"},"content":{"rendered":"

Workflows in SolidWorks Enterprise PDM (EPDM)<\/a> are designed to be pretty linear. Files start in the initial state in your workflow, cycle through your company\u2019s approval process and end up in the released\/approved sate at the end, where they are usually assigned a revision letter or number. Then if you want to make a new revision, you have a transition to jump the file back to the initial state and the process repeats all over again with the revision always incrementing each time.<\/p>\n

But what happens if there was a mistake and something got released\/approved that shouldn\u2019t have been? How do you correct the problem and get back to the previous revision (including the previous revision letter)?
\nOne way to do it is using the \u201cRollback\u201d command. You just right click on the file in Explorer View and select History. Then in the History window, select the version you want to revert to (1) and hit Rollback (2).<\/p>\n

\"1\"<\/a><\/p>\n

You\u2019ll get a warning dialog and if you click \u201cOK\u201d the file then rolls back to selected version and all versions created before the selected entry are removed.<\/p>\n

This is a very slick feature, but it does have a few drawbacks. One is you lose everything that occurred after the version you reverted to including the files and the history trails. If you look closely at my screenshot, you\u2019ll also notice there is a drawing associated with the part file but only the part is going to be rolled back; the rollback command can only be run on individual files and it doesn\u2019t roll back reference files. Finally, if I were to roll back the file in my example to Rev B and then later increment the revision again, it won\u2019t go to Rev C but go to Rev D instead. This is because the increment revision command does not take into account a roll back action in the workflow and it skips the revision counter you rolled back from.<\/p>\n

A different workaround (I\u2019m not going to say better) is to put a special transition in your workflow that decrements the revision. Here is how you do it. As you can see, I have a very basic workflow:<\/p>\n

\"Roll<\/p>\n

The first thing I do is add a new transition called \u201cAdmin Rollback\u201d going from my Released state (where the revision gets incremented) back to the initial state in my workflow.<\/p>\n

\"Roll<\/p>\n

On the permissions tab, I only give the Admin account permissions to run this transition (you can select other users instead, but I strongly recommend only giving one or two people access at the most):<\/p>\n

\"Roll<\/p>\n

On the Actions tab, add a \u201cset variable\u201d Transaction Action as shown.<\/p>\n

\"Roll<\/p>\n

Then add a \u201cInc. Revsion\u201d type Transaction Action.<\/p>\n

\"Roll<\/p>\n

Save everything, then back in the workflow select the state your transitioning to and go to the Revision Numbers tab. You should see your revision component and in the \u201cIncrement by\u2026\u201d column, enter \u201c<\/strong>-1\u201d and save your change.<\/p>\n

\"Roll<\/p>\n

Save your workflow, and you should be ready to roll something back. To do so, log into the vault with the correct account, find a file or assembly in the released state, right click on it and select Change State>Admin Rollback<\/strong>.
\nA few words of caution. I can use a negative value in my example because in this case it\u2019s the initial state. New files entering the vault will not have a revision value so this is permissible. If you are rolling back to a different state, you should contact CAPINC tech support<\/a> for assistance.
\nAlso, only people who know what they are doing should use either a Rollback transition or the Rollback command, so make sure you restrict user access to administrators.
\nFinally, before using either option in a production environment, try them out in your sandbox vault to familiarize yourself with them.<\/p>\n

***<\/p>\n

Jay Thompson is an Applications Engineer at\u00a0CAPINC<\/a>, a SolidWorks Value Added Reseller with locations across New England. He is a regular contributor to their CAPINC University blog<\/a>.<\/span><\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Workflows in SolidWorks Enterprise PDM (EPDM) are designed to be pretty linear. Files start in the initial state in your workflow, cycle through your company\u2019s approval process and end up in the released\/approved sate at the end, where they are<\/p>\n... Continued<\/a>","protected":false},"author":54,"featured_media":17783,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[45,16],"tags":[1000,174,187,999,997,998],"class_list":["post-2","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-solidworks-enterprise-pdm","category-tips-tricks","tag-dialog","tag-drawing","tag-epdm","tag-history-trails","tag-history-window","tag-initial-state"],"acf":[],"_links":{"self":[{"href":"https:\/\/blogs.solidworks.com\/solidworksblog\/wp-json\/wp\/v2\/posts\/2","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.solidworks.com\/solidworksblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.solidworks.com\/solidworksblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.solidworks.com\/solidworksblog\/wp-json\/wp\/v2\/users\/54"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.solidworks.com\/solidworksblog\/wp-json\/wp\/v2\/comments?post=2"}],"version-history":[{"count":0,"href":"https:\/\/blogs.solidworks.com\/solidworksblog\/wp-json\/wp\/v2\/posts\/2\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.solidworks.com\/solidworksblog\/wp-json\/wp\/v2\/media\/17783"}],"wp:attachment":[{"href":"https:\/\/blogs.solidworks.com\/solidworksblog\/wp-json\/wp\/v2\/media?parent=2"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.solidworks.com\/solidworksblog\/wp-json\/wp\/v2\/categories?post=2"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.solidworks.com\/solidworksblog\/wp-json\/wp\/v2\/tags?post=2"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}