Tag Groups can be confusing, with some being set up for specific things. It would be nice to be able to document with more detail what some are used for and the reasons why. In particular also to document the original configuration in case values need to be tinkered with.
Edit (as replied below):
What I mean by this is, you can have a number of different Tag Groups created obviously with a name, but the name may not be descriptive enough to fully describe what it's for or more importantly, why it's there and the intentions behind having it.
Did you notice the examples in the Tag Groups manual entry?
Direct Tag Group Examples
Driven Tag Group Examples
Leased Tag Group Examples
Is there something you are looking for that these examples don't cover?
Probably the biggest stumbling block on this subject is that the Tag Group Editor / Common / Mode description is confusing. It refers only to Driven mode, but doesn't say so (leaving anyone trying to use Leased or Direct totally confused). It kind of sets people up to fail. And then it talks about less used scenarios that should only be mentioned in the description for those specific properties. The rest of the descriptions are pretty good though.
It would be ideal to have an overall description generated (based on your current selections). For example, "Subscribes to all value changes (if the value source supports subscription). If three resubscribe requests fail (attempted every 20 to 30 minutes), these tags will fail to Leased polling at 10,000ms. While a Vision/Designer Client is open and requesting these tag values, polling will change to 1,000ms. These tags will attempt to resubscribe every hour."
That would be fantastic, and answer a lot of users' questions without having to pour over the manual at all.
Hmm, re-reading my OP, I realise that it could be misconstrued!
What I meant was, you can have a number of different Tag Groups created obviously with a name, but the name may not be descriptive enough to fully describe what it's for or more importantly, why it's there and the intentions behind having it.
In these cases, it would be very beneficial to be able to add
documentation to it like you can in tags: