It doesn't work like that. First, version control is independent for each element at the server. You don't rollback to a date, you rollback some workflow or some forms to a previous state, remaining the rest untouched.
Second, two people working separately on the same object is not desirable. In order to avoid this Remedy provides an object reservation concept, where one developer "reserves" some objects and the rest are not allowed to touch this element. It works very similar to the reservation concept of CVS. As I say in my post, it is not the best version control system (it could be far better), but it is unfair to say that Remedy doesn't have a Control Version System. Regards, Jose Huerta http://theremedyforit.com/ On Thu, Jan 12, 2012 at 21:58, John Baker <[email protected]>wrote: > So, three developers are working on something. Developer A decides that > he needs to re-run the application as per date X. If that means > developers B and C see the same change, it's not useful version control, > particularly if there are no diffs. > > Indeed, do developers B and C, who may have also been working on a > particular part of ITSM, lose their changes? > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
