Re: Enhancement Request

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

That's great, Rick, but it still doesn't help me.  When I'm working on a
single task, I may need to access programs from order entry, purchasing and
AP, as well as some utility programs.  The way the application suite is set
up, each application is easily filtered using a prefix on the member name
(such as ORD* for order entry).  However, there are maybe twenty different
applications.  Add to that the fact that I typically have at least two
different filters for a given prefix, one for production source and one for
test source, and you can see that I can quickly end up with a lot of
filters.  Add in variants for multiple versions or client custom code, and
you can get pretty full pretty quick, 

Now, if filters had the ability to add LISTS of selection criteria (such as
all ORD*, PUR* and SYS* members in libraries RV50PROD and REV50TEST) then it
might be a little easier.

Joe


> From: Rick.Chevalier@xxxxxxxxxxxxxxx
>
>
> Joe Pluta wrote:
> Me, I'm talking about having different filters for different
> applications within an application suite, as well as for different
> versions for historical or comparative purposes, so I need lots of
> filters in one connection.
>
> Joe,
>
> I've been using the connection per project for some time now and one of
> the things I really like is that I can easily open the connection for an
> old project and see what objects were used.  It makes going back in time
> much easier.
>
> I also think it simplifies the clutter of multiple filters.  I do use
> filter pools, but my main connection to our development box is still
> cumbersome to navigate.  It contains filters for each of the source
> files in my library (27 files, each for a different application +
> personal development/historical files) filters for members of my
> development team, and filters for our production source.  Each in a
> separate pool.  I much prefer a project connection where I can filter
> just the source files I will need.  It's a much smaller list to wade
> through.
>
> Because connections are the top level of RSI it's easy to find things if
> the names are descriptive.