I love status messages and the new state message system is a step backwards. I have no historical data for troubleshooting purposes. If I create a new revision of an application and deploy it, does it have a higher success rate than a previous revision? No clue.  

Also, I don't like that state messages are removed for deleted deployments. I want to know what deployment ran on what machine, regardless of if the deployment still exists or not. How do I know what was installed on one machine if the deployment is removed?

There are a ton of instances where historical state messages would be very helpful. It'd be amazing if you made them as detailed as the task sequence status messages, but at least keeping historical success/fail would be very help.

When I look at the reporting, I'm of course especially interested in the errors.
If there appears to be a structural problem, then a solution is developed and implemented.
However - unless it's a change in the revision of an application - there is no clear way to distinguish between errors from before and after the change.

Deployment Status messages do not include the Date/Time that the status message are processed.

We need to have the Date/Time status on these messages, so that we can determine month to month what are the successful installations we are getting on our Application Cat.

One of the main drivers of our App Cat. is to reduce then # of tickets users put in to request software installations.  By leveraging the App Cat. we are letting users Self Service many applications on their own.

When we add a new application to the Self Service catalog we need to track the time it takes user adoption but can't determine this because the Date/Time is not being collection.  We can tell the TOTAL # of Successful installations or Failures, but cannot create trend analysis without creating custom SQL jobs to daily pull the data and store it somewhere else.

It would be a great selling point for the CM App Cat. if we can show month to month, how many tickets we saved from being put into the HelpDesk.