Fixlet messages and tast

Content Authoring
1

(imported topic written by zhenwenw91)

Hi, Can someone help me by answering my below queries?

Is there any deference between fixlet messages and tast?

2

(imported comment written by brolly3391)

Hello zhenwenw,

There is a philosophical difference between Fixlets and Tasks. A Fixlet takes a known “broken” condition and fixes it. A Task takes a “not-necessarily broken condition” and changes it to something else that is “not-necessarily fixed”, like a configuration change for instance. A task would be changing the logon account that a service uses. A Fixlet would be upgrading an out of date .dll.

By default, when a fixlet finishes it’s action script, it checks the relevance to make sure it has gone from true (fixlet is relevance) to false (whatever was broken is now fixed) and reports back Fixed when it is done running.

By default, when a task finishes its action script, it does not check the relevance again. If all the lines in the action script completed then the client considers that action successful and reports back Complete.

To sum up

Fixlet: For fixing things, checks relevance after action script, reports back Fixed.

Task: For changing/configuring things, does not check relevance after action script, reports back Complete.

Cheers,

Brolly

3

(imported comment written by mellis200091)

So, for example, if I’m understanding correctly, it would be possible for me to, for example, run the “Automatically Restart Stopped BES Clients using TaskScheduler” task on a system, and then run it again another day. Based on your explanation, that makes sense, particularly since this particular task requires you to enter a time, so it would make sense that you should be able to run it again if you want to change the time, for example.

Thanks,

Mike

4

(imported comment written by SystemAdmin)

Can an existing task be changed to a fixlet?

or would I have to create a new fixlet and copy the contents of the task relevance and action into the new fixlet?