That's fantastic. I was looking for this one for ages. Also raised a ticket for the support team but they didn't provided this tremendous documentation.
About time.... phew!
Now that there is some* documentation to assist with development, my primary question if using Groovy for dynamic tags is around performance. In last several years, everyone I've talked with (including at Product Owners at QSC) in regards to this functionality were extremely concerned about the scalability/performance.
Are there any recommendations or thresholds we should be aware of when using dynamics tags built with Groovy functions?
Don't use Groovy tags for more than 1000 dynamics tags on a single account
Limit the amount of method calls to < 10
Increased processing delays as more tags are created and regularly evaluated on an account
These details will be helpful for me to decide if shifting part of my current asset discovery process over to dynamic tags is worthwhile.
Retrieving data ...