Concurrent requirement access
![](http://jazz.net/_images/myphoto/1a1c3766c4729aa468c4ad84f520e6df.jpg)
One answer
![](http://jazz.net/_images/myphoto/1a1c3766c4729aa468c4ad84f520e6df.jpg)
How does RRC handle concurrent requirement/artefact access/modification between 2 users?
From the RRC 2.0 New & Noteworthy:
https://jazz.net/downloads/rational-requirements-composer/releases/2.0?p=news
Improved team experience
Collaborate more effectively in a team environment with improvements in edit conflict resolution.
* Receive a visual indication that artifacts have changed on the server while editing
* Refresh the contents of editors with the latest from the server without having to close and reopen the editor
* Compare your changes in requirements and selected artifacts side-by-side with the latest content on the server.
In other words, if you are editing an artifact but haven't saved it yet, your RRC client will show an icon change in the upper right indicating someone else has changed the artifact. When you attempt to save, the client asks you to be explicit in saving over the changes (the other persons' changes are lost) or incorporating them (manually) into your version of the artifact.
Some customers have also asked for explicit locking capability; I believe there is an enhancement open for that.
Daniel