This is designed to be an Offer that can be taken anytime. Whenever I take the offer it disappears from the offers section. Not sure why it doesn’t come back eventually.
For some reason this currently only works for admin users. I’d like this to eventually work for non-admin users. (obviously non-admin users would need to be given read access to the log file)
I was testing this in Windows 10, so I’m not sure if that was part of my issues.
I don’t have much experience with Offers. I just figured if I set it to reapply while relevant, or when it becomes relevant again, then it should reappear. Neither option seemed to work.
I was testing Offers last night for one of our groups, and I was able to get the Offer to return.
For testing, I created a Fixlet to create a Testing.txt file in a folder. The Fixlet was relevant if a Windows computer had the folder without the file.
I deployed the Action as an Offer, configured to re-apply if it ever became relevant again.
When I accept the offer, the file is created. If I then deleted the file, the Offer returned in a few moments.
You might need to adjust the Relevance so that once the log file has been accessed, the Task becomes Relevant again. Without knowing how your relevance is written, I’m guessing the Task never changes It’s Relevance State when you accept the Offer, so the client never sees it “become Relevant” again.
Your guess is correct, that the relevance always stayed TRUE and never went to false and then true again.
This is why I told the offer to reapply “while relevant, waiting 15min between reapplications”, which I thought would cause it to reappear, but it didn’t seem to. Perhaps I was impatient, or perhaps I need to make it work more like you suggest so the the relevance state changes.
I added the following relevance: (which probably should have been there anyway)
not exists running applications "LogExpert.exe"
This goes to false when the offer is accepted, and becomes true again when the program that is opened by the offer is closed. It reappears in the offers pretty fast after LogExpert is closed, which is exactly what I was looking to happen.
I just made an update to this task. It did not work properly if the admin user had never opened the C:\Windows\Temp folder before, which I didn’t find in my initial testing.