We are using Version 3.0.1 for RRC. Previous versions allowed us create snapshot of a collection, this feature is missing in 3.0.1.

In support of CLM, I've found this:
"You might want to create a collection to:
...
- Capture the approved version of a set of requirements. For example, you can capture a set of artifacts that have been approved in a formal review. You can then work on changes to the requirements while the collection continues to show only the approved versions.
..."

I've created a revision from a colection, approved requirements and finalized review. Then, the "Create Colection" button has been activated. I've created the collection. From artifacts view, I've included a new text line in the requirement and I've opened the collection again. The requirement in the collection is the new version and not the approved version.

Is the procedure that I followed right? What do I need to do to keep the approved version of requirement en the collection ?

This question actually came up recently and this was the response:

Unfortunately, we do not have the collection snapshot capability in v3.0.1 so we cannot associate completed review artifacts to snapshot'ed collections. This feature will be making its way back into a future release of RRC. We are working on module baselines now which I would expect to also extend to collections.

There is a plan item for this in the RM 2012 plan:
44289: Baselining modules for auditability

Collections can be considered covered by module baselines.

Stef,

with Baselining Modules for auditability Feature, is it possible to link a Test Case with a specific Use Case version?