Error saving a sketch from storyboard in RRC 2.0.0.3

If you just want to save your work, hitting File, Save in the menu will save your storyboard and all of its frames.

The option "Save Frame as User Interface Sketch..." will extract the current frame into a new sketch artifact. This is similar to using parts within a sketch and lets you reuse components. Storyboard inheritance is explained in more detail here. http://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.rational.rrm.help.doc%2Ftopics%2Fc_storybrd.html

If I have a scenario where frame 3 inherits from frame 2, you will need to extract a sketch from frame 2. If you use the "Save Frame as User Interface Sketch..." option in frame 3, it will give you the error you received, in which case using that option in frame 2 would work.

If I have a scenario where frame 3 inherits from frame 2, you will need to extract a sketch from frame 2. If you use the "Save Frame as User Interface Sketch..." option in frame 3, it will give you the error you received, in which case using that option in frame 2 would work.

I have frame 3 inherit from frame 2 (Sketch or part). Does this mean that frame 3 can never be converted to a sketch?
If so, why ever inherit?

I have frame 3 inherit from frame 2 (Sketch or part). Does this mean that frame 3 can never be converted to a sketch?
If so, why ever inherit?

I would actually ask the question the other way around. Why do you want to extract each frame to each own sketch and effectively defeat the inheritance you're getting? The idea is to start a frame from a base sketch and then tweak/customize it in subsequent frames such that if you modify the base sketch later, all subsequent frames "inherit" those modifications - you don't have to go adjust each frame like you might with PowerPoint for example.

If you extract frame 2 as a sketch and then extract frame 3 as a sketch, you would lose the inheritance relationship between the two. If you change the sketch generated from frame 2 it will have no affect on the sketch created from frame 3.

Bottom line is the main inheritance you get is from reusing prior frames, not from extracting each one to it's own sketch. So again, why do you want to create so many sketches through extraction? What are you looking to achieve (because I may not be seeing/understanding your usecase)?

There is a slight caveat to this which is if you "master" one sketch with another sketch, but that's not applicable to how extracting a frame to a sketch works.

I would actually ask the question the other way around. Why do you want to extract each frame to each own sketch and effectively defeat the inheritance you're getting? The idea is to start a frame from a base sketch and then tweak/customize it in subsequent frames such that if you modify the base sketch later, all subsequent frames "inherit" those modifications - you don't have to go adjust each frame like you might with PowerPoint for example.

If you extract frame 2 as a sketch and then extract frame 3 as a sketch, you would lose the inheritance relationship between the two. If you change the sketch generated from frame 2 it will have no affect on the sketch created from frame 3.

Bottom line is the main inheritance you get is from reusing prior frames, not from extracting each one to it's own sketch. So again, why do you want to create so many sketches through extraction? What are you looking to achieve (because I may not be seeing/understanding your usecase)?

There is a slight caveat to this which is if you "master" one sketch with another sketch, but that's not applicable to how extracting a frame to a sketch works.

I though the point of a frame was to show how a Task in a process is processed.
If I have 5 frames with a common Header for look & feel, how do I link each of these frames back to a use case step/Task?
It just does not seem logical that I can copy a sketch to a frame 5 times and make frames of each frame, but I cannot make a sketch of a frame if it is copied. The limitation does not make sense to me.

Plus, the error message says I have to save something before I can create the sketch. IF the error says I cannot save a copied frame as a sketch, that would make sense as a limitation that was planned, not as something I was doing wrong.

I though the point of a frame was to show how a Task in a process is processed.
If I have 5 frames with a common Header for look & feel, how do I link each of these frames back to a use case step/Task?
It just does not seem logical that I can copy a sketch to a frame 5 times and make frames of each frame, but I cannot make a sketch of a frame if it is copied. The limitation does not make sense to me.

Plus, the error message says I have to save something before I can create the sketch. IF the error says I cannot save a copied frame as a sketch, that would make sense as a limitation that was planned, not as something I was doing wrong.

You can still link from elements (such as a panel) within any frame back to a usecase. This would actually allow you to visualize the link from within the storyboard. If you extract the frame to a sketch and create a link between the sketch and usecase, I don't believe you would see that link while viewing the frame in the storyboard. So how you choose to do this depends on how you want to visualize your links. There is no right or wrong way to do it - just options.

As for the error message, you can open a defect by creating a work item here: http://jazz.net/jazz03/web/projects/Rational%20Requirements%20Composer#action=com.ibm.team.workitem.viewWelcome