RTF Filters

[Graham_Moir]

I am having a mental block.  I have an RTF template that reports on packages and elements and that template is specified for a model document that defines the packages to operate on.   The model document is then used in a master document with some standard free format sections.  Not a complex virtual document really.

As a one off I wanted to create the RTF output just for a subset of elements that had been changed over the last few days, so I thought I'd use the filter options on the RTF document generation dialogue as they are not persistent.   However I can't get any of the filters to actually work, it doesn't matter what I specify I get all the elements in the defined packages every time.  

I vaguely recall the fact that filters only work in certain circumstances but I can't find that in the help - anyone remember ?    Or should this actually work ?   this is 7.5 build 850

thanks

[Dermot]

With the RTF virtual documents - there are several levels of filtering. The non-persistant filter in the F8 window does not  apply to all templates as each Model Document has package selection and each template has specific filters set within Element-Filters (RTF editor: File Docment Options | Element Filters).

[Graham_Moir]

Ah Thanks Dermot - so the F8 filters apply to just the master document template do they ?  

I think that means that I have to set the filters temporarily in the specific model document template that picks up the packages/elements and then reset that template, i.e. remove the filters, afterwards to put it back to pick up everything ?

[Richard Phillips]

Have you tried using the 'SearchName' and 'SearchValue' tagged values of the 'Model Document'.

When you create a virtual document and create model documents, drag a package into the model document class and you can then associate a template and search criteria in the tagged values for that model document.

We then create a new virtual document for each phase and put the phase as the search value for all model documents in that virtual document.

The only thing that irritates me is that the sort (SQL order by) clause doesn't worj so I can't change the order of the elements that result from the query.

[Graham_Moir]

Well on the surface that's not a bad suggestion Richard and I think could provide an equivalent solution to setting the filters on the template.   The thing is though the help is very clear  

"In a Model Document, you should not define both a list of packages and a search; if both are present, when you generate the document Enterprise Architect works from the package list only."

And all of our documentation is currently driven from the list of packages.  

Based on the help though - you have to ask yourself why/how your approach is working.