AnsweredAssumed Answered

Controlling changes

Question asked by David Watkins on Aug 27, 2013
Latest reply on Sep 4, 2013 by Christian Chu

Like • Show 0 Likes0
Comment • 6

I have setup a vault to test out using workgroup and I have a question about how to fit it into our workflow. We often collaborate on projects so currently we have network folders for files that are in development and another for released ones. If a component is being updated it is copied from the released folder to the development folder and worked on there so changes don’t affect other things until it is released.

Now, after playing around with WPDM I understand when I check something out of the vault it copies to my working folder and I am working on it from there. However if another user needs the new version I don’t understand how to get it to them without affecting the released version? If I check it in, it affects the released version. I am looking into setting up a lifecycle but so far I find it to be overly complex and too much time for an admen to manage. Are there other ways to set this up?

Thanks,

David

No one else has this question

Outcomes

Jerry Steiger Aug 27, 2013 7:20 PM

David,

You can set up WPDM to use a working version that you can check back in as often as you like before checking in as the new release. As I recall the working version is shown as a + on the version it was built from (3+ or C+). You can also just put a copy of your present version of the file on the other person's working directory.

Jerry S.

Actions

Christian Chu Sep 3, 2013 4:29 PM

Check in/out as a working copy is a way to go

Life cycle definitely solves your problem. It's not complex as you thought. I think you'd better spend time for setting it up now or later things would be actually "complex" and out of control - from my experiece - please avoid "short cut" if you can

Actions

Aaron Godwin Sep 3, 2013 5:44 PM

We have the same problem, so when we work on released files we try and work out of network folders. Once our files are released Admin. retains ownership always, so the "+" check-in wouldn't really work. And once a change is released Admin. can go grab them and check them back in if they're on the network.

Actions

Christian Chu @ Aaron Godwin on Sep 4, 2013 10:50 AM

Sorry if I missed something here - soon the file is released - the rev. can't be changed; otherwise, you will confuse the vendors or other users, any work/change should be on the next rev. (back to development/modifed status - you name it) - working copy should not be used on the release for a change

Actions

Aaron Godwin @ Christian Chu on Sep 4, 2013 11:32 AM

Yes, I have to fill out change requests and then change orders to make a change and bump the rev. And from time to time we have a change start but not get implemented.

The only time I use the working copy on released files is when something is added that is not a change to the part or drawing, like a configuration for assembly use. We have things like hoses and cables that are straight on a drawing and then bent in an assembly. So because it's more of a cosmetic change for an assembly the part rev has no need to bump.

Actions

Christian Chu @ Aaron Godwin on Sep 4, 2013 12:29 PM

The other option is to use "Allow latest revision overwrite" then you can keep the same release rev.

Actions

6 Replies

Jerry Steiger Aug 27, 2013 7:20 PM
Mark Correct
Correct Answer
David,

You can set up WPDM to use a working version that you can check back in as often as you like before checking in as the new release. As I recall the working version is shown as a + on the version it was built from (3+ or C+). You can also just put a copy of your present version of the file on the other person's working directory.

Jerry S.
Like • Show 0 Likes0
Actions
Christian Chu Sep 3, 2013 4:29 PM
Mark Correct
Correct Answer
Check in/out as a working copy is a way to go
Life cycle definitely solves your problem. It's not complex as you thought. I think you'd better spend time for setting it up now or later things would be actually "complex" and out of control - from my experiece - please avoid "short cut" if you can
Like • Show 0 Likes0
Actions
Aaron Godwin Sep 3, 2013 5:44 PM
Mark Correct
Correct Answer
We have the same problem, so when we work on released files we try and work out of network folders. Once our files are released Admin. retains ownership always, so the "+" check-in wouldn't really work. And once a change is released Admin. can go grab them and check them back in if they're on the network.
Like • Show 0 Likes0
Actions
- Christian Chu @ Aaron Godwin on Sep 4, 2013 10:50 AM
  Mark Correct
  Correct Answer
  Sorry if I missed something here - soon the file is released - the rev. can't be changed; otherwise, you will confuse the vendors or other users, any work/change should be on the next rev. (back to development/modifed status - you name it) - working copy should not be used on the release for a change
  Like • Show 0 Likes0
  Actions
  - Aaron Godwin @ Christian Chu on Sep 4, 2013 11:32 AM
    Mark Correct
    Correct Answer
    Yes, I have to fill out change requests and then change orders to make a change and bump the rev. And from time to time we have a change start but not get implemented.
    
    The only time I use the working copy on released files is when something is added that is not a change to the part or drawing, like a configuration for assembly use. We have things like hoses and cables that are straight on a drawing and then bent in an assembly. So because it's more of a cosmetic change for an assembly the part rev has no need to bump.
    Like • Show 0 Likes0
    Actions
    - Christian Chu @ Aaron Godwin on Sep 4, 2013 12:29 PM
      Mark Correct
      Correct Answer
      The other option is to use "Allow latest revision overwrite" then you can keep the same release rev.
      Like • Show 0 Likes0
      Actions

Controlling changes

Outcomes

Related Content

Recommended Content