Improve logging/tracability options of (HTTP) Case actions

Currently when executing case actions the investigator gets no information (UI) that an error might have occured delivering the message.

Also the logging of errors within a case audit trail seems only to work for HTTP error codes which are stored in the "comment" section in a case action history, not for other kind of actions (like servers isnt' available).

Suggestions:

• Log all Errors of a triggered case action to the case action history, not only partial specific kind of errors (like HTTP Status Response codes, 404, 401 etc.).

• Improve the logging at least with a small addition like "Error: 404" or "Error: XYZ". No details needed here, but makes sense to have a working audit trail that also helps to track down errors.

• Also log the success of delivered message ("OK")

• Ideally do not use the "comment" section but add a "status" column and store the responses there.

• Allow an option (per case action) to show a visual Information/warning to an investigator when the initial triggered delivery caused an error. No details, but perhaps an hint to contact admin or something.

• Would it be possible to store the result of a case action (sucess or errocode or something custom mapping) also to a data attribute like it is possible with the results of an external query?

Many case actions are actually critical for the workflow, regardless of emails or http commands and investigators have no chance to get a hint that a workflow might be interruppted. While operations may log an error, they have no easy way to find out what actions actually failed and who to contact. The case action audit trail also doesnt really help here, it only logs some errors in a very simple way.