We create all of our tasks with the Software Distribution Dashboard. The default action success criteria when creating a task with the SDD is “…all lines of the action script have completed successfully”. My question is why doesn’t the SDD default to, “…the applicability relevance evaluates to false”. I know this is the difference between a fixlet and a task which begs the question why have a fixlet and a task.
For every software package that gets distributed, you want to know if it was successfully installed or failed. If we leave the success criteria at the default, a task will report complete when the package really didn’t install. We will start changing the action success criteria to “…the applicability relevance evaluates to false”, unless there is some reason not to do this.
Yeah… that dashboard generating tasks is fine if you’re going to be lazy and not write applicability relevance but it kinda sucks if you write good relevance doesn’t it?
There are a couple workarounds for this:
Check the, “Reapply whenever relevant” box on the action.
On the baseline check the box to include the tasks relevance in the baseline’s relevance and then… check the “Reapply whenever relevant” box on the action.
And finally, you can just change the success criteria too but the two options listed about don’t require modification of the fixlet and option 1 can be included in an action preset
You should always include proper relevance that goes to false when the item is installed and the success criteria should always be “…the applicability relevance evaluates to false” or “custom”, but never runs to completion. This is true for all fixlets and tasks in about 98% of cases.