I have over 75 Custom Node Properties I use in my environment. Most are just informational providing contact information, data center location, rack location, assigned engineer, etc. but much of this information is repeated for all nodes belonging to a particular customer, for example. It means having to cut and paste the same values to each node one field at a time. This ends up chewing up a whole lot of time.
A solution might be to have Group Custom Properties, Categorized Groups and a detail View for displaying related Group Custom Properties for Groups that fill into a certain category. You could then create a Group in the category "Customer" for example which would have the common Custom Properties for all the customer's nodes. You would, of course, add all the customer's nodes and possibly even the related Application Monitors to the group. Then on the node or Application Monitor Details screen you would add a View for displaying a Group Categories Custom Properties, edit the View and choose the Group Category to use.
By designing it similar to the above, you could add a new customer and as long as you use the same Group Category to provide the Group Custom Property values, the webpage should just automatically display the Group Customer properties associated.
For this truly be a good design however, you really need to have a key field between the Node Custom Properties and this Group Custom Properties in order to tie them together and avoid duplicate Groups in the same Group Category using the same key. Otherwise you would run into problems with the View being confused about which Groups Custom Properties to use.
Anyway, wanted to throw out some thoughts on how this might work better for me and see if others have ideas for a solution. Mine may not be completely honed but maybe it will help to get the creative juices flowing.