Printing objects referenced in a diagram

[LarrySkelly]

We have a fairly large component model, and we are adding to it a number of increases in scope.  This is a typical 'change request' scenario, where the users have identified 6-8 changes, each of which impacts 10 or more components.

The approach we have taken is to update each of the components with the impact of the change, and use a diagram to show an overall picture of the components affected by the change.  But I find that I cannot print documentation for only those objects referenced by a diagram in a package.

I think this would be a useful addition - a new RTF Documentation parameter that indicates that objects referenced in diagrams are to be exploded in the documentation.  I say 'exploded' and not 'included' as a diagram object might be a package.

I've looked for other ways to identify the components related to a change, but cannot use version (a single component is part of many changes) or date.

Its really a collection of objects that I want to print, and I can't move them to their own package.  A diagram would work perfectly for me.

Any thoughts?

Thanks,
Larry

[gsparks]

Hi Larry,

I will look into the possibility of doing this. I asssume you would create a separate package for the diagram, with no elements in it, and drag the required elements from different places in the model - with the option to expand any contained package or view or project to its full depth (regardless of content). This would also give you the ability to create complex documents based on a varied assortment of packages  - you would need to be able to set the generation order. A lot of possibilities here. I will think some more on it.

In the meantime you could consider using the element Status field to filter ... assign elements under change requests a specific status and use the RTF Status filter to get the ones you want.

Geoff Sparks

[LarrySkelly]

Geoff,

Thanks for the workaround.  The diagram-based approach is nice because it allows you to have a single object participate in multiple ''views', which is what I need.  For now I will print the entire spec and have the users navigate themselves.

Small issue.  Still love the tool.  

Larry