+13So I just had a policy give me the "Complete Message" even though it failed. I wasn't expecting this but honestly, the term "Complete Message" doesn't give any notion of success or failure. I just assumed it meant success.
Has anyone else seen this behavior? If so, perhaps we should put in a feature request for two messages, one on successful completion and one on failure. What do you guys and gals think?
Best answer by bvrooman
Yes, "complete" in that case refers to both success and failures (at least in my experience). A feature request might be a good thing in this case, if you make use of the messages frequently and it would be helpful to differentiate.
+16Yes, "complete" in that case refers to both success and failures (at least in my experience). A feature request might be a good thing in this case, if you make use of the messages frequently and it would be helpful to differentiate.
+13@bvrooman Yes, we use the messages all the time. The policy in question was a caching policy say Adobe Reader. I have a policy that caches the installer then displays a message to the user to let them know they can install it (the cached version) from Self Service. That message showed up on a test machine even though the policy was not present in Self Service. I started digging into the install policy to see what was going on. Finding nothing, I finally moved over to the caching policy only to see the download had failed.
So yes, it that case, it would be beneficial to have a separate message depending on success or failure.
Think I will make that a feature request. Thanks for your input.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.