In ACT 6.03 one was able to create membership rules that allowed contacts to be added groups if certain information was entered in user fields. As a contractor this was very useful. We would create rule based on what was added in the ID/STATUS field, for example, if "Concrete Contractor" was typed in the ID/Status Field, that contractor would be added to the Concrete Contractors Group when we ran membership rules. This could be further refined by assigning that contractor to a Geographic area. That is, by setting a second condition, we could delegate the new Concrete contractor to say, Northwestern Suburbs , or City Work only, Or Southside Subs, ....what ever, you get the idea.
This allowed us to select a group of contractors to bid projects depending on where the projects were located. The "Dynamic Group Membership" in 2012 does not allow us to do this.
We also used this feature to add contacts to groups as needed. For example, after we sent out invitations to bid to a group we created, we logged the responses to a job name field as Bidding, Not Bidding, Maybe, Got Plans From FTP site, Left Message, etc, etc. As we found out about other subcontractors bidding the project we would add one of the designated conditions to the Job field, having a rule set to add any one with the Bidding, Not Bidding, Maybe, Got Plans From FTP site, Left Message, etc, etc in the Job field to a specific Group. While this still works with the dynamic functionality, I fails to add the group membership to the Groups tab on the Contact details sheet. So as bid day approaches and 5 us are mining our database to find other subs that are likely to be bidding, knowone can tell who has been called or added to the project group and who has not. This results is several people calling the same contact. I makes us look like we don't know what we are doing. While the Dynamic look up is nice, you need to tweak it a bit to restore what I felt was one of ACTs strongest attributes