Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: Jeff B. on February 09, 2012, 08:35:54 am

Title: How to Skip Certain Diagrams when Generating RTF
Post by: Jeff B. on February 09, 2012, 08:35:54 am

Given the following sample structure:

  ->Package: Diagrams
  ----->Package:System1
  --------->Diagram:System1
  ----->Package:System2
  --------->Diagram:System2
  ----->Package:System3
  --------->Diagram:System3

How can I generate (RTF) documentation starting with the package "Package: Diagrams" but have it skip the diagrams in, say, "Package:System2"?

I was hoping I could use an element filter based on a Tagged Value but that doesn't seem to work (I don't think I fully understand the purpose of Element Filters).  Is there a way to filter certain diagrams out when generating the documentation - based on a Tagged Value?

I realize I can exclude a package from documentation on a "global" level (by setting the "Exclude Package from Generated Reports") but I don't want to do that.  I want to be able to exclude it at the time I generate the report (because I might have one report that includes a given package and another report that doesn't).

Is this possible?

  --- Thanks, Jeff

Title: Re: How to Skip Certain Diagrams when Generating R
Post by: philchudley on February 09, 2012, 09:27:35 am

Hi Jeff

Although not exactly what you are after, the properties of a diagram (Diagram tab) has a checkbox [highlight]Exclude image from RTF reports[/highlight]

Before generating documentation, you could check this checkbox for eaxh diagram then generate the report.

Another possibility is to have two packages. Copy each diagram to the clipboard and then paste using shallow copy into the second package. In one package you have the checkbox for excluding the image set and in the other package have the checkbox cleared.

Then you could use either package to drive the documentation with or without the diagrams. Being shallow copies changes to the diagrams in either package will ensure they are synchronised.

By using either model documents or resource documents, the documentation production would a bit smoother.

Hope this makes sense

Cheers

Phil