Just to add to your tip:
I use these settings frequently to create custom compliance actions, and for a custom User Rights Management (Temporary Local Administrator) workflow that BigFix manages.
A few caveats on this option:
Whenever It Becomes Relevant Again
The key word here is “Again”. When executing an action that may result in only a short window for the BES client to see the relevance become false, then true again, it is sometimes missed. In short, the action is not reapplied as the client never determined the relevance was ever false.
Typically you can tell if that’s the case by testing the action on a few devices and set the Success Criteria (Success Criteria tab under Take Action) to “…the applicability relevance evaluates to false.” If the action comes back as Failed, you see on the action log for the test devices that all lines of the action completed, and the exit code isn’t showing a different reason, your action may have executed and became relevant again before the client evaluated it.
While I’ve been told that the client should evaluate the properties involved when the action completes, I’ve had a few instances where I was able to disprove this statement.
While relevant, waiting:
This is perfect for applying an action (or offer) repetitively. However, you might want to consider a baseline instead of using a singular action. As JGStew pointed out, it doesn’t care if the action relevance ever showed as False, it just knows that the relvance is still true after the time you specificed in the drop down to the right of the option.
That said, Great Tip!