Include the parameters used in the Job Report
The current Job Report is of varying usefulness, depending upon the job run. In many cases, all that is returned is the name the user gave to the batch, time and date run, the number of records processed, and a process ID which is useless on the local level.
It would be FAR more useful if the Job Report, at a minimum, included all of the parameters used to generate the report -- a summary of the selections and input made in the "Run a Job" screens. Without the parameters, troubleshooting is difficult if not impossible.
As an example, when running Norm Rules jobs to change bib or holding data, it is quite easy to accidentally select the wrong rule from the drop down menu. No matter how careful a person is in double-checking before submitting the job, accidents happen. Unfortunately, if you discover that the job ran successfully but the expected changes are not in place, there is no way to tell WHICH norm rule was run in error, other than to look at each individual record in the batch and compare versions of the record and assess the changes against the Norm Rules in the ME. And that's assuming you've cottoned on to naming your jobs to include the name of the set the job is being run against, because otherwise you are really screwed.
Annie
shared this idea
Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.
Alma Product Team
-
Naomi
commented
It would be very useful and also it would help to have detailed events report that many jobs are lacking.
-
Kathie Retszeigle
commented
This would be very helpful.