Audit Log view should display the affected node

Current Situation

1. Not all information from the REST API is visible with the JOC Cockpit GUI:
   1. For operations that act on a node such as "stop node" a response from the REST API is provided like this:

      {"jobChain":"/product_demo/shell_chain","node":"300","jobschedulerId":"apmacwin_4444"}

   2. For operations that act on an order such as "add order" a response from the REST API is provided like this:

      "orderId":"5142","jobChain":"/product_demo/shell_chain","state":"200","at":"now","jobschedulerId":"apmacwin_4444"}

2. Users have to open the Audit Log entry details to verify the affected node/state of a users' intervention from the request body.

Desired Behavior

1. The column "Job" that is available from the global Audit Log view should be added to the local Audit Log for the Job Chains view and Orders view. The "Job" column should display a value whenever an operation is related to a job node.
2. An additional column "State" should be added to the global Audit Log view and local Audit Log view for Job Chains and Orders that displays the affected state of an operation.
   • The "node" information from the REST API response currently is the same as the "State" information. Therefore this should be changed to reflect the same JSON property names.
   • The same "Job" can be used a number of times in a job chain, therefore the "State" information is important to identify the job node.
3. The "State" column should be visible
   • for the global Audit Log view after the "Job Chain" column.
   • for the local Audit Log view after the "Request URL" column.
4. This feature request applies to the global Audit Log view and the audit log that is available with the Job Chains view, Orders view and Jobs view.

Maintainer Notes

• This feature is not intended for immediate implementation.
• Please vote for this feature and let us know your feedback.