Using region groups has multiple minor issues to resolve.

[davenice]

In your zowe config file, you can specify a cicsplex and regionName.

Your regionName is actually a scope which is a CPSM term. It can be either the name of a region (no wildcards) or a region group (also called a system group).

You can see in Eclipse CICS Explorer we can see both regions (systems) and groups:

Here's an example of the config to show a group:

Now you'll see if you expand your CICSplex you see a different (old!) icon and just the regions within that group:

However there is a bug. The VS Code extension gets into a loop where it constantly refreshes 😬 - you can see this is happening because the loading indicator on the CICS view keeps spinning and you can't filter on regions.

[github-actions]

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

[davenice]

I think this will be improved by #610

However I believe when we have set a region in the zowe config file (either to a region name or a region group name) we should indicate that a filter is in play and can be cancelled.

So I think that the behaviour should be like this:

• If you have a region named in your zowe config
• When you expand the cicsplex and then regions node
• The regions node should show a filter set matching what was named in the zowe config
• You should be able to set a new filter or remove the existing filter
• If you close and open the regions node again i think it could revert to the original filter

There will need to be another work item created and completed to make this work fully - instead of filtering the list of regions client-side we'll need to take the user's input and set a scoped context which can either be a single region or a region group. This could be done as part of #574