Open Action Relevance

(imported topic written by SystemAdmin)

I’m wondering if there is a way to check for open task actions using relevance language? My end goal is that I would like to make my task not relevant for computers that have already had the task applied but it is still open as it is pending user interaction.

Synario:

I’m rolling out a software package that requires the user to have Outlook closed. The Action ‘Message’ prompts the user to close Outlook before clicking “take action” and as such I allow them to snooze the action for a few days. During this time the task still reports as ‘relevant’ as the software hasn’t been installed though there is an open task to install the software. Ideally I would like to make the task no longer relevant once the software is installed OR there is an open task to install the software.

Thanks

(imported comment written by BenKus)

Hey j2johnson,

I can’t think of an easy way to do this… but have you considered Offers? Maybe they will give you a useful workflow with your users…

Ben

(imported comment written by SystemAdmin)

Unfortunately I don’t think offers would work in this case given the “extra” end user interaction required. Though my task would most likely end up in the same scenario would it not? Machines would still show as relevant for the task even though there was a pending offer for them? The ability to make a task not relelvant for a computer if that task was already pending an action would very easily allow the BigFix admin/user to see new computers which need to have the task applied. Maybe something possible in the future?