Post

1 follower Follow
1
Avatar

How does 'Track/Accept Changes' work for a shared project?

Hi,

How does the 'Track Changes' and 'Accept Changes'  functionality work when a team is working on a shared project where mutiple packages are being used in a check out/check in type arrangement (ie. using CC's built-in version control system)?

Let's say we have a team of 5 working on a shared project. Assume that I am the Team Lead - I wish to have sole control on when to take 'snaphots' to baseline the model at various points. I do not want the other team members to be able to baseline the model.

Can this be achieved?

Thanks

Adam

Adam Bradley Answered

Please sign in to leave a comment.

2 comments

0
Avatar

Hi Adam,

Track and Accept Changes is somewhat analogous to the Track Changes feature in Microsoft Word. When you select Track Changes, any changes to the project will be stored until someone selects Accept Changes. Selecting Show Changes will show all of the changes made since Change Tracking was turned on.

Currently, we don't have a mechanism to authorize only certain users to turn change tracking on or off.

It sounds like what you're trying to accomplish might be better handled in your revision control system. If you wanted to baseline your requirements, you could either label or branch your repository at specific points. You could then pull specific baselines from the repository. A nice way to show differences between baselines is to generate a Word report for each and use the Compare feature in Word - it will show you markup with the differences.

Let me know if this helps. Thanks!

Matt Terski 0 votes
Comment actions Permalink
0
Avatar

Hi Matt,

Thanks for clarifying, that makes sense.

Regards

Adam

Adam Bradley 0 votes
Comment actions Permalink