Scheduled Jobs - "Job state" web script harder to use with ACS 6.0 Object.toString-based job names

[AFaust]

BUG

WIth Alfresco Content Services 6.0, some jobs have names based on the Object.toString() result for the bean being registered, since Alfresco has simplified some of their internal registration handling. This means that the result of the "Job state" web script is now harder to use for monitoring as various jobs can now no longer be differentiated.

Expected behavior

The JSON result of the web script (/alfresco/s/ootbee/admin/scheduled-jobs-states) includes easily identifable keys / information to differentiate running jobs.

Actual behavior

Currently, various keys for running jobs are of the highly generic and unidentifiable value pattern "org.springframework.scheduling.quartz.JobDetailFactoryBean#" instead of an approriate name for the job.

Steps to reproduce the behavior

Difficult to do as it is very timing-specific to "catch" a job being run, especially in a small dev / test system.
Essentially:

• Open the Scheduled Jobs tool and activate the browser developer tools (network view)
• Trigger a job without a value in the name column
• Check the networks view for the result of the /scheduled-job-states call(s) (ideally, if the job was running long enough, there should be one response with the job listed as currently running)

Additional details (analysis so far, log statements, references, etc.)

Tell us about your environment

ACS 6.0.7-GA