@JasonWalker, that is a great idea
If evaluating the relevance via Web Reports or REST API, we can use the
first became relevant of <bes fixlet result> inspector (reference) as a means to identify roughly when it was added to the system.
Here’s a sample bit of session relevance that will return machines with a device type of ‘ESXi Hypervisor’ that have a particular Fixlet that first became relevant within the last day:
((name of computer of it, first became relevant of it) of results whose (device type of computer of it = "ESXi Hypervisor") of bes fixlets whose (display name of site of it = "BES Support" AND id of it = 204)) whose (item 1 of it > (now - 1 * day))
This approach can then be used in combination with scheduling and triggers within Web Reports.